4.5 Virtual Appliance, "no crontab for zimbra" error

[danfluidmind]

Hi all.

I just installed the VMware virtual appliance for Zimbra 4.5 beta. It seems to have installed alright, but when I reboot it none of the Zimbra services start up automatically. And, in the rPath log I see the following:

Failed: (Unknown Exception Type) Could not run '/opt/zimbra/libexec/zmsetup.pl -c /opt/zimbra/config.1989' no crontab for zimbra
Rebuilding backup cron no crontab for zimbra

Anyone know what's going on there?

Thanks
--Dan

[brian]

This is a known issue with the Virtual appliance beta (bug 11846). The error message is unrelated to zimbra not starting upon reboot.

The work around until this is fixed is to manually add the init script.

cp -f /opt/zimbra/libexec/zimbra /etc/init.d/zimbra
chkconfig --add zimbra
chkconfig zimbra on

[danfluidmind]

Thanks!

That got almost all of it started. Everything but the log. On the "Zimbra Servers" page it says: "zmlogswatchctl is not running".

--Dan

[brian]

/var/log/zimbra.log may not be readable by zimbra but to be sure that is the problem check /tmp/logswatch.out for any error messages.

[danfluidmind]

Originally Posted by brian

/var/log/zimbra.log may not be readable by zimbra but to be sure that is the problem check /tmp/logswatch.out for any error messages.

Thanks Brian. I just rebooted again. Waited a while, and checked the status page. Still shows "zmlogswatchctl is not running". Here's what's in the logswatch.out file:

*** logswatch version 3.1.1 (pid:1965) started at Wed Nov 29 10:56:52 UTC 2006

DBI connect('database=zimbra_logger;mysql_read_default _file=/opt/zimbra/conf/my.logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock','zimbra',...) failed: Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2) at /opt/zimbra/libexec/zmlogger line 47
DB: Can't connect to dbi:mysql:database=zimbra_logger;mysql_read_defaul t_file=/opt/zimbra/conf/my.logger.cnf;mysql_socket=/opt/zimbra/logger/db/mysql.sock: Can't connect to local MySQL server through socket '/opt/zimbra/logger/db/mysql.sock' (2)

[danfluidmind]

This is also odd:

In the rPath admin address (8003) under "Zimbra Services" is says:

logger Stopped
zmlogswatchctl is not running

Yet, when I login to the Zimbra admin address (7071) it shows a check mark beside the logger!

--Dan

[bobby]

if the logger service has stopped, and therefore stopped updating the logger database, the status display in the zimbra admin console, which is read from the logger database, is probably out of date. what is the output of these commands:

su - zimbra
cat /opt/zimbra/log/logswatch.pid
ps ax | grep logswatch
ps ax | grep logger
logmysqladmin status
logmysql zimbra_logger -e 'select * from service_status'