Page 6 of 6

M1 -> M2 Upgrade Scripts

Posted: Tue Nov 29, 2005 1:00 pm
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.

M1 -> M2 Upgrade Scripts

Posted: Tue Nov 29, 2005 1:07 pm
by 7323graffiti
[quote user="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.[/QUOTE]
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

M1 -> M2 Upgrade Scripts

Posted: Tue Nov 29, 2005 1:24 pm
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.

M1 -> M2 Upgrade Scripts

Posted: Tue Nov 29, 2005 8:34 pm
by 7323graffiti
[quote user="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.[/QUOTE]
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

[/quote]
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(ServiceException.java:99)

at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool.java:358)

at com.zimbra.cs.service.admin.GetServiceStatus.handle(GetServiceStatus.java:67)

at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:249)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:163)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:84)

at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:226)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709">HttpServlet.service(HttpServlet.java:709)

at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:148)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802">HttpServlet.service(HttpServlet.java:802)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)

at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)

at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)

at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)

at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.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(StandardSocketFactory.java:156)

at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2541)

at com.mysql.jdbc.Connection.(Connection.java:1474)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.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.handle(GetServiceStatus.java:67)

at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:249)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:163)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:84)

at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:226)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709">HttpServlet.service(HttpServlet.java:709)

at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:148)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:802">HttpServlet.service(HttpServlet.java:802)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)

at org.apache.catalina.core.StandardContextValve.invoke(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.invoke(StandardEngineValve.java:107)

at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)

at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)

at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.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.java:2607)

at com.mysql.jdbc.Connection.(Connection.java:1474)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.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
[/quote]
I'm sure that the logger mysql is running because logmysql works. Please help.
-g

M1 -> M2 Upgrade Scripts

Posted: Wed Nov 30, 2005 8:47 am
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;

M1 -> M2 Upgrade Scripts

Posted: Wed Nov 30, 2005 10:52 am
by rsharpe
I'm having the same issue with the statistics. I checked out the tables, and the majority of them are empty.

M1 -> M2 Upgrade Scripts

Posted: Wed Nov 30, 2005 11:41 am
by 7323graffiti
[quote user="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;[/QUOTE]
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

M1 -> M2 Upgrade Scripts

Posted: Thu Dec 15, 2005 11:10 am
by marcmac
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)...