Upgrade Error

[carnold]

OK, we have been happily running zimbra 6 and OES2 SP1 with no problems. Today, i upgraded to OES2 SP2 and now:
1-users can not connect to the server using imap (web interface works)
2-when upgrading zimbra to 6.0.2, we get prereq error: missing: compat-libstdc++-5.0.7

Checking yast software show libstdc++-4.x and nothing on compat-libstdc++. Does anyone know if zimbra will run correctly on OES2 SP2? Could this missing package be why users can not connect to the server using imap?

[LMStone]

Originally Posted by carnold

OK, we have been happily running zimbra 6 and OES2 SP1 with no problems. Today, i upgraded to OES2 SP2 and now:
1-users can not connect to the server using imap (web interface works)
2-when upgrading zimbra to 6.0.2, we get prereq error: missing: compat-libstdc++-5.0.7

Checking yast software show libstdc++-4.x and nothing on compat-libstdc++. Does anyone know if zimbra will run correctly on OES2 SP2? Could this missing package be why users can not connect to the server using imap?

OES has a lot of Novell add-ins to provide the Open Enterprise features; we stick to vanilla SLES for Zimbra installs. I don't believe OES is a supported distro for Zimbra, even though it is SLES-based.

Having said that, the compat lib issue you may be able to fix either by installing that version of the library (may be in a devel package; we don't use OES so I don't have a box on which I can confirm)) or by symlinking to whatever version of compat you do have installed.

The IMAP issue may be a port conflict with the mail services included with OES; hard to say without logs or other info.

Hope that helps,
Mark

[carnold]

Originally Posted by LMStone

The IMAP issue may be a port conflict with the mail services included with OES; hard to say without logs or other info.

netstat -nlp shows:
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 4414/nginx.conf
I believe this is what it was when it did work using imap 993. Is it possible to bind nginx to a specific ip?

[carnold]

Not sure if this has anything to do with why we can no longer connect to imap (port 143 or 993) but the nginx.log file is 5.9GB! Thats right, GB...Should it be this big?

[phoenix]

Is this a multi or single server install?

[carnold]

Single server

[phoenix]

Originally Posted by carnold

Single server

You shouldn't have the proxy installed on a single server, follow thse instructions to remove it: imapproxy won't start after upgrade As Mark mentioned earlier, OES isn't a supported platform and you really should use SLES for the server.

[carnold]

Taken from mailbox.log. Below shows the time span of the update:
2009-11-15 06:54:30,833 INFO [Shutdown] [] log - Shutdown hook complete
2009-11-15 08:15:49,680 INFO [main] [] soap - Servlet SoapServlet starting up
Mail seems to flow fine but ppl can not connect using imap (143 or 993). Below shows first instance of a connection refused:
2009-11-15 09:47:12,862 INFO [IndexReadersCache-Sweeper] [] IndexReadersCache - IndexReadersCache-Sweeper thread exiting
2009-11-15 09:47:12,988 WARN [Shutdown] [] dbconn - ignoring error while forcing mysql to flush innodb log to disk
com.zimbra.common.service.ServiceException: system failure: getting database maintenance connection
ExceptionId:Shutdown:1258296432878:63a5a8d676acec5 1
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:251)
at com.zimbra.cs.db.DbPool.getMaintenanceConnection(D bPool.java:391)
at com.zimbra.cs.db.MySQL.flushToDisk(MySQL.java:203)
at com.zimbra.cs.redolog.RedoLogManager.rollover(Redo LogManager.java:604)
at com.zimbra.cs.redolog.RedoLogManager.forceRollover (RedoLogManager.java:642)
at com.zimbra.cs.redolog.RedoLogManager.forceRollover (RedoLogManager.java:638)
at com.zimbra.cs.redolog.RedoLogManager.stop(RedoLogM anager.java:363)
at com.zimbra.cs.redolog.DefaultRedoLogProvider.shutd own(DefaultRedoLogProvider.java:46)
at com.zimbra.cs.util.Zimbra.shutdown(Zimbra.java:292 )
at com.zimbra.soap.SoapServlet.destroy(SoapServlet.ja va:138)
at org.mortbay.jetty.servlet.ServletHolder.destroyIns tance(ServletHolder.java:318)
at org.mortbay.jetty.servlet.ServletHolder.doStop(Ser vletHolder.java:289)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.servlet.ServletHandler.doStop(Se rvletHandler.java:173)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.servlet.SessionHandler.doStop(Se ssionHandler.java:124)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.handler.ContextHandler.doStop(Co ntextHandler.java:591)
at org.mortbay.jetty.webapp.WebAppContext.doStop(WebA ppContext.java:504)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerCollection.doStop (HandlerCollection.java:169)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerCollection.doStop (HandlerCollection.java:169)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.Server.doStop(Server.java:281)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.Server$ShutdownHookThread.run(Se rver.java:559)
Caused by: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.net.ConnectException
MESSAGE: Connection refused

