Yes, that I see. However, something is obviously not right, and is using sh instead. However:
shows that for the zimbra user the shell is bash. And:
verifies that this is the case. This is what the cron looks like for the zimbra user:
zimbra@mail:~$ echo $0
and when we run this manually as the zimbra user from the console:
45 0 * * * . /opt/zimbra/.bashrc; /opt/zimbra/libexec/zmsaupdate
it works as no error is reported. And yet, when the cron itself runs at night, I get the error.
. /opt/zimbra/.bashrc; /opt/zimbra/libexec/zmsaupdate
I've noticed that the /etc/crontab has a value:
so I've changed this for now to /bin/bash and will see if this makes a difference. Alternatively, at the beginning of the zimbra crontab outside of the "DO NOT EDIT" parts, I could specify the shell in here so that it would be set as a per-user basis. As now, set in /etc/crontab means that bash should be used system-wide. I'll report back later to see if this is the case.