[Mailman-Users] Problems after server migration

[Glen Prideaux]

Is it possible that the new server has two installations of Mailman in different locations, and the one referenced by the startup script (that can't find the lists) is different from the one you are accessing manually? 

Glen

> From: alv at alv.cl
> Subject: Re: [Mailman-Users] Problems after server migration
> Date: 17 July 2013 8:38:12 AM AWST
> To: mailman-users at python.org
> 
> 
> On Tue, 16 Jul 2013 at 12:28pm, Mark Sapiro wrote:
> 
>> This makes no sense.
> 
> Yes, that's why I'm so puzzled.
> 
> 
>> Does bin/list_lists list both the old and the newly created, working lists?
> 
> Yes.
> 
> 
>> Are the mode and group of the lists/LISTNAME directories and the lists/LISTNAME/config.pck files the same for all lists?
> 
> Yes, all files and directories belong to mailman, and mailman group.
> 
> 
>> Does 'bin/dumpdb lists/LISTNAME/config.pck' produce appropriate output for both old and new lists?
> 
> They both seem consistent. Is there anything in particular I should look more carefully?
> 
> 
>> Does mail to the newly created lists work?
> 
> Yes.
> 
> 
>> Does the old server still exist, and if so is there some possible
>> confusion between IPs and DNS so something is looking at the wrong
>> machine?
> 
> The old server no longer exists. There's no chance of confusing because I'm sending the test mails from the mailman server itself.
> 
> 
>> Try 'grep -r xxx.xxx.xxx.xxx /usr/lib/mailman /var/lib/mailman'
>> where xxx.xxx.xxx.xxx is the old IP. There should be no reference by IP,
>> but ...?
> 
> As you suggested I did that, but all I found was references to the old IP in the archives.
> 
> Somehow the old lists are registered somewhere else and the "service mailman start" doesn't know where and refuses to start without a list called mailman.
> 
> 
> Regards
> 
> 
> -alv-