Re: [Mailman-Users] fix_url error
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Please include the list in your replies.
Catherine Maxwell wrote:
What does bin/list_lists report?
What does bin/check_perms run as root report?
What are the permissions on the lists/listname directory itself?
What does bin/dumpdb lists/listname/config.pck report? (You can elide all the membership info. In fact, if you get a reasonable looking report, you can just compare it to that of another list to verify that it looks good.)
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/a6afaaa7d0e4cf9885ac9c5b877b5d10.jpg?s=120&d=mm&r=g)
At 11:22 PM 9/29/2006, Mark Sapiro wrote:
What does bin/list_lists report?
It displays the listname there.
What does bin/check_perms run as root report?
It states: No problems found
What are the permissions on the lists/listname directory itself?
drwxrwsr-x 2 mailman mailman 512 Sep 30 02:49 listname
[----- start pickle file -----] [----- end pickle file -----]
All of the reports look fine except the program won't identify that the list exists. Conclusion: corrupted config.pck.
So I dug around and found a old config.pck for that list from last year and saved it to the lists/listname directory and -- wonders of wonders -- the list's webpages are all back including members and archives. The configuration needs to be updated but everything else is there. :) Now on to enjoy the rest of my weekend.
--Catherine
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Catherine Maxwell wrote:
If you are saying that the two lines
[----- start pickle file -----] [----- end pickle file -----]
were the entire output from bin/dumpdb, then I agree that config.pck was corrupt.
You previously wrote:
Is the config.pck.bak from Oct 3 2005 the one you used, or did you find one more recent than that?
I would be concerned about 2 things. The Oct 3 2005 file is less than half the size of the 'current' files. This is probably because that file has a lot fewer list members.
Also, the Sept 29 config.pck and config.pck.last are 6 bytes different in size. This suggests to me that the config.pck.last was successfully accessed and updated to produce the corrupt config.pck. Thus, I am surprised that it too is corrupt, but it does appear to be. Possibly your power outage caused the corruption 'outside' of Mailman - maybe some disk cache didn't get flushed.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/a6afaaa7d0e4cf9885ac9c5b877b5d10.jpg?s=120&d=mm&r=g)
At 11:22 PM 9/29/2006, Mark Sapiro wrote:
What does bin/list_lists report?
It displays the listname there.
What does bin/check_perms run as root report?
It states: No problems found
What are the permissions on the lists/listname directory itself?
drwxrwsr-x 2 mailman mailman 512 Sep 30 02:49 listname
[----- start pickle file -----] [----- end pickle file -----]
All of the reports look fine except the program won't identify that the list exists. Conclusion: corrupted config.pck.
So I dug around and found a old config.pck for that list from last year and saved it to the lists/listname directory and -- wonders of wonders -- the list's webpages are all back including members and archives. The configuration needs to be updated but everything else is there. :) Now on to enjoy the rest of my weekend.
--Catherine
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
Catherine Maxwell wrote:
If you are saying that the two lines
[----- start pickle file -----] [----- end pickle file -----]
were the entire output from bin/dumpdb, then I agree that config.pck was corrupt.
You previously wrote:
Is the config.pck.bak from Oct 3 2005 the one you used, or did you find one more recent than that?
I would be concerned about 2 things. The Oct 3 2005 file is less than half the size of the 'current' files. This is probably because that file has a lot fewer list members.
Also, the Sept 29 config.pck and config.pck.last are 6 bytes different in size. This suggests to me that the config.pck.last was successfully accessed and updated to produce the corrupt config.pck. Thus, I am surprised that it too is corrupt, but it does appear to be. Possibly your power outage caused the corruption 'outside' of Mailman - maybe some disk cache didn't get flushed.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Catherine Maxwell
-
Mark Sapiro