[Mailman-Users] fix_url error

[Mark Sapiro]

Catherine Maxwell wrote:

>At 11:22 PM 9/29/2006, Mark Sapiro wrote:
>
>>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.)
>
>[----- 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.


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.

>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.


You previously wrote:

>These are the files that are on the server:
>
>-rw-rw----  1 mailman  mailman  216198 Sep 29 00:41 config.pck
>-rw-r-----  1 mailman  mailman   93225 Oct  3  2005 config.pck.bak
>-rw-rw----  1 mailman  mailman  216192 Sep 29 00:41 config.pck.last
>-rw-rw----  1 mailman  mailman   27421 Sep 28 20:04 digest.mbox
>-rw-rw----  1 mailman  mailman   11615 Sep 29 00:41 pending.pck
>-rw-rw-r--  1 mailman  mailman    6430 Sep 29 00:41 request.pck

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 at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan