We upgraded our single node/single volume cluster on Red Hat Enterprise Linux AS release 4 (Nahant Update 5) x86_64 from 4.5.11 -> 5.0.2.

Zimbra is up and running, but on the stanby node (zimbra1) we got strange behaviour; from the zimbra.log:

Code:
Mar 18 04:18:03 zimbra1 zimbramon[24939]: 24939:info: 2008-03-18 04:18:01, STATUS: : Unable: to 
Mar 18 04:18:03 zimbra1 sendmail[25148]: m2I3I3YW025148: from=zimbra, size=295, class=0, nrcpts=1, msgid=<200803180318.m2I3I3YW025148@zimbra1.xxx.xx>, rela
y=zimbra@localhost
Mar 18 04:18:03 zimbra1 sendmail[25148]: m2I3I3YW025148: to=zimbra, ctladdr=zimbra (1000/1000), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30295, rel
ay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1]
It seems that zimbra user's crontab is still active on the stanby node, and status check is still reporting service error every 2 minutes; in fact running as zimbra zmstatuslog we get:
Code:
Unable to determine enabled services from ldap.
I'd like know if it's a simple crontab problem or if there's an upgrade underlying problem that I must investigate.

Thanks in advance.