These things happened last week:
* ssh connections to cl-net were routed to new-cl-net * we were asked to install several applications on new-cl-net (emacs, zsh) * we started to create subdomains for services (first: git.cl.net) * after being reported that people were missing group memberships, we've now migrated all project related groups with a gid < 1000; because those numbers are reserved for system groups, they were excluded from the account/group migration. In order to prevent similar issues in the future, all these groups have been renumbered. There's currently a batch running to re-assign all group ownerships in the file systems
* we stopped routing traffic to new-cl-net because commit mails were no longer coming through [the mailer wasn't fully set up yet on new-cl-net]
Next steps:
* set up the mailer * re-instate the ssh traffic route to new-cl-net * set up the webserver in order to be able to migrate trac.c-l.net
Anybody who wants to use new-cl-net services directly should log into tiger.common-lisp.net; passwords and ssh keys are the same as on common-lisp.net (aka elephant.common-lisp.net).
Bye,
Erik.
Hi,
can someone who knows more about Debian resolve this?
common-lisp:/etc# apt-get install exim4 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: exim4-base exim4-config exim4-daemon-light Suggested packages: eximon4 exim4-doc-html exim4-doc-info spf-tools-perl swaks The following packages will be REMOVED: postfix The following NEW packages will be installed: exim4 exim4-base exim4-config exim4-daemon-light 0 upgraded, 4 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B/2030 kB of archives. After this operation, 868 kB of additional disk space will be used. Do you want to continue [Y/n]? E: Could not perform immediate configuration on 'exim4'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
Thanks, Hans
On Sat, May 7, 2011 at 10:41 AM, Erik Huelsmann ehuels@gmail.com wrote:
These things happened last week:
* ssh connections to cl-net were routed to new-cl-net * we were asked to install several applications on new-cl-net (emacs, zsh) * we started to create subdomains for services (first: git.cl.net) * after being reported that people were missing group memberships, we've now migrated all project related groups with a gid < 1000; because those numbers are reserved for system groups, they were excluded from the account/group migration. In order to prevent similar issues in the future, all these groups have been renumbered. There's currently a batch running to re-assign all group ownerships in the file systems
* we stopped routing traffic to new-cl-net because commit mails were no longer coming through [the mailer wasn't fully set up yet on new-cl-net]
Next steps:
* set up the mailer * re-instate the ssh traffic route to new-cl-net * set up the webserver in order to be able to migrate trac.c-l.net
Anybody who wants to use new-cl-net services directly should log into tiger.common-lisp.net; passwords and ssh keys are the same as on common-lisp.net (aka elephant.common-lisp.net).
Bye,
Erik.
Hi,
can someone who knows more about Debian resolve this?
We found the solution to this yesterday. For the record, it was this command which fixed the situation:
$ dpkg --force-all -r postfix
The situation was caused by postfix having been installed before the exim setup was attempted.
Bye,
Erik.
Hi,
Next steps:
* set up the mailer
Well, Hans was able to get the MTA up and running. It's now able to send out commit mails and handle mailing list traffic. Setup includes handling of mails for the ticket handling system.
We can't switch to the next steps below yet, because:
* the webserver (on new) needs to be configured to handle serving the mailman web interface and archives [done; although I need to make this an official vhost] * the webserver (on old) should be configured to respond with "permanently moved" responses [to be done]
In order to be able to forward the web ui and archive traffic to the new host, I've created 'lists.common-lisp.net' to serve list related web traffic.
* The common-lisp main website needs to be adjusted to point to the new lists.* subdomain. [in progress; I've copied /var/www to /var/www-new-lists for the purpose on old-cl-net]
* set up Apache virtual hosts for common-lisp.net, lists.common-lisp.net, trac.common-lisp.net (others?)
* re-instate the ssh traffic route to new-cl-net
When we reinstate ssh traffic routing, we'll also need to migrate Trac: some projects will depend on being able to call the trac-post-commit handler for subversion integration. Maybe other version control tools have similar integration. [Nice to have to be around the same time; but it does like a good next step after ]
* set up the webserver in order to be able to migrate trac.c-l.net
So, all in all, this was a productive weekend and we're ready to take the next steps.
Before we can switch over the MX dns entry, Hans said we need to copy the /var/lib/mailman/lists directory, meaning that the switch-over steps will be: * Turn off the MTA on old-* * Turn off mailman on old-* * Turn off mailman on new-* * Sync mailman lists directory to new-* * Update the URL in the existing projects using the command "/usr/lib/mailman/bin/withlist -l -a -r fix_url -- -v" * (re)start mailman on new-* * introduce redirect rules for common-lisp.net/pipermail, common-lisp.net/mailman/ and common-lisp.net/cgi-bin/mailman to lists.common-lisp.net/* * move the /var/www-new-lists directory over the /var/www directory, updating links to lists.common-lisp.net.
I'll keep you posted on my progress. In case anybody has cycles to spend...
Bye,
Erik.
Hi all,
To follow up on my earlier mail from last weekend:
* set up Apache virtual hosts for common-lisp.net, lists.common-lisp.net, trac.common-lisp.net (others?)
I've set up two virtual hosts in the web server: lists.cl-net and trac.cl-net (the latter has an alias for trac.new.common-lisp.net for as long as it's not the main trac server yet).
The Trac webserver configuration has been ported from Apache1.3 to Apache2.2, which should take us another 15 years to require updating again :-)
* re-instate the ssh traffic route to new-cl-net
When we reinstate ssh traffic routing, we'll also need to migrate Trac: some projects will depend on being able to call the trac-post-commit handler for subversion integration. Maybe other version control tools have similar integration. [Nice to have to be around the same time; but it does like a good next step after ]
* set up the webserver in order to be able to migrate trac.c-l.net
This has happened now, including authentication setup. If people could test the new setup is stable again, I'd like to switch trac.cl-net to this new service.
Raymond, this is where you could do some testing: I've converted the 'oct' trac.ini to support git. There were other projects you wanted to use with git support. It'd be great if you could test those on the new machine.
So, all in all, this was a productive weekend and we're ready to take the next steps.
Before we can switch over the MX dns entry, Hans said we need to copy the /var/lib/mailman/lists directory, meaning that the switch-over steps will be: * Turn off the MTA on old-* * Turn off mailman on old-* * Turn off mailman on new-* * Sync mailman lists directory to new-* * Update the URL in the existing projects using the command "/usr/lib/mailman/bin/withlist -l -a -r fix_url -- -v" * (re)start mailman on new-* * introduce redirect rules for common-lisp.net/pipermail, common-lisp.net/mailman/ and common-lisp.net/cgi-bin/mailman to lists.common-lisp.net/* * move the /var/www-new-lists directory over the /var/www directory, updating links to lists.common-lisp.net.
I'm planning to execute the steps above (migrating the MTA) on friday night, if feedback on Trac is good enough (or none). If there's any reason not to proceed, please let me know before Friday 18:00 CEST.
Bye,
Erik
"Erik" == Erik Huelsmann ehuels@gmail.com writes:
Erik> Raymond, this is where you could do some testing: I've converted the Erik> 'oct' trac.ini to support git. There were other projects you wanted to Erik> use with git support. It'd be great if you could test those on the new Erik> machine.
Thanks! I'll test it today. I was a little unclear about the host names though. To test trac, I should use trac.common-lisp.net, like I used to? Or should I be using trac.new.common-lisp.net?
Ray
"Raymond" == Raymond Toy toy.raymond@gmail.com writes:
"Erik" == Erik Huelsmann ehuels@gmail.com writes:
Erik> Raymond, this is where you could do some testing: I've converted the Erik> 'oct' trac.ini to support git. There were other projects you wanted to Erik> use with git support. It'd be great if you could test those on the new Erik> machine.
Raymond> Thanks! I'll test it today. I was a little unclear about the host Raymond> names though. To test trac, I should use trac.common-lisp.net, like I Raymond> used to? Or should I be using trac.new.common-lisp.net?
For the record, git and trac integration are working well on trac.new.common-lisp.net. (Especially after I entered my password correctly.)
As a bonus (for me), hg and trac integration seems to be working just fine too.
Many thanks to the admins for doing a fine job of upgrading/migrating common-lisp.net!
Ray
-
Erik Huelsmann -
Hans Hübner -
Raymond Toy