MTA shuts down, mail within domain still works.

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Wed Dec 05, 2018 8:50 am

This is a 4 year old install on Ubuntu 14.04, 8 core server with 32 gigs of RAM and 144 mail accounts averaging 6500ish emails per day.

We have a filtering service so all traffic comes from them through the MTA connection. On a normal business day it has started shutting down and will not receive email. Emails from domain user to domain user work fine, and sending email works fine. Sometimes doing a zmcontrol restart fixes the issue for a while, sometimes I have to reboot the entire machine.


Code: Select all

zimbra@MAIL:/$ zmcontrol -v
Release 8.8.9.GA.2055.UBUNTU14.64 UBUNTU14_64 FOSS edition, Patch 8.8.9_P8.


From mail.err

Code: Select all

Dec  4 10:27:03 MAIL zmmailboxdmgr[20544]: no manager process is running
Dec  4 10:33:55 MAIL zmmailboxdmgr[3061]: no manager process is running
Dec  4 11:14:03 MAIL zmmailboxdmgr[1413]: no manager process is running
Dec  4 11:14:03 MAIL zmmailboxdmgr[1455]: no manager process is running
Dec  4 11:14:04 MAIL zmmailboxdmgr[1531]: no manager process is running
Dec  4 11:14:04 MAIL zmmailboxdmgr[1548]: no manager process is running
Dec  4 11:14:04 MAIL zmmailboxdmgr[1565]: no manager process is running
Dec  4 11:14:52 MAIL zmmailboxdmgr[3315]: no manager process is running




From zmmailboxd.out, its filled with these

Code: Select all

2018-12-04 00:00:01.995:INFO:oejm.ThreadMonitor:Thread-37: Thread 'ImapSSLServer-177'[RUNNABLE,id:8217,cpu:96.81%] SPINNING
2018-12-04 00:00:01.995:WARN:oejm.ThreadMonitor:Thread-37:
org.eclipse.jetty.monitor.thread.ThreadMonitorException: Thread 'ImapSSLServer-177'[RUNNABLE,id:8217,cpu:96.81%] STACK TRACE
   at java.lang.String.toUpperCase(String.java:2765)
   at java.lang.String.toUpperCase(String.java:2833)
   at com.zimbra.cs.imap.ImapHandler.getFolderAttrs(ImapHandler.java:2428)
   at com.zimbra.cs.imap.ImapHandler.doLIST(ImapHandler.java:2233)
   at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:733)
   at com.zimbra.cs.imap.NioImapHandler.processRequest(NioImapHandler.java:123)
   at com.zimbra.cs.imap.NioImapHandler.messageReceived(NioImapHandler.java:63)
   at com.zimbra.cs.server.NioHandlerDispatcher.messageReceived(NioHandlerDispatcher.java:95)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
   at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:427)
   at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:245)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
   at com.zimbra.cs.server.NioLoggingFilter.messageReceived(NioLoggingFilter.java:68)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
   at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
   at org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:75)
   at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
   at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTask(OrderedThreadPoolExecutor.java:780)
   at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTasks(OrderedThreadPoolExecutor.java:772)
   at org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.run(OrderedThreadPoolExecutor.java:714)
   at java.lang.Thread.run(Thread.java:748)




Between 10:08 and 10:38 today there is zero traffic from my filtering service but all other traffic looks normal. When they try and telnet in they get a "refused" error but I cannot find one in the logs. This is strange because if I remove them from the MTA I get a normal "denied" entry in the logs like this.

Code: Select all

root@MAIL:/var/log# grep denied zimbra.log
Oct 11 06:54:14 MAIL postfix/smtpd[22770]: NOQUEUE: reject: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: 554 5.7.1 >: Relay access denied; from=> to=> proto=ESMTP helo=<mail.filter.com>



