after the Upgrade from 14.04 to 16.04 mailbx Start FAIL

Ask questions about your setup or get help installing ZCS server (ZD section below).
Post Reply
metk0
Posts: 3
Joined: Tue Nov 02, 2021 5:30 pm

after the Upgrade from 14.04 to 16.04 mailbx Start FAIL

Post by metk0 »

Hi All,

after the Upgrade from 14.04 to 16.04 and also reinstallation Zimbra version 8.8.15 3389,
mailbox service webapp zimbra webapp zimbraAdmin webapp zimlet webapp doesn't start any more.

zimbra@mail:~$ zmcontrol status
Host mail.partsch.eu
...
mailbox Stopped
zmmailboxdctl is not running.
...
service webapp Stopped
zmmailboxdctl is not running.
...
zimbra webapp Stopped
zmmailboxdctl is not running.
zimbraAdmin webapp Stopped
zmmailboxdctl is not running.
zimlet webapp Stopped
zmmailboxdctl is not running.
zmconfigd Running


Log i got from /var/log/zimbra.log
mail zmmailboxdmgr[5949]: stale pid 3987 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process

and also from zmmailboxd.out

2021-11-01 15:51:59.548:INFO:oejs.ServerConnector:Thread-12: Stopped ServerConnector@32464a14{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2021-11-01 15:51:59.549:INFO:oejs.ServerConnector:Thread-12: Stopped ServerConnector@4e4aea35{SSL,[ssl, http/1.1]}{0.0.0.0:7071}
2021-11-01 15:51:59.549:INFO:oejs.ServerConnector:Thread-12: Stopped ServerConnector@1442d7b5{SSL,[ssl, http/1.1]}{0.0.0.0:7073}
2021-11-01 15:51:59.550:INFO:oejs.ServerConnector:Thread-12: Stopped ServerConnector@1efee8e7{SSL,[ssl, http/1.1]}{0.0.0.0:7072}
2021-11-01 15:51:59.578:INFO:oejsh.ContextHandler:Thread-12: Stopped o.e.j.w.WebAppContext@5be6e01c{/zimlet,[file:///opt/zimbra/jetty_base/webapps/zimlet/, file:///opt/zimbra/zimlets-deployed/],UNAVAILABLE$
2021-11-01 15:51:59.580:INFO:oejsh.ContextHandler:Thread-12: Stopped o.e.j.w.WebAppContext@7880cdf3{/zimbraAdmin,null,UNAVAILABLE}{/zimbraAdmin}
2021-11-01 15:51:59.586:INFO:oejsh.ContextHandler:Thread-12: Stopped o.e.j.w.WebAppContext@36c88a32{/zimbra,null,UNAVAILABLE}{/zimbra}
2021-11-01 15:52:03.036:INFO:oejsh.ContextHandler:Thread-12: Stopped o.e.j.w.WebAppContext@47d90b9e{/service,null,UNAVAILABLE}{/service}
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Unrecognized VM option 'PrintGCApplicationStoppedTime'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

OpenJDK 64-Bit Server VM warning: .hotspot_compiler file is present but has been ignored. Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.
[0.068s][info][gc] Periodic GC disabled
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
JettyMonitor monitoring thread pool QueuedThreadPool[qtp210652080]@c8e4bb0{STOPPED,10<=0<=250,i=0,r=-1,q=0}[NO_TRY]
Zimbra server reserving server socket port=7110 bindaddr=null ssl=false
Zimbra server reserving server socket port=7995 bindaddr=null ssl=false
Zimbra server reserving server socket port=7143 bindaddr=null ssl=false
Zimbra server reserving server socket port=7993 bindaddr=null ssl=false
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false

Java Version are the default ones for root
root@mail:/opt/zimbra/log# java -version
OpenJDK 64-Bit Server VM warning: .hotspot_compiler file is present but has been ignored. Run with -XX:CompileCommandFile=.hotspot_compiler to load the file.
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-8u292-b10-0ubuntu1~16.04.1-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)

zimbra@mail:~$ java -version
openjdk version "13.0.1" 2019-10-15
OpenJDK Runtime Environment (build 13.0.1+9)
OpenJDK 64-Bit Server VM (build 13.0.1+9, mixed mode, sharing)


Why uses root the default to handle zimbra processes and crashes and not the zimbra version ??
Is this java version Problem ??
But anyways any tipps for me How to fix this ?

Thanks in Advance
BR
Top
metk0
Posts: 3
Joined: Tue Nov 02, 2021 5:30 pm

Re: after the Upgrade from 14.04 to 16.04 mailbx Start FAIL

Post by metk0 »

Hi Again,

after another try of upgrade reinstall. the following happend also :

*** Updating Zimbra ldaputils ***
mailboxd is not running.
*** Mailbox is not running... ***
*** Follow the steps below as zimbra user ignore if installing through install.sh .. ***
*** zmzimletctl deploy /opt/zimbra/zimlets/com_zimbra_email.zip ***
*** zmprov fc zimlet ***
**** Fixing up the permission ****
[] INFO: master is down, falling back to replica...
[] FATAL: failed to initialize LDAP client
com.zimbra.cs.ldap.LdapException: LDAP error: : An error occurred while attempting to connect to server 127.0.0.1:389: java.io.IOException: An error occurred while attempting to establish a connection to server 127.0.0.1:389: java.net.ConnectException: Connection refused
ExceptionId:main:1635895177317:f7cbfb98f5407eb5
Code:ldap.LDAP_ERROR
at com.zimbra.cs.ldap.LdapException.LDAP_ERROR(LdapException.java:90)
at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:74)
at com.zimbra.cs.ldap.unboundid.UBIDLdapException.mapToLdapException(UBIDLdapException.java:40)
at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnPool(LdapConnectionPool.java:117)
at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnectionPool(LdapConnectionPool.java:63)
at com.zimbra.cs.ldap.unboundid.UBIDLdapContext.init(UBIDLdapContext.java:111)
at com.zimbra.cs.ldap.unboundid.UBIDLdapClient.init(UBIDLdapClient.java:39)
at com.zimbra.cs.ldap.LdapClient.getInstanceIfLDAPavailable(LdapClient.java:62)
at com.zimbra.cs.ldap.LdapClient.getInstance(LdapClient.java:69)
at com.zimbra.cs.ldap.LdapClient.initialize(LdapClient.java:94)
at com.zimbra.cs.account.ldap.LdapProv.<init>(LdapProv.java:47)
at com.zimbra.cs.account.ldap.LdapProvisioning.<init>(LdapProvisioning.java:292)
at com.zimbra.cs.account.ldap.LdapProvisioning.<init>(LdapProvisioning.java:289)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.ReflectAccess.newInstance(ReflectAccess.java:166)
at java.base/jdk.internal.reflect.ReflectionFactory.newInstance(ReflectionFactory.java:404)
at java.base/java.lang.Class.newInstance(Class.java:591)
at com.zimbra.cs.account.Provisioning.getInstance(Provisioning.java:354)
at com.zimbra.cs.account.Provisioning.getInstance(Provisioning.java:310)
at com.zimbra.cs.account.ProvUtil.initProvisioning(ProvUtil.java:1032)
at com.zimbra.cs.account.ProvUtil.main(ProvUtil.java:4156)
Caused by: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to connect to server 127.0.0.1:389: java.io.IOException: An error occurred while attempting to establish a connection to server 127.0.0.1:389: java.net.ConnectException: Connection refused')
at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:754)
at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:686)
at com.unboundid.ldap.sdk.LDAPConnection.<init>(LDAPConnection.java:518)
at com.unboundid.ldap.sdk.SingleServerSet.getConnection(SingleServerSet.java:229)
at com.unboundid.ldap.sdk.ServerSet.getConnection(ServerSet.java:98)
at com.unboundid.ldap.sdk.FailoverServerSet.getConnection(FailoverServerSet.java:545)
at com.unboundid.ldap.sdk.LDAPConnectionPool.createConnection(LDAPConnectionPool.java:938)
at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:876)
at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:779)
at com.unboundid.ldap.sdk.LDAPConnectionPool.<init>(LDAPConnectionPool.java:726)
at com.zimbra.cs.ldap.unboundid.LdapConnectionPool.createConnPool(LdapConnectionPool.java:114)
... 20 more
Caused by: java.io.IOException: An error occurred while attempting to establish a connection to server 127.0.0.1:389: java.net.ConnectException: Connection refused
at com.unboundid.ldap.sdk.LDAPConnectionInternals.<init>(LDAPConnectionInternals.java:137)
at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:744)
... 30 more
updateRsyslogd: Updating /etc/rsyslog.d/50-default.conf...done.
**** Installation Completed. ****
**** Restart all the service as zimbra user. Run zmcontrol restart. ****
zimbra-proxy-patch (8.8.15.1634196512.p27-1.u16) wird eingerichtet ...

Thanks
BR
Top
metk0
Posts: 3
Joined: Tue Nov 02, 2021 5:30 pm

Re: after the Upgrade from 14.04 to 16.04 mailbx Start FAIL

Post by metk0 »

Hi All,

install again from backup files getting success.

zimbra@mail:~$ zmcontrol status
Host mail.xxx.x.x.x
amavis Running
antispam Running
antivirus Running
dnscache Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Running
opendkim Running
proxy Running
service webapp Running
snmp Running
spell Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running



BR
Top
Post Reply

Return to “Installation and Upgrade”