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 08-09-2010, 02:56 AM
Junior Member
 
Posts: 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
Reply With Quote
  #2 (permalink)  
Old 08-09-2010, 03:18 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
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
Reply With Quote
  #3 (permalink)  
Old 08-10-2010, 03:00 AM
Junior Member
 
Posts: 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
Reply With Quote
  #4 (permalink)  
Old 08-10-2010, 08:25 AM
Partner (VAR/HSP)
 
Posts: 425
Default

You should search the forums for database recovery.
Reply With Quote
  #5 (permalink)  
Old 08-10-2010, 06:44 PM
Junior Member
 
Posts: 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
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.