Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > General Zimbra > Announcements

Welcome to the Zimbra - Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack (1) Thread Tools Display Modes
  #51 (permalink)  
Old 11-29-2005, 12:00 PM
Zimbra Employee
 
Posts: 2,073
Default tables

The table in zimbra is no longer used, it's left over from previous versions.

I'll check out why you're not getting the status.
Reply With Quote
  #52 (permalink)  
Old 11-29-2005, 12:07 PM
Loyal Member
 
Posts: 95
Default

Quote:
Originally Posted by marcmac
The table in zimbra is no longer used, it's left over from previous versions.

I'll check out why you're not getting the status.
TIA. Please note that if I install M2 from scratch, "Server Status" just works, so I think maybe there is a bug in the upgrade script.

-g
Reply With Quote
  #53 (permalink)  
Old 11-29-2005, 12:24 PM
Zimbra Employee
 
Posts: 2,073
Default Possible causes

Are there an excpetions in /opt/zimbra/log/zimbra.log or tomcat/logs/catalinba.out?

An exception was thrown when trying to get connection to Logger database.

is the logger host defined in ldap? Check for zimbraLogHostname, it should be the same as the output of zmhostname on the logger host.
Reply With Quote
  #54 (permalink)  
Old 11-29-2005, 07:34 PM
Loyal Member
 
Posts: 95
Default

Quote:
Originally Posted by marcmac
Are there an excpetions in /opt/zimbra/log/zimbra.log or tomcat/logs/catalinba.out?

An exception was thrown when trying to get connection to Logger database.

is the logger host defined in ldap? Check for zimbraLogHostname, it should be the same as the output of zmhostname on the logger host.
I install all the packages in the same server so zimbraLogHostname and zmhostname just return the same value:

Quote:
[zimbra@ronaldo ~]$ zmprov gcf zimbraLogHostname
zimbraLogHostname: ronaldo.example.com
[zimbra@ronaldo ~]$ zmhostname
ronaldo.example.com
Yeah, there're tons of exeption in /opt/zimbra/log/zimbra.log but nothing show up in tomcat/logs/catalina.output:

Quote:
2005-11-30 10:48:54,822 INFO [http-7071-Processor49] [ip=220.231.81.139;name=thai.duong@example.com;] SoapEngine - handler exception
com.zimbra.cs.service.ServiceException: system failure: getting database logger connection
at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:99)
at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool .java:358)
at com.zimbra.cs.service.admin.GetServiceStatus.handl e(GetServiceStatus.java:67)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:249)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:226)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:526)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:825)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.processConnection(Http11Protocol.jav a:738)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:526)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused

STACKTRACE:

java.net.SocketException: java.net.ConnectException: Connection refused
at com.mysql.jdbc.StandardSocketFactory.connect(Stand ardSocketFactory.java:156)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:284)
at com.mysql.jdbc.Connection.createNewIO(Connection.j ava:2541)
at com.mysql.jdbc.Connection.<init>(Connection.java:1 474)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:266)
at java.sql.DriverManager.getConnection(DriverManager .java:525)
at java.sql.DriverManager.getConnection(DriverManager .java:193)
at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool .java:355)
at com.zimbra.cs.service.admin.GetServiceStatus.handl e(GetServiceStatus.java:67)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:249)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:226)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:526)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:825)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.processConnection(Http11Protocol.jav a:738)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:526)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)


** END NESTED EXCEPTION **



Last packet sent to the server was 2 ms ago.
at com.mysql.jdbc.Connection.createNewIO(Connection.j ava:2607)
at com.mysql.jdbc.Connection.<init>(Connection.java:1 474)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:266)
at java.sql.DriverManager.getConnection(DriverManager .java:525)
at java.sql.DriverManager.getConnection(DriverManager .java:193)
at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool .java:355)
... 23 more
I'm sure that the logger mysql is running because logmysql works. Please help.

-g
Reply With Quote
  #55 (permalink)  
Old 11-30-2005, 07:47 AM
Zimbra Employee
 
Posts: 2,073
Default logger db connection

You're not connecting to the logger db

zmlocalconfig | grep sql - what port is it running on? It should be 7307

Can you log into it from the command line? Try:
logmysql
use zimbra_logger;
show tables;
Reply With Quote
  #56 (permalink)  
Old 11-30-2005, 09:52 AM
Elite Member & Volunteer
 
Posts: 255
Default

I'm having the same issue with the statistics. I checked out the tables, and the majority of them are empty.
Reply With Quote
  #57 (permalink)  
Old 11-30-2005, 10:41 AM
Loyal Member
 
Posts: 95
Default

Quote:
Originally Posted by marcmac
You're not connecting to the logger db

zmlocalconfig | grep sql - what port is it running on? It should be 7307

Can you log into it from the command line? Try:
logmysql
use zimbra_logger;
show tables;
Hi marcmac,

Somehow the value of logger_mysql_port is 3307, maybe a bug huh or is it a configurable parameter at the installation stage?. I change it to 7307 and Server Status works like a charm. marcmac., special thanks or ur wonderful support.

Regards,

-g
Reply With Quote
  #58 (permalink)  
Old 12-15-2005, 10:10 AM
Zimbra Employee
 
Posts: 2,073
Default zmlocalconfig

use zmlocalconfig -e key=value to set this correctly

The config file is correct, which is a bug, because it should use the localconfig value, which is wrong. (It works, but shouldn't)...
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0