problem with corrupt config.db (PR#223)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
High
|
Unassigned |
Bug Description
Jitterbug-Id: 223
Submitted-By: <email address hidden>
Date: Wed, 12 Apr 2000 18:31:22 -0400 (EDT)
Version: 1.0 c3 and upgraded to 2 beta2
OS: solaris 7
The list was runing just fine .. the last thing I did was deleting a user
and
resuscribing it
I did it yesterday, now in the syslog, it shows:
Apr 12 17:44:27 neblina postfix/
to=<email address hidden>, relay=local, delay=11, status=bounced
(Command
died with status 1: "/home/
reactecnicos".
Command output: Traceback (innermost last): File
"/home/
line 45, in ? mlist = MailList.
"/home/
self.Load() File
"/home/
Errors.
dictionary )
Apr 12 18:12:52 neblina postfix/
to=<email address hidden>, relay=local, delay=6, status=bounced
(Command
died with status 1: "/home/
reactecnicos".
Command output: Traceback (innermost last): File
"/home/
line 86, in ? main() File "/home/
line 43, in main
mlist = MailList.
"/home/
self.Load() File
"/home/
Errors.
Mailman.
List's config.db did not unmarshal into a dictionary )
in the errors file it logs:
Apr 12 17:39:22 2000 post: Traceback (innermost last):
post: File "/home/
post: mlist = MailList.
post: File "/home/
__init__
post: self.Load()
post: File "/home/
Load
post: raise Errors.
post: MMBadListError : Unmarshaled config info is not a dictionary
Apr 12 17:44:27 2000 post: Traceback (innermost last):
post: File "/home/
post: mlist = MailList.
post: File "/home/
__init__
post: self.Load()
post: File "/home/
Load
post: raise Errors.
post: MMBadListError : Unmarshaled config info is not a dictionary
everything points to a corrupted config.db but I dont know how to fix it
...
is there any tools to do that ... where is the documentation for this
cases?
I recreated the list but moved all the files to a diferente directory, so I
still
have the config.db file ...
thanks in advance ..
-Oswaldo
=======
Audit trail:
None
[http://
If both config.db and config.db.last are corrupt, there's little that can
be done. Note that Mailman 2.0b5 should be much more robust in the face of
these types of problems.