[SOLVED] server stats throwing java exception

[useopenid]

Release 5.0.18_GA_3011.RHEL5_20090707164432 CentOS5 FOSS edition
(we're planning on upgrading to 6.x next week...)

2010-02-24 17:31:34,486 INFO  [btpool0-6] [name=root@zmail01.peak.org;mid=4;ip=172.20.0.2;ua=ZimbraWebClient - FF3.0 (Mac);] soap - GetServiceStatusRequest
2010-02-24 17:31:34,511 INFO  [btpool0-6] [name=root@zmail01.peak.org;mid=4;ip=172.20.0.2;ua=ZimbraWebClient - FF3.0 (Mac);] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: getting service status
ExceptionId:btpool0-6:1267061494511:2c1de7894578f943
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
	at com.zimbra.cs.db.DbServiceStatus.getStatus(DbServiceStatus.java:74)
	at com.zimbra.cs.service.admin.GetServiceStatus.handle(GetServiceStatus.java:74)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:429)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:275)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:187)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:129)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:350)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
	at org.mortbay.jetty.Server.handle(Server.java:313)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.sql.SQLException: Table './zimbra_logger/service_status' is marked as crashed and should be repaired
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1573)
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665)
	at com.mysql.jdbc.Connection.execSQL(Connection.java:3124)
	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1149)
	at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1262)
	at com.zimbra.cs.db.DbServiceStatus.getStatus(DbServiceStatus.java:68)
	... 31 more

[phoenix]

Check some of these threads: site:zimbra.com +"system failure: getting service status" - Yahoo! Search Results

[useopenid]

It turned out to be that several tables were corrupt; on repair, all is well. Thanks!