5.0.10 upgrade problem

[Vladimir]

Well hmm. I had a similar issue when I installed the Thawte certs I used, were I needed extra links for the their root cert, but it the steps described above seemed to have worked. I would suggest you contact support and ask them.

[maumar]

i am in the same case:

[02:05:35 root@zimbra ~ ]# ls -la /opt/zimbra/conf/ca
totale 24
drwxr-xr-x 2 zimbra zimbra 4096 22 ago 01:58 .
drwxrwxr-x 9 zimbra zimbra 4096 24 set 17:39 ..
lrwxrwxrwx 1 root   root     19 22 ago 01:58 74c26bd0.0 -> commercial_ca_1.pem
lrwxrwxrwx 1 root   root      6 22 ago 01:58 88d12f15.0 -> ca.pem
-rw-r--r-- 1 zimbra zimbra  887 22 ago 01:58 ca.key
-rw-r--r-- 1 zimbra zimbra  993 22 ago 01:58 ca.pem
-rw-r--r-- 1 zimbra zimbra  948 22 ago 01:58 commercial_ca_1.pem
-rw-r--r-- 1 zimbra zimbra  948 22 ago 01:58 commercial_ca.pem
lrwxrwxrwx 1 root   root     17 20 ago 08:07 d8274e24.0 -> commercial_ca.pem

as far as i can argue by your 5 steps fix, it's enough i clear it after saved content, this way:

rm -f commercial_ca_1.pem commercial_ca.pem 74c26bd0.0 d8274e24.0

then upgrade 5.0.9 to 5.0.10.

This what stated in wiki url, more

Maurizio

[maumar]

It's worked for me.
i would mark it as SoLVED


m.

[brian]

Redeploying your cert with zmcertmgr will also fix the issue in 5.0.10. The number of files in /opt/zimbra/conf/ca will depend on your certificate provider and maybe be more or less then 3 files. There will be one file for each intermediate cert and root certificate.

[Vladimir]

This seems to be a lot messier in a multi server setup. After we had a solution for the single server we initially deployed this on, I've upgraded a 6 machine multiserver install and following the same steps on all the machines doesn't seem to fix the issue.

That machine cluster is not in production yet, so after much cursing I gave up for the day. I'll beat on it some more tomorrow and contact support again if I fail.

[dwmtractor]

Brian (and/or others),

Has a bug been filed off of this thread, internally if not publicly? It would seem to me that this is something we should hope will not be a problem in 5.0.11, and if that is the case some of us that are still on 5.0.9 might just wait to save ourselves the headache. . .

[tgx]

I was wanting to go to 5.0.10 after the IM problems surfaced in 5.0.9 which was
a major fiasco in our office and I'm sure others got some jaws about the From sorting. I was waiting to see what might be wrong in 5.0.10, now I know. I don't see how we can upgrade when each new one is broken in some fashion.

[Vladimir]

Because I'm annoyed I'm working from home at this, so I figured I'd post the errors I'm getting in case anyone has any ideas. I've redeployed the certs from scratch and followed the steps that worked on the single server with no luck. Tried dropping the slave out of rotation. Ran fixperms. Everything but mail seems to function.

Back to prodding this with a sharp stick ..


Currently mail mailog shows:

Oct 15 18:45:54 zimmta1 postfix/proxymap[15518]: warning: dict_ldap_connect: Unable to bind to server ldap://zimldap1.rutgers.edu ldap://zimldap2.rutgers.edu as uid=zmpostfix,cn=appaccts,cn=zimbra: 49 (Invalid credentials)
Oct 15 18:45:54 zimmta1 last message repeated 2 times
Oct 15 18:45:54 zimmta1 postfix/trivial-rewrite[15517]: fatal: proxy:ldap:/opt/z
imbra/conf/ldap-vad.cf(0,lock|fold_fix): table lookup problem


While my mailbox.log on the mail box servers show (while trying to send a message from inside the web ui):

2008-10-15 18:44:45,772 INFO [btpool0-13] [name=vgabriel@rumail.rutgers.edu;mid
=8;ip=192.168.170.11;ua=ZimbraWebClient - FF3.0 (Win)/5.0.10_GA_2638.RHEL5_64;]
SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: MessagingException
ExceptionId:btpool0-13:1224110685772:f1d9e7743a072c76
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:211)
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.close(SMTPTranspor t.java:685)
at javax.mail.Transport.send0(Transport.java:171)
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

[Vladimir]

Yay for mark I eyeball. After carefully looking through countless config files I noticed that ldap_postfix_password and ldap_amavis_password on the ldap master had new and strange values. I have no clue where they came from, they were not those initially set and the previous version worked so I can only assume the upgrade didn't correctly save those passwords.

After fixing the passwords and restarting the whole mess, mail seems to be flowing. I'm not quite calling it solved yet, until I play with it some more.