STACKTRACE:

java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at java.net.Socket.<init>(Socket.java:372)
at java.net.Socket.<init>(Socket.java:215)
at com.mysql.jdbc.StandardSocketFactory.connect(Stand ardSocketFactory.java:256)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:271)
at com.mysql.jdbc.Connection.createNewIO(Connection.j ava:2771)
at com.mysql.jdbc.Connection.<init>(Connection.java:1 555)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:285)
at java.sql.DriverManager.getConnection(DriverManager .java:582)
at java.sql.DriverManager.getConnection(DriverManager .java:207)
at com.zimbra.cs.db.DbPool.getMaintenanceConnection(D bPool.java:387)
at com.zimbra.cs.db.MySQL.flushToDisk(MySQL.java:203)
at com.zimbra.cs.redolog.RedoLogManager.rollover(Redo LogManager.java:604)
at com.zimbra.cs.redolog.RedoLogManager.forceRollover (RedoLogManager.java:642)
at com.zimbra.cs.redolog.RedoLogManager.forceRollover (RedoLogManager.java:638)
at com.zimbra.cs.redolog.RedoLogManager.stop(RedoLogM anager.java:363)
at com.zimbra.cs.redolog.DefaultRedoLogProvider.shutd own(DefaultRedoLogProvider.java:46)
at com.zimbra.cs.util.Zimbra.shutdown(Zimbra.java:292 )
at com.zimbra.soap.SoapServlet.destroy(SoapServlet.ja va:138)
at org.mortbay.jetty.servlet.ServletHolder.destroyIns tance(ServletHolder.java:318)
at org.mortbay.jetty.servlet.ServletHolder.doStop(Ser vletHolder.java:289)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.servlet.ServletHandler.doStop(Se rvletHandler.java:173)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.servlet.SessionHandler.doStop(Se ssionHandler.java:124)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.handler.ContextHandler.doStop(Co ntextHandler.java:591)
at org.mortbay.jetty.webapp.WebAppContext.doStop(WebA ppContext.java:504)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerCollection.doStop (HandlerCollection.java:169)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerCollection.doStop (HandlerCollection.java:169)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.handler.HandlerWrapper.doStop(Ha ndlerWrapper.java:142)
at org.mortbay.jetty.Server.doStop(Server.java:281)
at org.mortbay.component.AbstractLifeCycle.stop(Abstr actLifeCycle.java:78)
at org.mortbay.jetty.Server$ShutdownHookThread.run(Se rver.java:559)


** END NESTED EXCEPTION **



Last packet sent to the server was 1 ms ago.
at com.mysql.jdbc.Connection.createNewIO(Connection.j ava:2847)
at com.mysql.jdbc.Connection.<init>(Connection.java:1 555)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:285)
at java.sql.DriverManager.getConnection(DriverManager .java:582)
at java.sql.DriverManager.getConnection(DriverManager .java:207)
at com.zimbra.cs.db.DbPool.getMaintenanceConnection(D bPool.java:387)
... 32 more
2009-11-15 09:47:16,162 INFO [Shutdown] [] redolog - Redo log rollover took 3296ms

[carnold]

Originally Posted by phoenix

You shouldn't have the proxy installed on a single server, follow thse instructions to remove it: imapproxy won't start after upgrade As Mark mentioned earlier, OES isn't a supported platform and you really should use SLES for the server.

Done! And now we can connect using imap!!! Thank you.
Can i get rid of that nginx.log file and free up 6GB of space? Create a new file with the same name and delete the 6GB one? Any chance OES will be "supported" in the future? We have been running zimbra along side OES2 for about 2 yrs (maybe longer. At least since beta 5 zimbra) now with minimal issues.

[phoenix]

Originally Posted by carnold

Done! And now we can connect using imap!!! Thank you.
Can i get rid of that nginx.log file and free up 6GB of space? Create a new file with the same name and delete the 6GB one?

Yes, you can just delete it.

Originally Posted by carnold

Any chance OES will be "supported" in the future?

It's not likely.

Originally Posted by carnold

We have been running zimbra along side OES2 for about 2 yrs (maybe longer. At least since beta 5 zimbra) now with minimal issues.

That's fine but you will from time to time encounter problems like the compat-libs one you mentioned earlier. Zimbra is tested on specific platforms and should install without problems on those and anything else is 'unsupported' i.e. you may hit problems and you may not be able to fix them.