5.0.10 upgrade problem

[Vladimir]

After upgrading I'm now getting errors while sending mail:

msg: system failure: MessagingException
code: service.FAILURE
method: SendMsgRequest
detail: soap:Receiver
trace: btpool0-16:1223480041691:ea3219b26e9c53c3

Anyone know what that means?

[Vladimir]

Also in my logs I see :

Soap
Engine - handler exception
com.zimbra.common.service.ServiceException: system failure: MessagingException
ExceptionId:btpool0-31:1223481250977:ea3219b26e9c53c3
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.j
ava:253)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:330)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:118)
at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:189)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:154)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:411)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:268)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:269)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:189)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487
)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(Servlet
Handler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(Servlet
Handler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:3
60)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.jav
a:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:1
81)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:7
16)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHand
lerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.
java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:1
39)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandle
r.java:350)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:1
39)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:50
6)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnectio
n.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.ja
va:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool
.java:442)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: Read timed o
ut; chained exception is:
java.net.SocketTimeoutException: Read timed out
at com.sun.mail.smtp.SMTPTransport.readServerResponse (SMTPTransport.java
:1598)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTra nsport.java:1356)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SM TPTransport.java:39
9)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:535)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:253)
... 33 more

[irfan]

Issue is fixed with the help of Zimbra support.

[rwc101010]

So, what was the fix? Care to share??

[Vladimir]

The ca directory contained extra links to different certificates. This seemed to not bother 5.0.9 but under 5.0.10 postfix has a fit if there are more then 3 files in that directory. Check out Error (MTA): Unable to set STARTTLS - Zimbra :: Wiki.

As per support instructions the fix was:

1) Clear all the contents of the /opt/zimbra/conf/ca directory by backing them up
somewhere on disk.
2) Copy the /opt/zimbra/ssl/zimbra/commercial/commercial.key /opt/zimbra/conf/ca/ca.key
3) Copy /opt/zimbra/ssl/zimbra/commercial/commercial.crt /opt/zimbra/conf/ca/ca.pem
4) Create the hash value
ln -f -s ca.pem /opt/zimbra/conf/ca/`openssl x509 -hash -noout -in
/opt/zimbra/conf/ca/ca.pem`.0
5) Chmod 644 /opt/zimbra/conf/ca/*
6) Restart the zmcontrol

[tgx]

So is this likely to happen with everyone that upgrades to 5.0.10?

[jrefl5]

Originally Posted by Vladimir

The ca directory contained extra links to different certificates. This seemed to not bother 5.0.9 but under 5.0.10 postfix has a fit if there are more then 3 files in that directory. Check out Error (MTA): Unable to set STARTTLS - Zimbra :: Wiki.

Sounds like I'm in for fun.
in /opt/zimbra/ssl/zimbra/commercial i have;

commercial_ca.crt
commercial.crt
commercial.csr
commercial.key

And yes they are GoDaddy certificates

and in /opt/zimbra/conf;

219d9499.0 -> commercial_ca.pem
67504c4f.0 -> ca.pem
97552d04.0 -> commercial_ca_2.pem
bcdd5959.0 -> commercial_ca_3.pem
ca.key
ca.pem
commercial_ca_1.pem
commercial_ca_2.pem
commercial_ca_3.pem
commercial_ca.pem

all with timestamps of the upgrade to 5.0.9

[jrefl5]

Any ideas, documentation on what I need to do prior to upgrade to 5.0.10, or do I just wait for a later update?

[Vladimir]

Well the fix is fairly simple and quick. My guess is that if you do your upgrade, and follow the fix steps it should only add a couple of minutes to the whole process.

[jrefl5]

Vladimir,
The problem is that I will still have more that 3 files in /opt/zimbra/conf/ca, because GoDaddy cirts need the crt they issue, and their crt, which do I copy to .pem, or do I copy both to .pem files?
If both then I end up with 1 .key, 2 .pem , and links to one or both .pem files that comes to 5 files.

The problem is in part due to the way that GoDaddy issued their certificates, and the way Zimbra handles them.

james