I have...several times. I kept getting the same result mailbox and logger would be stopped.
At this point my customers are running again, so I am wary of stopping it until the weekend officially arrives, which is a couple of more hours for you guys in California.
I get this though, if it helps, when I check zmlogger status:
[zimbra@membermail bin]$ ./zmlogger status
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 ./zmlogger line 44
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)
Cannot connect to local MySql server through socket?
I am cool now as the mailbox has come back to life. But I would prefer that the logger be running, though the zimbra.log is updating. I also feel moderately queasy about the fact that I revived the mailbox but don't know how I did it. Unanswered questions are always scary.  |