Results 1 to 5 of 5

Thread: Zimra not accesible

  1. #1
    heiituaku is offline Junior Member
    Join Date
    Nov 2008
    Posts
    6
    Rep Power
    6

    Default Zimra not accesible

    Hi All,

    Sorry if it is already solved in another thread.

    I have crashed Zimbra OSE 6.0.6 . After restart it became inaccesible (web client and web admin) I check the status zmcontrol status, everything running. I tried to upgrade to 6.0.7 wished the upgradeing process solve the problem, but idid not. Please tell me how to trouble shoot it

    Best Regards

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,201
    Rep Power
    56

    Default

    Quote Originally Posted by heiituaku View Post
    Sorry if it is already solved in another thread.
    It most likely is.

    Quote Originally Posted by heiituaku View Post
    I have crashed Zimbra OSE 6.0.6 . After restart it became inaccesible (web client and web admin) I check the status zmcontrol status, everything running.
    What do you mean by 'I crashed it....'?

    Quote Originally Posted by heiituaku View Post
    I tried to upgrade to 6.0.7 wished the upgradeing process solve the problem, but idid not.
    An upgrade is never likely to fix a problem like this, you're always better trying to debug the problem.

    Please tell me how to trouble shoot it[/QUOTE]You need to look in the log files to see what errors you have in there.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    heiituaku is offline Junior Member
    Join Date
    Nov 2008
    Posts
    6
    Rep Power
    6

    Default

    hi Bill,

    Sorry for my poor english. It was suddenly crash. I suspicious with this in log file
    "2010-08-08 10:40:28,617 FATAL [LmtpServer-5] [ip=192.168.1.212;] system - Unable to commit database transaction. Forcing server to abort.
    com.zimbra.common.service.ServiceException: system failure: committing database transaction
    ExceptionId:LmtpServer-5:1281238828617:cc03bf637ed31e7d
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:124)
    at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb ox.java:6746)
    at com.zimbra.cs.mailbox.Mailbox.getConfig(Mailbox.ja va:1257)
    at com.zimbra.cs.mailbox.Mailbox.finishInitialization (Mailbox.java:440)
    at com.zimbra.cs.mailbox.MailboxManager.getMailboxByI d(MailboxManager.java:483)
    at com.zimbra.cs.mailbox.MailboxManager.getMailboxByA ccountId(MailboxManager.java:336)
    at com.zimbra.cs.mailbox.MailboxManager.getMailboxByA ccount(MailboxManager.java:272)
    at com.zimbra.cs.mailbox.MailboxManager.getMailboxByA ccount(MailboxManager.java:231)
    at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:328 )
    at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:279 )
    at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver (ZimbraLmtpBackend.java:169)
    at com.zimbra.cs.lmtpserver.LmtpHandler.processMessag eData(LmtpHandler.java:365)
    at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDA TA(TcpLmtpHandler.java:72)
    at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHa ndler.java:350)
    at com.zimbra.cs.lmtpserver.LmtpHandler.processComman d(LmtpHandler.java:170)
    at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCom mand(TcpLmtpHandler.java:66)
    at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:175)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:132)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnect ionException: Communications link failure during commit(). Transaction resolution unknown.
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:888)
    at com.mysql.jdbc.Connection.commit(Connection.java:2 292)
    at com.zimbra.cs.db.DebugConnection.commit(DebugConne ction.java:42)
    at org.apache.commons.dbcp.DelegatingConnection.commi t(DelegatingConnection.java:301)
    at org.apache.commons.dbcp.PoolingDataSource$PoolGuar dConnectionWrapper.commit(PoolingDataSource.java:2 00)
    at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:122)
    ... 19 more"

    Regards

  4. #4
    iway is offline Partner (VAR/HSP)
    Join Date
    May 2008
    Posts
    432
    Rep Power
    6

    Default

    You should search the forums for database recovery.

  5. #5
    heiituaku is offline Junior Member
    Join Date
    Nov 2008
    Posts
    6
    Rep Power
    6

    Default

    thanks, and another thing i must do is tweaked the memory allocation. Since i upgrade to 6, it often crashed because run out of memory. My hardware is Xeon E3110 with 4GB RAM, previously i used dual Xeon 2.0GHz with 3GB RAM and ran smoothly.


    Regards

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. zimra on CenTOS domain name
    By esra in forum Migration
    Replies: 16
    Last Post: 03-05-2010, 02:55 AM
  2. [SOLVED] Will Zimra do what I need ?
    By babysnake in forum Installation
    Replies: 5
    Last Post: 01-14-2009, 03:40 AM
  3. Replies: 38
    Last Post: 08-15-2007, 11:45 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •