Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

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 Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-10-2008, 03:03 PM
Active Member
 
Posts: 39
Default Error Message on login into admin console

Zimbra: Release 5.0.0_GA_1869.UBUNTU6 UBUNTU6 NETWORK edition
OS: Ubuntu 6.06LTS

I am having problems with zimbra logger I think. When I login to the admin console (in Firefox) I get the following error message:

Code:
Message: system failure: getting database logger connection Error code: service.FAILURE Method: ZmCsfeCommand.prototype.invoke Details:soap:Receiver
Since I thought it was logger I tried zmcontrol start logger as zimbra but recieved this error message.

Code:
Starting logger...FAILED


        Starting mailbox...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...FAILED


        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.
and from /var/log/syslog - it says the logger is running:

Code:
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: antispam: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: antivirus: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: ldap: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: logger: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: mailbox: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: mta: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: snmp: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: spell: Running 
Mar 11 10:46:06 circuit zimbramon[25635]: 25635:info: 2008-03-11 10:46:02, STATUS: <HOSTNAME>: stats: Running
P.S. I have masked the server host name as <HOSTNAME>
Reply With Quote
  #2 (permalink)  
Old 03-10-2008, 03:13 PM
Active Member
 
Posts: 39
Default this maybe related to this problem

Maybe related to this problem I am still having despite following the directions in the post...

Error Message on login into admin console
Reply With Quote
  #3 (permalink)  
Old 03-17-2008, 08:27 PM
Active Member
 
Posts: 39
Default

bump bump bump
Reply With Quote
  #4 (permalink)  
Old 03-17-2008, 08:35 PM
Former Zimbran
 
Posts: 5,606
Default

Check
/opt/zimbra/log/mailbox.log for the error
Reply With Quote
  #5 (permalink)  
Old 03-17-2008, 08:38 PM
Active Member
 
Posts: 39
Default

Quote:
Originally Posted by jholder View Post
Check
/opt/zimbra/log/mailbox.log for the error
Code:
2008-03-18 16:31:41,366 INFO  [btpool0-8] [name=tim.wiel@<domainname>;ip=192.168.10.25;ua=ZimbraWebClient - FF2.0 (Linux);] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: getting database logger connection
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:183)
        at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool.java:314)
        at com.zimbra.cs.service.admin.GetServiceStatus.handle(GetServiceStatus.java:73)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:347)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:213)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:118)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)
        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:132)
        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:712)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
        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.RewriteHandler.handle(RewriteHandler.java:176)
        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:205)
        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: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Too many connections
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:921)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:812)
        at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:3269)
        at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1182)
        at com.mysql.jdbc.Connection.createNewIO(Connection.java:2644)
        at com.mysql.jdbc.Connection.<init>(Connection.java:1531)
        at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:207)
        at com.zimbra.cs.db.DbPool.getLoggerConnection(DbPool.java:311)
        ... 31 more
Reply With Quote
  #6 (permalink)  
Old 03-17-2008, 08:41 PM
Former Zimbran
 
Posts: 5,606
Default

[SOLVED] Daily reports stopped sending - Mysql Too many connections
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
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.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.