Web interface not working after migration

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
Goelsac
Posts: 7
Joined: Sat Sep 13, 2014 10:36 pm

Web interface not working after migration

Post by Goelsac »

Hi All,
This is my first post.
I am trying to migrate my Zimbra 6.0.14 OSE to a new server. After rsync the data and setting the necessary permissions all Zimbra services seems to work fine but I am not able to load the administration  and user Web interface,  also none of  the zmprov commands are working. Can anybody help me?
Regards,
Sachin
User avatar
vavai
Advanced member
Advanced member
Posts: 174
Joined: Thu Nov 14, 2013 2:41 pm
Location: Indonesia
ZCS/ZD Version: 0
Contact:

Web interface not working after migration

Post by vavai »

What is the error message while trying using zmprov command on Zimbra CLI and what is relevant error messages on /opt/zimbra/log/mailbox.log
Goelsac
Posts: 7
Joined: Sat Sep 13, 2014 10:36 pm

Web interface not working after migration

Post by Goelsac »

Hi,



Many thanks for your reply. Also sending the last 100 lines of mailbox.log



Below is error received when running zmprov command



command : zmprov ca xxx@xxxx,com xxxxxxxxxxxxxxxxx



Error Received: ERROR: zclient.IO_ERROR (invoke Read timed out, server: localhost) (casue: java.net.SocketTimeoutException Read timed out)







tail: invalid option -- l

Try `tail --help' for more information.

[root@mail ~]# tail -n 100 /opt/zimbra/log/mailbox.log

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.mortbay.start.Main.invokeMain(Main.java:194)

at org.mortbay.start.Main.start(Main.java:534)

at org.mortbay.start.Main.start(Main.java:441)

at org.mortbay.start.Main.main(Main.java:119)

Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Server connection failure during transaction. Due to underlying exception: 'java.net.ConnectException: Connection refused'.



** 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:351)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

at java.net.Socket.connect(Socket.java:529)

at java.net.Socket.connect(Socket.java:478)

at java.net.Socket.<init>(Socket.java:375)

at java.net.Socket.<init>(Socket.java:218)

at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:256)

at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:271)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2921)

at com.mysql.jdbc.Connection.<init>(Connection.java:1555)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:154)

at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)

at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:66)

at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)

at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:294)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:277)

at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.java:199)

at com.zimbra.cs.db.DbPool.startup(DbPool.java:190)

at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:156)

at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:123)

at com.zimbra.soap.SoapServlet.init(SoapServlet.java:125)

at javax.servlet.GenericServlet.init(GenericServlet.java:241)

at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)

at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)

at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)

at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1254)

at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)

at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:471)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)

at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

at org.mortbay.jetty.handler.DebugHandler.doStart(DebugHandler.java:127)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

at org.mortbay.jetty.Server.doStart(Server.java:224)

at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServer.java:158)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.mortbay.start.Main.invokeMain(Main.java:194)

at org.mortbay.start.Main.start(Main.java:534)

at org.mortbay.start.Main.start(Main.java:441)

at org.mortbay.start.Main.main(Main.java:119)





** END NESTED EXCEPTION **





Attempted reconnect 3 times. Giving up.

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:888)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2997)

at com.mysql.jdbc.Connection.<init>(Connection.java:1555)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:154)

at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)

at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:66)

at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)

at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:294)

... 39 more
User avatar
vavai
Advanced member
Advanced member
Posts: 174
Joined: Thu Nov 14, 2013 2:41 pm
Location: Indonesia
ZCS/ZD Version: 0
Contact:

Web interface not working after migration

Post by vavai »

According to your error log, it seems that your Zimbra MySQL database didn't up either. Check it by using following command :



su - zimbra

mysql.server status



also check on /opt/zimbra/log/mysql_error_log



Also check permission for /opt/zimbra/conf/my.cnf, sometimes MySQL would not be up due to it's world permission (777)



Vavai
Goelsac
Posts: 7
Joined: Sat Sep 13, 2014 10:36 pm

Web interface not working after migration

Post by Goelsac »

Hi,



There is some corruption in innodb as I googled with the error. I feel the problem is that I have not shutdown Zimbra/mysql before rsync. Now is there any possibility of correcting this mistake or I need to do rsync again. The data is about 3TB and took 2 days to complete the rsync. It is impossible for me to shutdown Zimbra for 2days to do the rsync again. Any ideas?



Thanks

Sachin
abatie
Advanced member
Advanced member
Posts: 61
Joined: Thu Aug 07, 2014 12:02 pm

Web interface not working after migration

Post by abatie »

rsync will only copy the stuff that has changed, so it won't take nearly as long to redo it with the production system shutdown so things are in a consistent state. Do another rsync while things are running, maybe a few to get it as current as you can (when the rsyncs aren't getting any faster), then shutdown zimbra and do a final rsync.
Post Reply