Results 1 to 3 of 3

Thread: Zimbra stop regulary since migration hardware and software migration

  1. #1
    Join Date
    Sep 2011
    Posts
    2
    Rep Power
    4

    Default Zimbra stop regulary since migration hardware and software migration

    Hello everybody,

    1st sorry for my bad english writing

    We use zimbra OSE since 3 year now without any problem in a openvz container on proxmox.

    2 weeks ago we decide to move on a new hardware configuration, with the same os and system : proxmox 1.9 on debian 5.0.8

    The migration was pretty simple by using the cluster system, the live container migration and an ipfailover.

    We also made an update of zimbra from 6.0.10 to 6.0.14 then 7.1.2 (and 7.1.3 since this week ^^)

    But since this hardware and software upgrade we got a lot of problems with our installation.

    The mailboxd service stop apparently randomly with those consequences : Mails are not delivered and all webmails access are crashed. We got a lot of stacktrace and hs_err_pid in the log directory and they are totaly differents on each crash.

    After a crash, we have to restart the services by hand and everything seem good until the next crash.

    I attach some crash log

    the last crash was this morning, i got this in the mailbox.log

    Code:
    2011-10-04 11:41:01,333 INFO  [btpool0-25://zimbra.exemple.com/service/soap/SendMsgRequest] [name=florent@exemple.com;mid=25;ip=195.200.180.51;ua=ZimbraWebClient - GC14 (Win)/7.1.3_GA_3346;] SoapEngine - handler exception
    com.zimbra.cs.mailbox.MailServiceException: try again: message send already in progress: 1317721219310
    ExceptionId:btpool0-25://zimbra.exemple.com/service/soap/SendMsgRequest:1317721261331:33031ea63a54e158
    Code:mail.TRY_AGAIN
    	at com.zimbra.cs.mailbox.MailServiceException.TRY_AGAIN(MailServiceException.java:475)
    	at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:142)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
    	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
    	at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	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:1157)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:326)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:583)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:986)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:414)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    yesterday after the upgrade to 7.1.3, i got this in the zmconfigd.log
    Code:
    Starting zmconfigd...zmconfigd is already running.
    2011-10-04 00:35:40,605 zmconfigd WARNING [15456-MainThread] Fetching All configs
    2011-10-04 00:35:40,871 zmconfigd WARNING [15456-MainThread] All configs fetched in 0.26 seconds
    2011-10-04 00:35:41,618 zmconfigd WARNING [15456-MainThread] Watchdog: service antivirus status is OK.
    2011-10-04 00:35:41,678 zmconfigd WARNING [15456-MainThread] All rewrite threads completed in 0.00 sec
    2011-10-04 00:35:41,678 zmconfigd WARNING [15456-MainThread] All restarts completed in 0.00 sec
    Starting zmconfigd...zmconfigd is already running.
    2011-10-04 00:36:41,690 zmconfigd WARNING [15456-MainThread] Fetching All configs
    2011-10-04 00:36:41,957 zmconfigd WARNING [15456-MainThread] All configs fetched in 0.27 seconds
    2011-10-04 00:36:42,697 zmconfigd WARNING [15456-MainThread] Watchdog: service antivirus status is OK.
    2011-10-04 00:36:42,759 zmconfigd WARNING [15456-MainThread] All rewrite threads completed in 0.00 sec
    2011-10-04 00:36:42,760 zmconfigd WARNING [15456-MainThread] All restarts completed in 0.00 sec
    Starting zmconfigd...zmconfigd is already running.
    2011-10-04 00:37:42,770 zmconfigd WARNING [15456-MainThread] Fetching All configs
    Starting zmconfigd...zmconfigd is already running.
    Starting zmconfigd...zmconfigd is already running.
    2011-10-04 00:39:42,839 zmconfigd CRITICAL [15456-MainThread] Thread mc still alive, waiting 60
    Starting zmconfigd...zmconfigd is already running.
    Check the zmmailboxd.log, I past only the strange line

    I'm totaly lost with all those information, and cannot found what happen to my beautyfull zimbra :'(

    Is anybody can help us with that ?

    Thank in advance Zimbra community
    Attached Files Attached Files

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by Tataragne View Post
    2 weeks ago we decide to move on a new hardware configuration, with the same os and system : proxmox 1.9 on debian 5.0.8
    I'm afraid I can't specifically help you with this as I know nothing about proxmox but I must point out that this is an unsupported environment - Zimbra may, or may not, work in this environment. Was this a conversion from 32bit to 64bit? The usual reason for problems with Zimbra in this environment are problems with insufficient RAM, how much is allocated to the server?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Sep 2011
    Posts
    2
    Rep Power
    4

    Default

    Proxmox is an openvz manager, I known that it's not a officially supported environnement, and you're right on the 64bit host to 32 bits guest VM. The guest machine has 8 Go of memory allocated, currently used around 4.7 Go. At the crash moment, zimbra still have free memory available (look into the attached logs).

Similar Threads

  1. Migration from one PC to another
    By gfdos.sys in forum Migration
    Replies: 7
    Last Post: 09-20-2007, 02:16 AM
  2. Hardware Specs, Zimbra Features
    By Markus23 in forum Migration
    Replies: 6
    Last Post: 07-31-2007, 07:32 AM

Posting Permissions

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