I have nothing like that in today's log. The last of the "normal" traffic ends with a "Recipient address rejected" which is expected, its an employee that no longer works here. I filtered the log by the name of the filtering service and the only strange thing I can see right before it started rejecting traffic is this part about "timeout after END-OF-MESSAGE". This is the only place in the entire log that this shows up, but I did not receive anything from the filtering service after this. In the full log you can still see traffic going between local accounts and going out to other domains, but nothing coming in. And you can see when I performed a reboot and it goes through the normal process, but nothing from my filtering service at all between 10:08 and the reboot. Then it failed again at 10:48 with the same messages in the log and forced another boot which I did at 11:14. Then it was fine the rest of the day.


Code: Select all

Dec  4 10:03:32 MAIL postfix/smtpd[7841]: NOQUEUE: reject: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: 550 5.1.1 <old.employee@domain.com>: Recipient address rejected: domain.com; from=<winter.resistant.vest@crodders.com> to=<old.employee@domain.com> proto=ESMTP helo=<mail.filter.com>
Dec  4 10:03:32 MAIL postfix/smtpd[7841]: NOQUEUE: reject: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: 550 5.1.1 <old.employee@domain.com>: Recipient address rejected: domain.com; from=<winter.resistant.vest@crodders.com> to=<old.employee@domain.com> proto=ESMTP helo=<mail.filter.com>
Dec  4 10:03:32 MAIL postfix/smtpd[7827]: 0914EC9E006A: client=mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:03:32 MAIL postfix/smtpd[7861]: 09437C9E006B: client=mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:31 MAIL postfix/smtpd[7821]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:31 MAIL postfix/smtpd[7821]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=1/2 data=1/2 rset=2 commands=7/9
Dec  4 10:08:31 MAIL postfix/smtpd[7818]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:31 MAIL postfix/smtpd[7818]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[7843]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7843]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[7847]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7847]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[7829]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7829]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[7820]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7820]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[5647]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[5647]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=2 data=2 rset=1 commands=8
Dec  4 10:08:32 MAIL postfix/smtpd[7832]: timeout after RSET from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7832]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=1/2 data=1/2 rset=2 commands=7/9
Dec  4 10:08:32 MAIL postfix/smtpd[7841]: timeout after RSET from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7841]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=1/2 data=1/2 rset=2 commands=7/9
Dec  4 10:08:32 MAIL postfix/smtpd[7861]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7819]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7861]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Dec  4 10:08:32 MAIL postfix/smtpd[7819]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=4 rcpt=2/4 data=2/4 rset=5 commands=14/18
Dec  4 10:08:32 MAIL postfix/smtpd[7830]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7830]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=2 data=2 rset=1 commands=8
Dec  4 10:08:32 MAIL postfix/smtpd[7825]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7825]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=2 data=2 rset=1 commands=8
Dec  4 10:08:32 MAIL postfix/smtpd[7827]: timeout after END-OF-MESSAGE from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:08:32 MAIL postfix/smtpd[7827]: disconnect from mail.filter.com[xxx.xxx.xxx.xxx] ehlo=1 mail=2 rcpt=2 data=2 rset=1 commands=8
Dec  4 10:38:31 MAIL postfix/smtpd[5885]: connect from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:38:31 MAIL postfix/smtpd[7311]: connect from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:38:31 MAIL postfix/smtpd[7310]: connect from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:38:31 MAIL postfix/smtpd[7312]: connect from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:38:31 MAIL postfix/smtpd[7313]: connect from mail.filter.com[xxx.xxx.xxx.xxx]
Dec  4 10:38:31 MAIL postfix/smtpd[5885]: NOQUEUE: filter: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: <return_0_23645497894_23622487125@texasdebrazil.fbmta.com>: Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026; from=<return_0_23645497894_23622487125@texasdebrazil.fbmta.com> to=<current.employee@domain.com> proto=ESMTP helo=<mail.filter.com>


GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

Re: MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Fri Dec 14, 2018 10:55 pm

