cpanel cron errors
After recent upgrade to 11.44 were getting following email errors;
[QUOTE]/usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs
Traceback (most recent call last):
File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 211, in
main()
File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 105, in main
discarded = auto_discard(mlist)
File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 200, in auto_discard
heldmsgs = mlist.GetHeldMessageIds()
File "/usr/local/cpanel/3rdparty/mailman/Mailman/ListAdmin.py", line 143, in GetHeldMessageIds
return self.__getmsgids(HELDMSG)
File "/usr/local/cpanel/3rdparty/mailman/Mailman/ListAdmin.py", line 138, in __getmsgids
ids = [k for k, (op, data) in self.__db.items() if op == rtype]
ValueError: need more than 0 values to unpack
Ideas to fix are welcome :)
Ideas to fix are welcome :)
-
Hello :) Are you using CageFS? If so, use a command such as "cagefsctl --list" to see if it's enabled for the mailman user. If it is, disable it via: cagefsctl --disable mailman
Thank you.0 -
Hi, We are using cagefs but mailman is not listed as enabled. 0 -
Please try running the following command and let us know if you notice any particular errors: /scripts/fixmailman
Thank you.0 -
The following errors occured: /scripts/fixmailman Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 802, in errors = main() File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 692, in main errors = errors + dolist(listname) File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 222, in dolist mlist._UpdateRecords() File "/usr/local/cpanel/3rdparty/mailman/Mailman/ListAdmin.py", line 579, in _UpdateRecords assert False, 'Unknown record format in %s' % self.__filename AssertionError: Unknown record format in /usr/local/cpanel/3rdparty/mailman/lists/domain.uk/request.pck Setting mailman permissions. Setting mailman lists permissions. Purging mailman queue. Restarting mailman.
Ah! looks like a problem with a clients domain mailing list . Removed the list and now no errors. Thanks Michael :)0 -
I am happy to see you were able to resolve the issue. Thank you for updating us with the outcome. 0 -
I am having a similar problem but don't want to delete the list as I own it and would prefer not to rebuild it. /scripts/fixmailman Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 802, in errors = main() File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 692, in main errors = errors + dolist(listname) File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 222, in dolist mlist._UpdateRecords() File "/usr/local/cpanel/3rdparty/mailman/Mailman/ListAdmin.py", line 579, in _UpdateRecords assert False, 'Unknown record format in %s' % self.__filename AssertionError: Unknown record format in /usr/local/cpanel/3rdparty/mailman/lists/xxx-exec_yyy.org/request.pck Setting mailman permissions. Setting mailman lists permissions. Purging mailman queue. Restarting mailman.0 -
Was the account associated with that mailing list backed up and restored at some point in the past? Thank you. 0 -
I'm also seeing this problem and I was wondering if anyone might be able to help. If I run `fixmailman` I get: [QUOTE]Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 802, in errors = main() File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 692, in main errors = errors + dolist(listname) File "/usr/local/cpanel/3rdparty/mailman/bin/update", line 222, in dolist mlist._UpdateRecords() File "/usr/local/cpanel/3rdparty/mailman/Mailman/ListAdmin.py", line 579, in _UpdateRecords assert False, 'Unknown record format in %s' % self.__filename AssertionError: Unknown record format in /usr/local/cpanel/3rdparty/mailman/lists/myList_domain.com/request.pck Setting mailman permissions. Setting mailman lists permissions. Purging mailman queue. Restarting mailman.
I have transferred the domain from one server to another, but it is not clear if it was working immediately after the transfer, or if it has cropped up since then (the list admin can't remember). How might this be resolved? Thanks, Allan0 -
Could you provide more information about the steps you have taken thus far? For instance, have you reviewed the previous replies to this thread (e.g. CageFS issue)? Thank you. 0 -
Sorry yes, I meant to mention CageFS - CageFS is not used on this machine. It is a CentOS 6.5 server with WHM 11.44.1 build 18 on it. I tried the fix mailman script as I indicated above, but it gives the error above. I also tried remove the `request.pck` file that the error mentions and also replacing it with an empty file, but always get the same error. Thanks, Allan 0 -
Were these accounts restored from backup at some point? Thank you. 0 -
They were transferred from one server to another, does that count as a backup and then restore? Thanks, Allan 0 -
Yes, transfers would also apply. Internal case number 109093 addresses this issue so it does not happen again, but it does not fix existing lists already effected by the issue. Have you tried removing the .pck file and not creating an empty one to see if the issue persists? Thank you. 0 -
Okay, I've renamed the file and then the `fixmailman`script and get a warning about not being able to acquire a lock: > WARNING: could not acquire lock for list: committee-list_myDomain.com I also get the same error as above about the unknown record format for another list. Fixing that results in above lock not being acquired and the next list showing the same issue. So before I got through all of the lists renaming the file to hide it, should I do something about the warning? 0 -
[quote="theallan, post: 1738081">So before I got through all of the lists renaming the file to hide it, should I do something about the warning?
You can proceed without addressing the "could not acquire lock" messages. Those should go away after accessing the mailing list. Thank you.0 -
Okay thanks - I've gone through all of the lists on the server and performed that action. When I run the fixmailman script now it completes without any errors (a few lock warnings) as above, but no errors. However, now when I try to access the mailman admindb page for a list it just hangs. Enter the password and then nothing. No errors in the mailman log and no abnormal load on the server. Reloading the access page and then entering the password again causes exactly the same again - just hangs. Thanks, Allan 0 -
Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Thanks - i've opened a ticket. Before I paste the id, I presume that only myself and cPanel staff can view the information in the ticket? Thanks, Allan 0 -
[quote="theallan, post: 1738741">Thanks - i've opened a ticket. Before I paste the id, I presume that only myself and cPanel staff can view the information in the ticket?
Yes, that is correct. Thanks.0 -
Super - thanks! Ticket id is 5507633. 0 -
Just had the same issue and ran /scripts/fixmailman It gave me the error and pointed it to a customers mailman folder. Logged into the customers account which was suspended funny enough and deleted the mailman list. All working again. 0 -
[quote="theallan, post: 1738871">Super - thanks! Ticket id is 5507633.
To update, the resolution suggested in this thread worked. The additional issue was just a cache issue on the local workstation, and is now resolved. Thank you.0
Please sign in to leave a comment.
Comments
22 comments