[Mailman-Users] moving mailman

[mardin at comcast.net]

Mark,

Please see the errors after moving to the new mailman server with same hostname and IP address:

> Didn't work how? What happens when you post to a list? What happens
> when you go to that URL?

(1) Went to URL (http://mailman_server.domain.net/mailman/admin/) and got errors:

Not Found
The request URL /mailman/admin/ was not found on this server

(2) Errors of post to the mailing list test at mailman_server.domain.net

Jul 11 8:02:20 mailman_server sendmail[5791]: k6BM2ALL005791: from=<mardin at domain.net>, size=418, class=0, nrcpts=1, msgid=<44B41F46.3080604 at domain.net>, proto=ESMTP, daemon=MTA, relay=mardin.domain.net [163.10.21.33]
Jul 11 8:02:20 mailman_server smrsh: uid 8: attempt to use "mailman post test" (stat failed)
Jul 11 8:02:20 mailman_server sendmail[5792]: k6BM2ALL005791: to="|/usr/local/mailman/mail/mailman post test", ctladdr=<test at mailman_server.domain.net> (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30624, dsn=5.0.0, stat=Service unavailable
Jul 11 8:02:20 mailman_server sendmail[5792]: k6BM2ALL005791: k6BM2ALL005792: DSN: Service unavailable

Thanks for your help!
Mardin


 -------------- Original message ----------------------
From: Mark Sapiro <msapiro at value.net>
> mardin at comcast.net wrote:
> >
> >The Mailman 2.1.5 was running well. We wanted to move it to another computer 
> with more powerfull hardware. We installed the same Linux system on the new 
> computer.
> >  
> >Then we moved all Mailman related data from the original computer to the new 
> computer:
> >/usr/local/mailman
> >/home/mailman
> >/etc/passwd
> >/etc/group
> >/etc/httpd
> >/etc/init.d/mailman
> >/etc/mail
> >/etc/aliases
> >
> >We powered off the original computer and renamed the new computer with the 
> original hostname and IP address. After that we restarted mailman on the new 
> computer
 and got the master qrunner lock errors::
> ># su - mailman
> >$ cd /usr/local/mailman
> >$ bin/mailmanctl start
> >The master qrunner lock could not be acquired. It appears as though there is a 
> stale master qrunner lock. Try re-running mailmanctl with the -s flag.
> 
> 
> Because you moved /usr/local/mailman while Mailman was running on the
> old system so you moved the lock files.
> 
> 
> >We re-run mailmanctl with the -s flag without errors: 
> >$ bin/mailmanctl -s start
> 
> 
> OK
> 
> 
> >then restart mailman again:
> >$ bin/mailmanctl -s -q start
> 
> 
> Unless you stopped Mailman in between, you now have two masters and
> sets of qrunners running. This is bad. See
> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>
> and stop all the Mailman processes as described there and then do
> 'bin/mailmanctl start' just once.
> 
> 
> >The maiman daeman were up but both mailman and http://hostname/mailman/admin/ 
> didn't work. Does anyone know how to resolve it?
> 
> 
> Didn't work how? What happens when you post to a list? What happens
> when you go to that URL?
> 
> 
> >questions: Is the above moving method correct or not? Did we forget something 
> else? Is there a better way to move mailman without re-compile it to another 
> same hostname, IP address, and same OS system machine?
> 
> 
> I would stop the MTA, web server, Mailman and all other services on the
> source machine before moving the directories and files, but I would
> prefer to actually install and test all the software on the new box
> and then just move the list and archive data for Mailman.
> 
> -- 
> Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>