No thoughts at all? Its been ok most of this week, and have had to boot it 5-6 times today.
lytledd
Outstanding Member
Outstanding Member
Posts: 491
Joined: Sat Sep 13, 2014 12:54 am
ZCS/ZD Version: Ubuntu Release 8.8.11.GA.P3 FOSS

Re: MTA shuts down, mail within domain still works.

Postby lytledd » Sat Dec 15, 2018 11:38 am

I'd update to 8.8.10 P4 before trying to diagnose this,

Doug
axslingr
Advanced member
Advanced member
Posts: 117
Joined: Sat Sep 13, 2014 2:20 am
ZCS/ZD Version: Release 8.8.9.GA.3019.UBUNTU14.64

Re: MTA shuts down, mail within domain still works.

Postby axslingr » Sat Dec 15, 2018 5:30 pm

GrnEyedDvl wrote:This is strange because if I remove them from the MTA I get a normal "denied" entry in the logs like this.

Code: Select all

root@MAIL:/var/log# grep denied zimbra.log
Oct 11 06:54:14 MAIL postfix/smtpd[22770]: NOQUEUE: reject: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: 554 5.7.1 >: Relay access denied; from=> to=> proto=ESMTP helo=<mail.filter.com>



This is the part I don't understand. Are you requiring your filtering service to authenticate to your server? Does the service not send email over port 25 like any other email server?

Lance
GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

Re: MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Sun Dec 16, 2018 12:41 pm

lytledd wrote:I'd update to 8.8.10 P4 before trying to diagnose this,

Doug

I can do that but upgrading to 8.8.9 didnt help.






axslingr wrote:
GrnEyedDvl wrote:This is strange because if I remove them from the MTA I get a normal "denied" entry in the logs like this.

Code: Select all

root@MAIL:/var/log# grep denied zimbra.log
Oct 11 06:54:14 MAIL postfix/smtpd[22770]: NOQUEUE: reject: RCPT from mail.filter.com[xxx.xxx.xxx.xxx]: 554 5.7.1 >: Relay access denied; from=> to=> proto=ESMTP helo=<mail.filter.com>



This is the part I don't understand. Are you requiring your filtering service to authenticate to your server? Does the service not send email over port 25 like any other email server?

Lance

Sorry if I wasnt clear enough here. Its a standard port 25 setup with iptables (ufw) open to their ports

When this thing locks up, their server reports a "denied" message but I have nothing in my logs about it, and mail piles up on the filtering server until I reboot my server.

However if I remove them from the "Inbound SMTP Hostname" in the admin control panel or via command line I get a "Denied" message in my logs just like I would expect, and mail piles up on their server until I add it back in and it can be delivered.

So in one case I get it logged like I am supposed to. When it fails there is nothing logged. Its not in fail2ban (whitelisted and no logs about blocking traffic) and even if I completely disable ufw and fail2ban and open port 25 to the entire world they still get a denied message, until I boot.


This is in mail.err, but looking in the other logs at the same time isnt giving me any clues. If you run a zmcontrol status everything shows as up.

Code: Select all

Dec 14 10:03:30 MAIL postfix/postqueue[10740]: fatal: Queue report unavailable - mail system is down
Dec 14 10:04:00 MAIL postfix/postqueue[10931]: fatal: Queue report unavailable - mail system is down
Dec 14 10:04:03 MAIL zmmailboxdmgr[11079]: no manager process is running
Dec 14 10:04:03 MAIL zmmailboxdmgr[11125]: no manager process is running
Dec 14 10:04:04 MAIL zmmailboxdmgr[11207]: no manager process is running
Dec 14 10:04:04 MAIL zmmailboxdmgr[11224]: no manager process is running
Dec 14 10:04:04 MAIL zmmailboxdmgr[11241]: no manager process is running
Dec 14 10:04:05 MAIL zmmailboxdmgr[11264]: no manager process is running
Dec 14 10:04:05 MAIL zmmailboxdmgr[11288]: no manager process is running
Dec 14 10:04:05 MAIL zmmailboxdmgr[11312]: no manager process is running
Dec 14 10:04:06 MAIL /postfix-script[11391]: fatal: the Postfix mail system is not running
axslingr
Advanced member
Advanced member
Posts: 117
Joined: Sat Sep 13, 2014 2:20 am
ZCS/ZD Version: Release 8.8.9.GA.3019.UBUNTU14.64

