zimbra 7.1.1: zmmailboxdctl is not running on cold standby server

[Rocky]

Hello,

I am running 7.1.1. on CentOS for our production server, and set up a standby server with hourly rsync /opt/zimbra to standby server following the steps here:Harley77-Backup - Zimbra :: Wiki . The standby server used to work well; But it broken after i upgraded both servers from 7.0.1 to 7.1.1 with P5. When i try to run "zmcontrol start" on standby server, the zmmailboxdctl could not start.


[zimbra@zimbra ~]$ zmcontrol start
Host zimbra.remotelyyours.com
Starting ldap...Done.
Starting zmconfigd...Done.
Starting logger...Done.
Starting convertd...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
[zimbra@zimbra ~]$ zmcontrol status
Host zimbra.remotelyyours.com
antispam Running
antivirus Running
convertd Running
ldap Running
logger Running
mailbox Stopped
zmmailboxdctl is not running.
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running

And i looked into /opt/zimbra/log/mailbox.log and found some Java.jdbc error:

"2011-09-09 11:35:07,495 INFO [main] [] system - Setting mysql connector property: maxActive=100
2011-09-09 11:35:07,767 FATAL [main] [] system - Config initialization failed
com.zimbra.common.service.ServiceException: system failure: getting all config entries
ExceptionId:main:1315582507765:ac7fbbdd3ac3456c
Code:service.FAILURE
.....

at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.start.Main.start(Main.java:441)
at org.mortbay.start.Main.main(Main.java:119)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientC onnectionException: Communications link failure
"

Anyone can help me with that? Maybe i need to upgrade to latest 7.1.2?

Thanks,
Rocky

[Rocky]

I just tried to upgraded standby server from 7.1.1 to 7.1.2, then the service start up. I guess it cleared out all the java odbc errors. Does it means i have to upgrade our production server from 7.1.1 to 7.1.2 as well?

Thanks,
Rocky