[Mailman-Users] What is really required to go from 2.0.x to 2.1.y?
I am almost hesitant to post this email at all, because I am so amazingly confused at what is going on I half-think I'm imagining it. I have a Mailman 2.0.12 instance (not 2.0.5 as I previously thought, sorry Mark) running on a Solaris 8 SPARC server, which I'd planned to move onto a Linux RHEL4 x86 server using Mailman 2.1.9. In both cases, Mailman would be installed into /home/mailman to minimize configuration changes. In both cases, the hostname of the server would be list.bowdoin.edu. In both cases, /home/mailman would actually be served via NFS. And, oh yeah, I'm switching MTAs too (Postfix to sendmail). So, I made a copy of /home/mailman (which is actually on a NetApp) in case I had to revert my migration from Solaris to Linux. This was my workflow on the Linux server: * mount a fresh copy of /home/mailman (which is Mailman 0.12 from Solaris) * rm -rf /home/mailman/Mailman (because I'm switching MTAs) * configure Mailman 2.1.9 using the following string: ./configure --prefix=/home/mailman --with-urlhost=list.bowdoin.edu --with-mailhost=list.bowdoin.edu --with-cgi-gid=apache --with-mail-gid=mail * run make install * watch as make install runs bin/update, it fails on a couple of lists. Remove the offending lists, re-run bin/update, watch it run successfully. * rm /home/mailman/locks/* ; rm /home/mailman/qfiles/* ; rm /home/mailman/data/pending_subscriptions.db just to make sure * run bin/check_perms -f, watch it run successfully. * run bin/genaliases, paste output into /etc/aliases, run newaliases * run bin/mm_sitepass * run bin/mailmanctl start The problem is when I run bin/list_members on a list of whose membership I know well. Amazingly, when I run that command, I see list members from around 2-3 years ago; I do not see list members whom I absolutely know are on that list. And then, well, I get so confused I can hardly stand. :) What on earth is going on here? I have seen URLs like http://acd.ucar.edu/~fredrick/linux/mailman/upgrading.html and http://www.mail-archive.com/mailman-users@python.org/msg13279.html with hints for migrating server and versions at the same time; specifically running the fix_url command to update URLs for archives. But, I'm keeping the same hostname (list.bowdoin.edu) from both Solaris and Linux, so I don't bother with this. Does anyone have the faintest idea of what's going on? It's like I'm seeing a ghost. I know that copy of /home/mailman is, pre-upgrade, the same from the Sun server to the Linux server because there are unique files in there which I've placed myself. FWIW, I just made *another* copy of the /home/mailman directory from the Sun server, mounted it on the Linux server and DID NOT UPGRADE IT. Lo and behold, when I run bin/list_members, I see _correct_ users, _not old ones_. Thoughts? Am I going crazy? Thanks, Chris -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?
Christopher Waltham wrote: process snipped, but it looks OK The problem is when I run bin/list_members on a list of whose membership I know well. Amazingly, when I run that command, I see list members from around 2-3 years ago; I do not see list members whom I absolutely know are on that list. And then, well, I get so confused I can hardly stand. :) I don't know, but I have a good guess. 2-3 years ago, someone tried to migrate to Mailman 2.1.x and then reversed, but this process left config.pck files (converted from the 2.0.x config.db files) in some or all of the lists/listname/ directories. The current list upgrade process is finding those old config.pck files and using them in preference to the actually more current config.db files. Does anyone have the faintest idea of what's going on? It's like I'm seeing a ghost. I know that copy of /home/mailman is, pre-upgrade, the same from the Sun server to the Linux server because there are unique files in there which I've placed myself. FWIW, I just made *another* copy of the /home/mailman directory from the Sun server, mounted it on the Linux server and DID NOT UPGRADE IT. Lo and behold, when I run bin/list_members, I see _correct_ users, _not old ones_. Thoughts? Am I going crazy? Start with your good 2.0.12 installation and remove any config.pck and config.pck.last files from the lists/listname/ directories and then follow your upgrade procedure. Then when you are satisfied with the results, remove the old config.db and config.db.last files from the new installation so that they can't be used as fallbacks 2 years from now. A possibly viable alternative is to look at your 2.1.9 installation and just remove the config.pck and config.pck.last files from any lists/listname/ directory that has a config.db. Mailman will then convert the config.db the first time the list is accessed, and if you like that, you can then just remove the old config.db* files. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?
Again, apologies for the way Exchange Webmail quotes messages. -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Fri 3/14/2008 1:37 PM To: Christopher Waltham; mailman-users@python.org Subject: Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y? The problem is when I run bin/list_members on a list of whose membership I know well. Amazingly, when I run that command, I see list members from around 2-3 years ago; I do not see list members whom I absolutely know are on that list. And then, well, I get so confused I can hardly stand. :) I don't know, but I have a good guess. 2-3 years ago, someone tried to migrate to Mailman 2.1.x and then reversed, but this process left config.pck files (converted from the 2.0.x config.db files) in some or all of the lists/listname/ directories. Running this: ( cd lists ; find . -name config.pck ) finds lots of results -- I have a lot of lists, but I bet there's one for each list. :-( As you go on to explain, there were lots of config.pck.last files, too. The current list upgrade process is finding those old config.pck files and using them in preference to the actually more current config.db files. I had hoped (feared?) the process was doing something like what you outline, but at least I now know what it is! Start with your good 2.0.12 installation and remove any config.pck and config.pck.last files from the lists/listname/ directories and then follow your upgrade procedure. Done... Then when you are satisfied with the results, remove the old config.db and config.db.last files from the new installation so that they can't be used as fallbacks 2 years from now. In the process of doing this now. A possibly viable alternative is to look at your 2.1.9 installation and just remove the config.pck and config.pck.last files from any lists/listname/ directory that has a config.db. Mailman will then convert the config.db the first time the list is accessed, and if you like that, you can then just remove the old config.db* files. Just out of interest, what defines access? Is this something I can accomplish from the command-line myself, or does it require the mailman wrapper command being called from the aliases file? Thanks again, Mark, Chris -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?
Christopher Waltham quoted me and wrote: A possibly viable alternative is to look at your 2.1.9 installation and just remove the config.pck and config.pck.last files from any lists/listname/ directory that has a config.db. Mailman will then convert the config.db the first time the list is accessed, and if you like that, you can then just remove the old config.db* files. Just out of interest, what defines access? Is this something I can accomplish from the command-line myself, or does it require the mailman wrapper command being called from the aliases file? Anything that instantiates a list object. From the command line, bin/list_lists will do it for all lists. Any command that targets a list (e.g. bin/list_members) will do it for that list. From the web, the listinfo overview page will do it for all lists, and any list specific page will do it for that list. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