Re: MTA shuts down, mail within domain still works.

Postby axslingr » Sun Dec 16, 2018 8:28 pm

I guess I'm confused at to why your email server thinks the filtering service is trying to relay to a domain it's supposed to be receiving for. What's your output for these:

Code: Select all

[zimbra@mail ~]$ postconf mydestination
mydestination = localhost
[zimbra@mail ~]$ postconf mynetworks   
mynetworks = 127.0.0.0/8 [::1]/128 xxx.xxx.xxx.xxx/24
[zimbra@mail ~]$ postconf mydomain 
mydomain = mydomain.com


Lance
GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

Re: MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Wed Dec 26, 2018 3:19 am

Code: Select all

zimbra@MAIL:/$ postconf mydestination
mydestination = localhost
zimbra@MAIL:/$ postconf mynetworks
mynetworks = 127.0.0.0/8 208.69.72.0/24 38.116.133.0/25 10.8.1.0/24 50.21.186.0/24 159.203.92.0/24 138.197.57.0/24
zimbra@MAIL:/$ postconf mydomain
mydomain = thisiscorrect.com


I left the IPs, no real harm in that since these are all public mail servers anyways except for that 208 IP, that one is not there anymore. The strange thing here is that they have all been removed via the web interface and it has been booted several times since, the MTA Trusted Networks box is empty.
Image




The Inbound SMTP host name is the filtering service. As I said, if I remove that I get a "Rejected" or "Denied" message in logs, just as you would expect. But when this thing shuts down they get a connection denied message on their end but I get nothing in my logs.


There is something definitely going on with this machine, today I removed the "Relay MTA for external delivery" and left it blank, and restarted the service just to see what happened if I removed the relay service completely for both incoming and outgoing mail so I could skip a step and see if I still had a problem. Mail would not send at all, it just stacked up in the queue with a timeout error in the log.

Code: Select all

Dec 25 07:48:38 MAIL postfix/smtp[24819]: 71186C9E004F: to=<name@domain.com>, relay=none, delay=30, delays=0.04/0/30/0, dsn=4.4.1, status=deferred (connect to name.com[xxx.xxx.xxx.203]:25: Connection timed out)


In my experience that is either caused by a DNS problem or a problem with port 25. I know that neither one of those is the case this time, but I could not figure out why it would not send. DNS is obviously working, it posted the correct IP address in the log. I know port 25 is not blocked by the ISP for several reasons. Mainly that this is a Comcast business fiber connection and that both the sending machine and the receiving machine are on the same Comcast subnet in the same rack and have only one digit difference in IP address. Both machines are running Zimbra, both use Google for DNS (8.8.8.8 and 8.8.4.4) one sends with the external relay left blank, one does not.
axslingr
Advanced member
Advanced member
Posts: 117
Joined: Sat Sep 13, 2014 2:20 am
ZCS/ZD Version: Release 8.8.9.GA.3019.UBUNTU14.64

Re: MTA shuts down, mail within domain still works.

Postby axslingr » Wed Dec 26, 2018 4:50 pm

Those look like Global Settings. What do the MTA settings look like on Configure > Servers? Have you tried configuring everything here instead of global settings?

Lance
GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

Re: MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Fri Jan 11, 2019 1:58 am

Sorry for the slow reply, I was out of town.

axslingr wrote:Those look like Global Settings. What do the MTA settings look like on Configure > Servers? Have you tried configuring everything here instead of global settings?

Lance

I did find a setting in the Serve that didnt match Global, that fixed this problem. No idea who set it, but it was there.


