zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Ask questions about your setup or get help installing ZCS server (ZD section below).
Post Reply
txerra
Posts: 30
Joined: Sat Sep 13, 2014 3:11 am

zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by txerra »

Hi

I am with zimbra support since april 6, but for the moment they can´t help me, and I am desperate.
I am testing the upgrade from 8.7.1 to 8.7.x, single server, in a clon server of the production server.
In the clon 8.7.1 zimbra is working, but once i upgrade, I this error: zmmailboxctl is not running.
I tried the upgrade 6 times, to different version, but the same problem.
The upgrade always finishes as done, without errors.
I do the database integrity without errors....


Can somebody help me with this?

Thank you in advance

Txerra
User avatar
DualBoot
Elite member
Elite member
Posts: 1326
Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by DualBoot »

Hello

first stop all zimbra service and run only the mailboxd.
After doing this check the log and post any relevant information.

Regards,

PS: give us your Zimbra installation hardware settings.
txerra
Posts: 30
Joined: Sat Sep 13, 2014 3:11 am

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by txerra »

Hi, thank you for your message.
I have done you asked me ( i started first ldap ) and this is the message in mailbox.log file

2017-06-12 17:47:27,007 WARN [main] [] misc - Could not establish a connection to the database. Retrying in 5 seconds.
com.zimbra.common.service.ServiceException: system failure: getting database connection
ExceptionId:main:1497282447007:4e7fbba2466ba4fa
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:286)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:360)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:322)
at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.java:243)
at com.zimbra.cs.db.DbPool.startup(DbPool.java:234)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:219)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:180)
at com.zimbra.soap.SoapServlet.init(SoapServlet.java:126)
at javax.servlet.GenericServlet.init(GenericServlet.java:244)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:626)
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:405)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:875)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:346)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1380)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:772)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:259)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:518)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:161)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:212)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.handler.DebugHandler.doStart(DebugHandler.java:143)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:405)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:372)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1510)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:214)
at org.eclipse.jetty.start.Main.start(Main.java:457)
at org.eclipse.jetty.start.Main.main(Main.java:75)
Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to 127.0.0.1:7306 : Connection refused
at org.mariadb.jdbc.internal.SQLExceptionMapper.get(SQLExceptionMapper.java:136)
at org.mariadb.jdbc.internal.SQLExceptionMapper.throwException(SQLExceptionMapper.java:106)
at org.mariadb.jdbc.Driver.connect(Driver.java:115)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:78)
at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:67)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:341)
... 56 more
Caused by: org.mariadb.jdbc.internal.common.QueryException: Could not connect to 127.0.0.1:7306 : Connection refused
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.connect(MySQLProtocol.java:714)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.<init>(MySQLProtocol.java:280)
at org.mariadb.jdbc.Driver.connect(Driver.java:111)
... 64 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.connect(MySQLProtocol.java:387)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.connect(MySQLProtocol.java:709)
... 66 more


Hardware:

Virtual machina
2 CPU
12GB MEMORY
HD 1TB


Thank you
User avatar
DualBoot
Elite member
Elite member
Posts: 1326
Joined: Mon Apr 18, 2016 8:18 pm
Location: France - Earth
ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
Contact:

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by DualBoot »

so stop all zimbra services and then start only the mysql service with, as zimbra user, mysql.server start
then check if mysql server is listening.
txerra
Posts: 30
Joined: Sat Sep 13, 2014 3:11 am

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by txerra »

hi, here the result.

zimbra@mail:~$ mysql.server status
mysql is running with pid 9221
zimbra@mail:~$ netstat -tlpn
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN 9221/mysqld

Seems to be listening
zcole

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by zcole »

Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to 127.0.0.1:7306 : Connection refused

Do you have any firewall, iptables, etc running? Can you telnet to port 7306 as the zimbra user?

# su - zimbra
# telnet localhost 7306
txerra
Posts: 30
Joined: Sat Sep 13, 2014 3:11 am

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by txerra »

hi


thank you for your help, it seems it was some obsolete folders that are not necesary in Zimbra 8.7.x the cause of the problem.
After two months where the support guy didn´t help me, I opened a new case in support where fortunately the the guy who was encharged to help me, has solved me the problem in one hour......


thank you all for your answers and help!
kyilmaz80
Posts: 2
Joined: Tue Sep 12, 2017 4:00 pm

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by kyilmaz80 »

txerra wrote:hi


thank you for your help, it seems it was some obsolete folders that are not necesary in Zimbra 8.7.x the cause of the problem.
After two months where the support guy didn´t help me, I opened a new case in support where fortunately the the guy who was encharged to help me, has solved me the problem in one hour......


thank you all for your answers and help!
Hello we are facing the same problem. How did the problem solved?
txerra
Posts: 30
Joined: Sat Sep 13, 2014 3:11 am

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by txerra »

Excuse me, I didn´t read this message till today.

Did you solved it?

If not, tell me and i will show you how we solved it.

sorry again
judy
Posts: 1
Joined: Tue Oct 23, 2018 7:14 am

Re: zmmailboxctl is not running after updating from 8.7.1 to 8.7.x included 11

Post by judy »

Can you tell us your solution for the problem? I met the same problem, need your help.
Thank you in advance.
Post Reply