No, checked that on his, his queue is empty. I'll update after tonight's cron to see if editing the user cron helps. In addition I edited today /etc/crontab and then restarted cron. Perhaps that was why it didn't work the first time, anyway shall soon see.
Well, editing the zimbra user crontab and adding to the beginning, like this:
seemed to work as I didn't get any error message this morning. Either that, or the reload of crontab after editing /etc/crontab, as I did both. Anyway, it's now fixed. I'll see if this stays after future upgrades, although it should do as it is outside of the ZIMBRASTART and ZIMBRAEND lines. Therefore if you do it, put it at the very beginning like I did.Code:SHELL=/bin/bash # ZIMBRASTART -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRAEND #
Great solution. Thanks for your help and testing through this problem.
Changing SHELL=/bin/sh to SHELL=/bin/bash in /etc/crontab and restarting cron service doesn't work. I tested it by simply creating cron job as zimbra user:
and the output was this:Code:* * * * * env > /tmp/env.txt # ZIMBRASTART -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRAEND #
Zimbra user's cron was still using sh.Code:LANGUAGE=en_US:en HOME=/opt/zimbra LOGNAME=zimbra PATH=/usr/bin:/bin LANG=en_US.UTF-8 SHELL=/bin/sh PWD=/opt/zimbra
Only after applying your last solution:
the output of the cron job was:Code:SHELL=/bin/bash * * * * * env > /tmp/env.txt # ZIMBRASTART -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRAEND #
Code:SHELL=/bin/bash PATH=/usr/bin:/bin PWD=/opt/zimbra LANG=en_US.UTF-8 SHLVL=1 HOME=/opt/zimbra LANGUAGE=en_US:en LOGNAME=zimbra _=/usr/bin/env
Last edited by ludus; 12-24-2013 at 06:45 AM.
There are currently 1 users browsing this thread. (0 members and 1 guests)