Mailman Digests broken after 58 Update

brianc

• August 20, 2016 17:19

Servers that are upgraded to version 58 will find out that the cronjob for mailman has been erased. This will break the sending out of digests. When I discovered this, I re-added the cronjob using the script at ../mailman/cron/crontab.in. However this is not working either. The cronjob is running according to /var/log/cron but digests are not being sent out. I then noticed there is a difference in the command line for the cron entry that handles the sending out of digests: New: 0 12 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests Previous: 0 12 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests Can someone else confirm this and can I get cPanel to look into this? The fact that the original cronjob was erased after the upgrade is problematic and has caused me a big headache! Not very good quality control if you ask me.

• 

  cPanelMichael

  • August 23, 2016 20:09

  Hello, The following resolution in cPanel 58.0.24 should address this issue: Fixed case CPANEL-8109: rlimits for a service will only be set when starting it. You can review the full change log, information on updating cPanel/WHM, and information on the build/release process at:

  0
• 

  kernow

  • August 31, 2016 15:58

  Nope, were running 58.0.25 and still get that problem. Will change the cron entry to the temp one suggested above and see if that fixes it.

  0
• 

  cPanelMichael

  • September 06, 2016 20:07

  Nope, were running 58.0.25 and still get that problem.

  
  Please let us know the output when running the following command as root via SSH:
  sudo -Hu mailman /scripts/restartsrv_mailman --status
  Thank you.

  0
• 

  kernow

  • September 08, 2016 12:34

  It returns: mailman (/usr/bin/python /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s start) is running as mailman with PID 771072 (pidfile check method)
  

  0
• 

  cPanelMichael

  • September 08, 2016 15:44

  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
• 

  kernow

  • September 11, 2016 15:32

  We managed to fix this ourselves after running both of the following commands:
  /usr/local/cpanel/3rdparty/mailman/bin/check_perms -f
  And
  /scripts/fixmailman
  

  0

Please sign in to leave a comment.