Things ran normally for a few days while I was gone, then I was booting the server a couple of times a day from my phone so I couldnt really diagnose anything. Mon and Tues we had no problems. Today I had to boot the server 11 times. But I did finally see something new in the logs.

Also, it has been updated

Code: Select all

zimbra@MAIL:/var/log$ zmcontrol -v
Release 8.8.11.GA.3737.UBUNTU14.64 UBUNTU14_64 FOSS edition, Patch 8.8.11_P1.


I have 100,000 lines of this in /opt/zimbra/log/zmmailboxd.out.

Code: Select all

2019-01-10 18:33:17.129:INFO:oejm.ThreadMonitor:Thread-36: Thread 'ImapSSLServer-0'[RUNNABLE,id:74,cpu:98.64%] SPINNING
2019-01-10 18:33:17.129:WARN:oejm.ThreadMonitor:Thread-36:
org.eclipse.jetty.monitor.thread.ThreadMonitorException: Thread 'ImapSSLServer-0'[RUNNABLE,id:74,cpu:98.64%] STACK TRACE




I also have lots of stuff like this in mailbox.log

Code: Select all

2019-01-10 06:53:45,640 WARN  [qtp66233253-8350:https:https://mail.domain.com/service/soap/ZxChatRequest] [name=ron@domain.com;mid=19;ip=50.204.193.193;port=51730;ua=ZimbraWebClient - GC71 (Win)/8.8.11_GA_3737;soapId=63127510;] session - error encoding item -380514
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.m.zmain._jspx_meth_mo_005fhandleError_005f1(zmain.java:2459)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag._jspx_meth_c_005fcatch_005f0(moHandleError_tag.java:206)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.tag.web.mobile.moHandleError_tag.doTag(moHandleError_tag.java:138)
   at org.apache.jsp.m.zmain._jspx_meth_mo_005fhandleError_005f2(zmain.java:4504)


And this in /var/log/mail.err which I have always had.

Code: Select all

Jan 10 17:28:07 MAIL zmmailboxdmgr[1396]: no manager process is running
Jan 10 17:28:07 MAIL zmmailboxdmgr[1438]: no manager process is running
Jan 10 17:28:08 MAIL zmmailboxdmgr[1514]: no manager process is running
Jan 10 17:28:08 MAIL zmmailboxdmgr[1531]: no manager process is running
Jan 10 17:28:08 MAIL zmmailboxdmgr[1548]: no manager process is running
Jan 10 17:28:53 MAIL zmmailboxdmgr[3288]: no manager process is running
Jan 10 17:53:02 MAIL zmmailboxdmgr[23004]: no manager process is running
Jan 10 17:53:02 MAIL zmmailboxdmgr[23028]: no manager process is running
Jan 10 17:53:02 MAIL zmmailboxdmgr[23052]: no manager process is running
Jan 10 17:53:26 MAIL zmmailboxdmgr[23424]: no manager process is running
Jan 10 17:54:02 MAIL zmmailboxdmgr[24767]: no manager process is running
Jan 10 17:54:03 MAIL zmmailboxdmgr[24809]: no manager process is running
Jan 10 17:54:03 MAIL zmmailboxdmgr[24885]: no manager process is running
Jan 10 17:54:03 MAIL zmmailboxdmgr[24916]: no manager process is running
Jan 10 17:54:04 MAIL zmmailboxdmgr[24980]: no manager process is running
Jan 10 17:54:10 MAIL zmmailboxdmgr[25441]: no manager process is running
Jan 10 18:00:02 MAIL postfix/postqueue[1331]: fatal: Queue report unavailable -                                                                                                                                                              mail system is down
Jan 10 18:00:07 MAIL zmmailboxdmgr[1517]: no manager process is running
Jan 10 18:00:07 MAIL zmmailboxdmgr[1559]: no manager process is running
Jan 10 18:00:08 MAIL zmmailboxdmgr[1656]: no manager process is running
Jan 10 18:00:08 MAIL zmmailboxdmgr[1673]: no manager process is running
Jan 10 18:00:08 MAIL zmmailboxdmgr[1690]: no manager process is running
Jan 10 18:00:41 MAIL zmmailboxdmgr[3431]: no manager process is running
Jan 10 18:05:30 MAIL postfix/postqueue[7390]: fatal: Queue report unavailable -                                                                                                                                                              mail system is down
Jan 10 18:06:03 MAIL postfix/postqueue[8718]: fatal: Queue report unavailable -                                                                                                                                                              mail system is down
Jan 10 18:10:20 MAIL zmmailboxdmgr[12266]: no manager process is running
Jan 10 18:10:21 MAIL zmmailboxdmgr[12290]: no manager process is running
Jan 10 18:10:21 MAIL zmmailboxdmgr[12314]: no manager process is running
Jan 10 18:10:44 MAIL zmmailboxdmgr[12683]: no manager process is running
Jan 10 18:11:26 MAIL zmmailboxdmgr[14426]: no manager process is running
Jan 10 18:20:55 MAIL zmmailboxdmgr[20855]: no manager process is running
Jan 10 18:20:55 MAIL zmmailboxdmgr[20879]: no manager process is running
Jan 10 18:20:56 MAIL zmmailboxdmgr[20903]: no manager process is running
Jan 10 18:21:19 MAIL zmmailboxdmgr[21273]: no manager process is running
Jan 10 18:22:02 MAIL zmmailboxdmgr[23531]: no manager process is running
Jan 10 18:22:02 MAIL zmmailboxdmgr[23571]: no manager process is running
Jan 10 18:22:03 MAIL zmmailboxdmgr[23647]: no manager process is running
Jan 10 18:22:03 MAIL zmmailboxdmgr[23664]: no manager process is running
Jan 10 18:22:04 MAIL zmmailboxdmgr[23681]: no manager process is running
Jan 10 18:22:49 MAIL zmmailboxdmgr[25426]: no manager process is running
Jan 10 18:28:07 MAIL zmmailboxdmgr[1393]: no manager process is running
Jan 10 18:28:07 MAIL zmmailboxdmgr[1435]: no manager process is running
Jan 10 18:28:08 MAIL zmmailboxdmgr[1511]: no manager process is running
Jan 10 18:28:08 MAIL zmmailboxdmgr[1528]: no manager process is running
Jan 10 18:28:08 MAIL zmmailboxdmgr[1545]: no manager process is running
Jan 10 18:29:00 MAIL zmmailboxdmgr[3290]: no manager process is running
jwildman@MAIL:/var/log$ sudo -s
GrnEyedDvl
Posts: 11
Joined: Wed Dec 05, 2018 7:34 am

Re: MTA shuts down, mail within domain still works.

Postby GrnEyedDvl » Fri Jan 11, 2019 3:16 am

A small addition here. The MTA has been shutting down at pretty much all hours of the day. Between 6:00 and 7:00 tonight I booted the machine probably 3-4 times and it would run for 10 minutes and start catching up on its backlog from the filtering service, then it would die again.

Since ImapSSLServer errors started at basically midnight, and ran up until 7:14 PM when I last checked the logs, I decided I would simply close IMAP ports. I made no changes to Zimbra itself, I just denied everyone access to the IMAP functions via firewall.

Since they cant connect (mostly iPhone) obviously there are no new errors in the log, and its been up and running fine and catching up on 3,000 backlogged emails without a hitch.

So what would cause this? Something in the iPhones? I saw a thread somewhere around here about the number of folders a user has causing a similar issue. A memory or java configuration?

I have 2 or 3 users who have Outlook setup via IMAP and the rest use the web interface, but nearly all 142 people have iPhones setup with IMAP.
Last edited by GrnEyedDvl on Mon Jan 14, 2019 2:50 am, edited 1 time in total.

Return to “Administrators”

Who is online

Users browsing this forum: JDunphy and 21 guests