Re: [Mailman-Users] Bug in Mailman version 2.1.25
Many thanks. I have restored my list and all is well. Lesson learnt backups now in progress! > -Original Message- > From: Mailman-Users [mailto:mailman-users- > bounces+mpn=icabs.co...@python.org] On Behalf Of Mark Sapiro > Sent: Saturday, 14 April 2018 5:06 PM > To: mailman-users@python.org > Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25 > > On 04/14/2018 06:12 AM, Odhiambo Washington wrote: > > > > Here is what I would do: > ... > > The suggestions here are way too complicated. > > Do the following: > > Either run Mailman's > > bin/rmlist myproblemlist > > or just > > rm -r /usr/local/mailman/lists/myproblemlist/ > > These will do the same thing which is remove the list but not it's archives. > > Then recreate the list either via the web UI or Mailman's bin/newlist. > > Configure the list as desired and add the members. > > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list Mailman-Users@python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: > http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail- > archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman- > users/mpn%40icabs.co.zw -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bug in Mailman version 2.1.25
On 04/14/2018 06:12 AM, Odhiambo Washington wrote: > > Here is what I would do: ... The suggestions here are way too complicated. Do the following: Either run Mailman's bin/rmlist myproblemlist or just rm -r /usr/local/mailman/lists/myproblemlist/ These will do the same thing which is remove the list but not it's archives. Then recreate the list either via the web UI or Mailman's bin/newlist. Configure the list as desired and add the members. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bug in Mailman version 2.1.25
On 14 April 2018 at 15:33, MPN Kazishe wrote: > > -Original Message- > > From: Mailman-Users > [mailto:mailman-users-bounces+mpn=icabs.co...@python.org] On Behalf Of > Mark > Sapiro > > Sent: Friday, 13 April 2018 4:46 PM > > To: mailman-users@python.org > > Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25 > > > > Hopefully, you have a recent backup from before the outage with a good > /usr/local/mailman/lists/myproblemlist/config.pck file that you can > restore. > > > Unfortunately, I have no backups! How can I forcefully remove the list. My > only hope is in re-adding it. > > Many thanks. > Hi Kazishe, If your list has archives, you can re-use them, I believe. The fact that the config file is corrupt should not lead you to blow away the list and create it afresh. You can use another list as a template to create your corrupted list, I believe. You could lose the members, yes, but they will re-subscribe. Here is what I would do: 1. Export a working list configuration (a) /usr/local/mailman/bin/config_list -o working_listname > /tmp/listname.bak (b) vi /tmp/listname.bak and change the settings to match the name of the corrupted list. This is a text file, with comments explaining what is what :-) 2. Make a backup of the archives of the corrupted list for restore later (a) cd /usr/local/mailman/archives/private tar czf /tmp/corrupted_listname_private.tgz listname listname.mbox 3. Remove the corrupt list, recreate it, import configuration, restore the archives (a) /usr/local/mailman/bin/rmlist -a corrupt_listname # Blow it away (b) /usr/local/mailman/bin/newlist corrupt_listname # Recreate it (c) /usr/local/mailman/bin/config_list -i /tmp/listname.bak # Import the configuration (d) cd /usr/local/mailman/archives/private && tar yxvf /tmp/corrupted_listname_private.tgz # Restore the archives 4. Fix the permissions /usr/local/mailman/bin/check_perms -f Repeat this again just to be sure the permissions are fixed I hope I haven't forgotten a step, but that should give you a working list in a short time. Fix any subsequent errors. ASSUMPTION: Mailman on FreeBSD is installed in /usr/local/mailman/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft." -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bug in Mailman version 2.1.25
> -Original Message- > From: Mailman-Users [mailto:mailman-users-bounces+mpn=icabs.co...@python.org] On Behalf Of Mark Sapiro > Sent: Friday, 13 April 2018 4:46 PM > To: mailman-users@python.org > Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25 > > Hopefully, you have a recent backup from before the outage with a good /usr/local/mailman/lists/myproblemlist/config.pck file that you can restore. Unfortunately, I have no backups! How can I forcefully remove the list. My only hope is in re-adding it. Many thanks. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bug in Mailman version 2.1.25
On 04/13/2018 04:25 AM, MPN Kazishe wrote: > > Apr 13 13:04:49 2018 (58769) couldn't load config file > /usr/local/mailman/lists/myproblemlist/config.db.last > > [Errno 2] No such file or directory: > '/usr/local/mailman/lists/myproblemlist/config.db.last' > > Apr 13 13:04:49 2018 (58769) All myproblemlist fallbacks were corrupt, > giving up The /usr/local/mailman/lists/myproblemlist/config.pck file containing the list configuration, membership, etc. is corrupt. When this happens, Mailman tries in order /usr/local/mailman/lists/myproblemlist/config.pck.last /usr/local/mailman/lists/myproblemlist/config.db /usr/local/mailman/lists/myproblemlist/config.db.last the config.pck.last file is the immediately prior version and it too is apparently corrupt. The config.db and config.db.last files are artifacts from Mailman 2.0 and should not exist so the [Errno 2] No such file or directory: '/usr/local/mailman/lists/myproblemlist/config.db.last' is expected and normal in this situation. Hopefully, you have a recent backup from before the outage with a good /usr/local/mailman/lists/myproblemlist/config.pck file that you can restore. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
