mailbox.log filling disk after upgrade

Ask questions about your setup or get help installing ZCS server (ZD section below).
Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 11, 2018 7:04 pm

I have upgraded to Zimbra 8.8.8 from previous release and also upgraded from Ubuntu 14.04 to 16.04.
After Ubuntu upgrade I reinstalled Zimbra 8.8.8 (Ubuntu 16 version) over it.
All is working BUT my the logfiles is filling up the disk within a few hours.

Primary /opt/zimbra/log/mailbox.log is growing crazy fast (around 20GB within a few hours)
Also /opt/zimbra/log/trace_log.2018_04_11 (around 3-4GB during the same time).

Looking at the content of these logs I cannot direct tell that anything obvious is wrong.

I delete the files above and do a zmcontrol restart as a workaround for now.

Please help.


Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

Re: mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 18, 2018 6:16 am

Anyone..... :?:
Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

Re: mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 18, 2018 9:15 am

These are logged repeatedly in /opt/zimbra/log/mailbox.log

Can someone help me to identify the cause?

2018-04-18 11:10:13,099 WARN [qtp1595953398-1352:https:https://mail.xxxx.com/service/soap/] [name=xxxx@xxxx.com;mid=5;ip=192.168.1.34;port=57951;ua=Apple-iPhone9C3/1505.216(...bftcio) devip=192.168.1.161 ZPZB/66;soapId=7d1002a9;] SoapEngine - handler exception
com.zimbra.cs.mailbox.MailServiceException: WaitSet not found: WaitSet-ddf5106a-e7c7-4133-8113-06d7f477c7ee
ExceptionId:qtp1595953398-1352:https:https://mail.xxxx.com/service/soap/:1524042613099:8d60884355d11aad
Code:mail.NO_SUCH_WAITSET Arg:(id, STR, "WaitSet-ddf5106a-e7c7-4133-8113-06d7f477c7ee")
at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH_WAITSET(MailServiceException.java:335)
at com.zimbra.cs.session.WaitSetMgr.destroy(WaitSetMgr.java:165)
at com.zimbra.cs.service.mail.DestroyWaitSet.staticHandle(DestroyWaitSet.java:57)
at com.zimbra.cs.service.mail.DestroyWaitSet.handle(DestroyWaitSet.java:51)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:623)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:476)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:303)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:213)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
at com.zimbra.cs.servlet.CsrfFilter.doFilter(CsrfFilter.java:169)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.RequestStringFilter.doFilter(RequestStringFilter.java:54)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:59)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.ETagHeaderFilter.doFilter(ETagHeaderFilter.java:47)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.ContextPathBasedThreadPoolBalancerFilter.doFilter(ContextPathBasedThreadPoolBalancerFilter.java:107)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(ZimbraQoSFilter.java:116)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at com.zimbra.cs.servlet.ZimbraInvalidLoginFilter.doFilter(ZimbraInvalidLoginFilter.java:117)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:473)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:318)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:288)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:318)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:437)
at org.eclipse.jetty.server.handler.DebugHandler.handle(DebugHandler.java:84)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
at org.eclipse.jetty.server.Server.handle(Server.java:517)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:192)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
at java.lang.Thread.run(Thread.java:748)
Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

Re: mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 18, 2018 9:29 am

After some googling around I wnt to try to change the property: zimbra_waitset_max_per_account from 5 (dfault) to 10, but its failing..
How come?

zmprov ms mail.xxxx.com zimbra_waitset_max_per_account 10

ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: ldap host=mail.xxxx.com:389:zimbra_waitset_max_per_account: AttributeDescription contains inappropriate characters)
Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

Re: mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 18, 2018 1:05 pm

Ok, I was able to change it with:

zmlocalconfig -e zimbra_waitset_max_per_account=10
zmcontroldctl restart
Gr1pen
Posts: 17
Joined: Sat Oct 01, 2016 7:49 am

Re: mailbox.log filling disk after upgrade

Postby Gr1pen » Wed Apr 18, 2018 5:26 pm

Looks like that was the solution. After 6.5 hours the mailbox.log file is now 56 KB instead of 15-20 GB and the errors in the log are gone.

Return to “Installation and Upgrade”

Who is online

Users browsing this forum: No registered users and 9 guests