[SOLVED] GetServiceStatusRequest Failure

[mcheblak]

I've installed ZCS 5 [Debian 4 x86 package] and I'm running it on Debian Etch server. Everything was running good, until out of sudden i receive the following error when logging into the admin panel

Message: system failure: getting service status Error code: service.FAILURE Method: GetServiceStatusRequest Details:soap:Receiver

The daily report is:

Generating report
From 2008-04-22 00:00:00 to 2008-04-23 00:00:00

No messages found

any hint on how to fix this and re-activate the logger? will an upgrade from 5.0.4 to 5.0.5 fix this?

[phoenix]

Start here: Logger - Zimbra :: Wiki

[mcheblak]

#logmysql zimbra_logger

mysql> check table service_status;
+------------------------------+-------+----------+----------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------------+-------+----------+----------------------------------------------------------+
| zimbra_logger.service_status | check | warning | Table is marked as crashed |
| zimbra_logger.service_status | check | warning | 4 clients are using or haven't closed the table properly |
| zimbra_logger.service_status | check | error | Record at pos: 64 is not remove-marked |
| zimbra_logger.service_status | check | error | record delete-link-chain corrupted |
| zimbra_logger.service_status | check | error | Corrupt |
+------------------------------+-------+----------+----------------------------------------------------------+
5 rows in set (0.03 sec)

mysql> repair table service_status;
+------------------------------+--------+----------+------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------------+--------+----------+------------------------------------------------------+
| zimbra_logger.service_status | repair | warning | Duplicate key for record at 232 against record at 48 |
| zimbra_logger.service_status | repair | warning | Number of rows changed from 52 to 6 |
| zimbra_logger.service_status | repair | status | OK |
+------------------------------+--------+----------+------------------------------------------------------+
3 rows in set (0.04 sec)

mysql> repair table service_status;
+------------------------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------------------+--------+----------+----------+
| zimbra_logger.service_status | repair | status | OK |
+------------------------------+--------+----------+----------+
1 row in set (0.00 sec)

[nishith]

Dear Sir,

I am facing same problem regarding logmysql.server & mysql.server, these both services are not running.

su - zimbra
logmysql
ERROR 1045 (28000): Access denied for user 'zimbra'@'localhost' (using password: YES)

I am getting above error. COule you please suggest me how to solve this error?

Message: system failure: getting database logger connection Error code: service.FAILURE Method: GetServiceStatusRequest Details:soap:Receiver

[y@w]

Launch mysql with the exact same command mcheblak used ("logmysql zimbra_logger" instead of just "logmysql").

[nishith]

Dear Sir,

I can login mysql by using "logmysql zimbra_logger" command. Below is the final result of my problem.

I was facing problems of logmysql.server & mysql.server errors. Now,only I am getting this error by executing "zmcontrol status" command.

Below is the error.

Host webmail.renovau.net
antispam Running
antivirus Running
imapproxy Running
ldap Running
logger Running
mailbox Stopped
mysql.server is not running
mta Running
snmp Running
spell Running
stats Running


Kindly tell me what to do.

[y@w]

This is what happens when you do a "zmcontrol stop", "zmcontrol start"?

[nishith]

Dear Sir,

What is the suggestion posted by you? I can't understand.
Please send me any document link,so that I can sort out my problem.

[padraig]

it looks like Bug 33939 – 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: Too many connections

[phoenix]

Originally Posted by padraig

it looks like Bug 33939 – 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: Too many connections

The bug you've filed is probably a duplicate of this bug and you should try the fix mentioned in there.