From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11pre) Gecko/20061023 SUSE/18.104.22.168-0.1 Firefox/22.214.171.124pre
Description of problem:
The file /etc/cron.d/mailman has this cron job entry:
0 8 * * * mailman /usr/lib/mailman/cron/checkdbs
This script produces the following error (and mail the output to firstname.lastname@example.org) every morning:
Traceback (most recent call last):
File "/usr/lib/mailman/cron/checkdbs", line 178, in ?
File "/usr/lib/mailman/cron/checkdbs", line 109, in main
text += '\n' + pending_requests(mlist)
File "/usr/lib/mailman/cron/checkdbs", line 128, in pending_requests
for id in mlist.GetSubscriptionIds():
File "/usr/lib/mailman/Mailman/ListAdmin.py", line 140, in GetSubscriptionIds
File "/usr/lib/mailman/Mailman/ListAdmin.py", line 132, in __getmsgids
ids = [k for k, (op, data) in self.__db.items() if op == rtype]
ValueError: unpack tuple of wrong size
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install and configure mailman
2. Wait for cron to run the script
3. su mailman -c /usr/lib/mailman/cron/checkdbs
Error code as described above
No error code
The maillist server are in others parts working fine and serves about 200 mailing lists
This seems to be the same as the following:
The method described in this article helped me to find a corrupt request.pck in
*one* of the lists on this server.
/usr/lib/mailman/bin/dumpdb ./request.pck on that file showed a lot of data but
I could not see anything strange (and if I had, I have no clue on how to fix this).
My solution was to remove the file. It is recreated when you "Tend to pending
moderator requests" in the web front-end.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.