MM2.1 daily checkdbs traceback
Hello,
I just upgraded a 2.0.13 installation to 2.1, and I'm getting the following traceback every morning when checkdbs is called. I get the same traceback when I run checkdbs manually. I don't think any of my databases are corrupt - I ran bin/check_db on each list and no problems were reported.
Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 136, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 98, in pending_requests for id in mlist.GetSubscriptionIds(): File "/home/mailman/Mailman/ListAdmin.py", line 157, in GetSubscriptionIds return self.__getmsgids(SUBSCRIPTION) File "/home/mailman/Mailman/ListAdmin.py", line 149, in __getmsgids ids = [k for k, (type, data) in self.__db.items() if type == rtype] ValueError: unpack tuple of wrong size
The system is OpenBSD 2.8 on a sparc, with a newly compiled python 2.2.2
any ideas?
Thanks,
Scott
PS: to the moderator: I sent this a day or so ago but was not subscribed - feel free to cancel the held posting, if you haven't already.
FYI - i traced this down to a corrupt requests.db file for one of my lists that had a pending subscription request before the 2.1 upgrade. It seems that ListAdmin.py's __opendb function attempts to upgrade the db file, but somewhere during my 2.1 install it looks like the requests.db file was partially upgraded - ie, it didn't have the full name field added, but it did have the version field. Therefore, opendb didn't try to add the full name field. I was able to look at the pending submission via 'strings requests.db' and then just kill the file, and now checkdbs runs fine.
Scott
On Wednesday, 8 Jan 2003, Scott Lipcon wrote:
FYI - i traced this down to a corrupt requests.db file for one of my lists that had a pending subscription request before the 2.1 upgrade. It seems that ListAdmin.py's __opendb function attempts to upgrade the db file, but somewhere during my 2.1 install it looks like the requests.db file was partially upgraded - ie, it didn't have the full name field added, but it did have the version field. Therefore, opendb didn't try to add the full name field. I was able to look at the pending submission via 'strings requests.db' and then just kill the file, and now checkdbs runs fine.
Scott
On Wednesday, 8 Jan 2003, Scott Lipcon wrote:
participants (1)
-
Scott Lipcon