zmmailboxdctl failing to run after most recent apt-get

Ask questions about your setup or get help installing ZCS server (ZD section below).
mgmailadmin
Posts: 10
Joined: Wed Jun 15, 2022 3:18 am

Re: zmmailboxdctl failing to run after most recent apt-get

Post by mgmailadmin »

@mafiamail,

One other thing, the 8.8.15 FOSS build I installed and brought up successfully was

Code: Select all

zimbra@mail4:/home/ubuntu$ zmcontrol -v
Release 8.8.15.GA.4179.UBUNTU20.64 UBUNTU20_64 FOSS edition, Patch 8.8.15_P32.


I note the release number is different (later) than yours. This was the Ubuntu 20.04.6 LTS release so that may be why and may explain why it works but it is something to consider.
zgokan
Advanced member
Advanced member
Posts: 171
Joined: Sun Apr 17, 2016 8:58 am

Re: zmmailboxdctl failing to run after most recent apt-get

Post by zgokan »

I am having the same problem. I tried 3-4 times. Is there a general problem?

Problems with new installations: (zimbra9)
1. The zmmailboxd service is not running. (I tried 3 times.)
2. Repo issues on a different installation.

Code: Select all

0.007s][info][gc] Using G1
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.
2022-06-16 18:47:39.468:INFO::main: Logging initialized @424ms to org.eclipse.jetty.util.log.StdErrLog
JettyMonitor monitoring thread pool QueuedThreadPool[qtp1800659519]@6b53e23f{STOPPED,10<=0<=250,i=0,r=-1,q=0}[NO_TRY]
2022-06-16 18:47:39.654:WARN:oejx.XmlConfiguration:main: Deprecated constructor public org.eclipse.jetty.util.ssl.SslContextFactory() in file:///opt/zimbra/jetty_base/etc/jetty.xml
2022-06-16 18:47:39.835:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in
Then I tried to install on a different virtual machine and the following errors started to appear.

Code: Select all

      ...Unable to download packages from repository. System is not modified.
      Warning: apt-key output should not be parsed (stdout is not a terminal)
mgmailadmin
Posts: 10
Joined: Wed Jun 15, 2022 3:18 am

Re: zmmailboxdctl failing to run after most recent apt-get

Post by mgmailadmin »

zgokan wrote:I am having the same problem. I tried 3-4 times. Is there a general problem?

Problems with new installations: (zimbra9)
1. The zmmailboxd service is not running. (I tried 3 times.)
2. Repo issues on a different installation.

Code: Select all

0.007s][info][gc] Using G1
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.
2022-06-16 18:47:39.468:INFO::main: Logging initialized @424ms to org.eclipse.jetty.util.log.StdErrLog
JettyMonitor monitoring thread pool QueuedThreadPool[qtp1800659519]@6b53e23f{STOPPED,10<=0<=250,i=0,r=-1,q=0}[NO_TRY]
2022-06-16 18:47:39.654:WARN:oejx.XmlConfiguration:main: Deprecated constructor public org.eclipse.jetty.util.ssl.SslContextFactory() in file:///opt/zimbra/jetty_base/etc/jetty.xml
2022-06-16 18:47:39.835:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in
Then I tried to install on a different virtual machine and the following errors started to appear.

Code: Select all

      ...Unable to download packages from repository. System is not modified.
      Warning: apt-key output should not be parsed (stdout is not a terminal)
Yes @Zgokan, regarding repo issues on different installations....

When I was trying to setup a clean install on a new instance I observed that:
1) The Ubuntu 18.04.6 LTS version had the issues with mailboxd not starting so it would appear to be a general problem with the current ZEXTRAS FOSS 9 build for Ubuntu 18.04.6.
2) I also tried a fresh install of ZEXTRAS FOSS 9 for Ubuntu 20.04.6 and had the same experience you did. So again, the Zextras builds as currently posted in the repository are hosed.
3) As a test of my environment, I loaded the Zimbra 8.8.15 OSE load for Ubuntu 20.04.6 and that build loaded, installed without error and ran.

I was in the midst of the configuration of 3) when @livelace posted his comments relative to FOSS 9 so I tried that and was able to recover.

As an aside, the OpenJDK warnings about the hotspot compiler can be resolved by adding "-XX:CompileCommandFile=.hotspot_compiler" to the end of your zmlocalconfig java_mailboxd_options.

Assuming you are starting with Ubuntu 18.04.6, if you haven't already, try the downgrades mentioned above.
Martinwiertz
Advanced member
Advanced member
Posts: 85
Joined: Sat Sep 13, 2014 3:55 am
Location: The Netherlands
ZCS/ZD Version: V10 FOSS Intalio on Ubuntu20.04

Re: zmmailboxdctl failing to run after most recent apt-get

Post by Martinwiertz »

Update 5PM:
Restore from backup OS and include Zextras v9.0 9feb. Restored data/mails with Zextras suite and all is running again. :-)

Update 3PM:
A real mess.
Tried to uninstall the new packages core, jdk, jett but it failed.

Reinstall latest Zextras install results in new problems:

Downloading packages (11):
zimbra-core-components
zimbra-ldap-components
zimbra-mta-components
zimbra-dnscache-components
zimbra-snmp-components
zimbra-store-components
zimbra-jetty-distribution
zimbra-apache-components
zimbra-spell-components
zimbra-memcached
zimbra-proxy-components
...Unable to download packages from repository. System is not modified.

Great, now I have no server at all. I do have a Zextras suite data bkup and an disc backup of 1 month. Now trying to restore based on this.
P25 is killing......



Hello,

I would like to check something. I would like to downgrade the installed patches but are not comfortable with CLI-output to say Yes....
(situation Mailboxd is not running, LDAP is running)

On Zextras forum I see an post which indicates success but I want to make sure these commands and output are correct?
https://community.zextras.com/forum/postid/3218/

Current versions on my Zextras v9.0P25 system: (Release 9.0.0.ZEXTRAS.20220402.UBUNTU18.64 UBUNTU18_64 FOSS edition.)

sudo apt-cache showpkg zimbra-core-components
Package: zimbra-core-components
Versions: 3.0.12-1zimbra8.8b1.18.04

sudo apt-cache showpkg zimbra-jetty-distribution
Package: zimbra-jetty-distribution
Versions: 9.4.46.v20220331-2.u18

sudo apt-cache showpkg zimbra-ldap-components
Package: zimbra-ldap-components
Versions: 2.0.6-1zimbra8.8b1.18.04

sudo apt-cache showpkg zimbra-openjdk
Package: zimbra-openjdk
Versions: 17.0.2-1zimbra8.8b1.18.04 and more below is secondline 13.0.1-1zimbra8.8b1.18.04 and 11.0.2-1zimbra8.8b1.18.04 and 1.8.0u172b01-1zimbra8.7b5.18.04

sudo apt-get install zimbra-openjdk=17.0.2-1zimbra8.8b1.18.04
[sudo] password for martin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
zimbra-openjdk is already the newest version (17.0.2-1zimbra8.8b1.18.04).
zimbra-openjdk set to manually installed.


Do I say Yes to Remove package of will there be much more removed?? (regarding No longer required, will this delete to much?)
--------------------------------------------------------
sudo apt-get install zimbra-openjdk=13.0.1-1zimbra8.8b1.18.04
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libgraphite2-3 libharfbuzz0b libsensors4 libsocket6-perl pax sysstat zimbra-amavis-logwatch zimbra-bdb-lib zimbra-curl zimbra-curl-lib
zimbra-cyrus-sasl zimbra-freetype-lib zimbra-ldap-base zimbra-libart-lib zimbra-libltdl-lib zimbra-libpng-lib zimbra-libsodium-lib
zimbra-lmdb zimbra-openjdk-cacerts zimbra-openldap-client zimbra-openldap-server zimbra-openssl zimbra-os-requirements zimbra-osl
zimbra-perl zimbra-perl-archive-zip zimbra-perl-berkeleydb zimbra-perl-bit-vector zimbra-perl-canary-stability zimbra-perl-carp-clan
zimbra-perl-class-inspector zimbra-perl-convert-asn1 zimbra-perl-convert-binhex zimbra-perl-convert-tnef zimbra-perl-convert-uulib
zimbra-perl-crypt-openssl-random zimbra-perl-crypt-saltedhash zimbra-perl-data-uuid zimbra-perl-date-calc zimbra-perl-date-manip
zimbra-perl-db-file zimbra-perl-dbd-mysql zimbra-perl-email-date-format zimbra-perl-encode-locale zimbra-perl-file-grep
zimbra-perl-file-libmagic zimbra-perl-file-listing zimbra-perl-file-tail zimbra-perl-filesys-df zimbra-perl-geography-countries
zimbra-perl-http-cookies zimbra-perl-http-daemon zimbra-perl-http-date zimbra-perl-http-message zimbra-perl-http-negotiate
zimbra-perl-innotop zimbra-perl-io-html zimbra-perl-io-sessiondata zimbra-perl-io-socket-ip zimbra-perl-io-socket-ssl
zimbra-perl-io-stringy zimbra-perl-ip-country zimbra-perl-json-pp zimbra-perl-libwww zimbra-perl-lwp-mediatypes
zimbra-perl-lwp-protocol-https zimbra-perl-math-bigint zimbra-perl-mime-lite zimbra-perl-mime-tools zimbra-perl-mime-types
zimbra-perl-mozilla-ca zimbra-perl-net-http zimbra-perl-net-ldap zimbra-perl-net-ldapapi zimbra-perl-net-libidn zimbra-perl-net-ssleay
zimbra-perl-parent zimbra-perl-proc-processtable zimbra-perl-soap-lite zimbra-perl-socket-linux zimbra-perl-swatchdog
zimbra-perl-task-weaken zimbra-perl-term-readkey zimbra-perl-unix-getrusage zimbra-perl-unix-syslog zimbra-perl-uri
zimbra-perl-www-robotrules zimbra-perl-xml-namespacesupport zimbra-perl-xml-parser zimbra-perl-xml-parser-lite zimbra-perl-xml-sax
zimbra-perl-xml-sax-base zimbra-perl-xml-sax-expat zimbra-perl-xml-simple zimbra-perl-zmq-constants zimbra-perl-zmq-libzmq3
zimbra-pflogsumm zimbra-postfix-logwatch zimbra-prepflog zimbra-rrdtool zimbra-rrdtool-lib zimbra-rsync zimbra-tcmalloc-lib
zimbra-zeromq-lib
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
zimbra-apache zimbra-common-core-jar zimbra-common-core-libs zimbra-common-mbox-conf zimbra-common-mbox-conf-attrs
zimbra-common-mbox-conf-msgs zimbra-common-mbox-conf-rights zimbra-common-mbox-db zimbra-common-mbox-docs zimbra-common-mbox-native-lib
zimbra-core zimbra-core-components zimbra-ldap zimbra-ldap-components zimbra-logger zimbra-mbox-service zimbra-mta zimbra-proxy
zimbra-snmp zimbra-spell zimbra-store zimbra-timezone-data
The following packages will be DOWNGRADED:
zimbra-openjdk
0 upgraded, 0 newly installed, 1 downgraded, 22 to remove and 7 not upgraded.
Need to get 169 MB of archives.
After this operation, 89.8 MB disk space will be freed.
Do you want to continue? [Y/n]
Last edited by Martinwiertz on Fri Jun 17, 2022 3:27 pm, edited 4 times in total.
User avatar
L. Mark Stone
Ambassador
Ambassador
Posts: 2796
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine, US
ZCS/ZD Version: 10.0.6 Network Edition
Contact:

Re: zmmailboxdctl failing to run after most recent apt-get

Post by L. Mark Stone »

I wouldn't do ANYTHING right now that requires access to the Zimbra repos!

Instead of just removing Patch 32/25 from the repos, (allowing folks to upgrade to 31.1/24.1 if they haven't done so already, to be able to get the important security updates in those patches), Synacor are apparently blocking all access to the repos at this writing.
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
AWS Certified Solutions Architect-Associate
dasspiegel
Posts: 2
Joined: Sat Sep 13, 2014 1:23 am
Location: Dar es Salaam, Tanzania
ZCS/ZD Version: ZCS9-NE, ZCS9-OSS

Re: zmmailboxdctl failing to run after most recent apt-get

Post by dasspiegel »

L. Mark Stone wrote:I wouldn't do ANYTHING right now that requires access to the Zimbra repos!

Instead of just removing Patch 32/25 from the repos, (allowing folks to upgrade to 31.1/24.1 if they haven't done so already, to be able to get the important security updates in those patches), Synacor are apparently blocking all access to the repos at this writing.
Agreed, please hold and don't upgrade zimbra at least until this issue is sorted
mgmailadmin
Posts: 10
Joined: Wed Jun 15, 2022 3:18 am

Re: zmmailboxdctl failing to run after most recent apt-get

Post by mgmailadmin »

Zimbra issued a mea culpa here:viewtopic.php?f=13&t=70868 promising it won't happen again and that it is now safe to update:
Where things stand:
The patches for Zimbra 8.8.15 and 9.0.0 has been made available once again with the blocking issue resolved. The package repository issues have been corrected, fixing the issues with installations and upgrades. Everyone should now be able to install and upgrade without issue.
I'm not brave though so I'm going to wait and see.

Anyone out there tried this again? If so, how did it go?
User avatar
maxxer
Outstanding Member
Outstanding Member
Posts: 224
Joined: Fri Oct 04, 2013 2:12 am
Contact:

Re: zmmailboxdctl failing to run after most recent apt-get

Post by maxxer »

mgmailadmin wrote:Anyone out there tried this again? If so, how did it go?
viewtopic.php?p=305401#p305405
alextonio104
Posts: 7
Joined: Wed Nov 18, 2020 6:43 am

Re: zmmailboxdctl failing to run after most recent apt-get

Post by alextonio104 »

Hi,

I've seen that the downgrade of the packages work for Ubuntu 18.04, I'm using Ubuntu 20.04 but if I try to downgrade Zimbra-core-components says "zimbra-osl (>= 2.0.0-1zimbra9.0b1.20.04) but 1.0.9-1zimbra8.7b1.20.04 is going to be installed"

Is there a way to force the upgrade in Ubuntu 20.04?

Thanks in advance.
darkfader
Posts: 20
Joined: Sat Dec 11, 2021 11:39 pm

Re: zmmailboxdctl failing to run after most recent apt-get

Post by darkfader »

My server is still kinda broken - I upgraded on the 18th.

Apparently it has messed up the zmproxy settings and mailboxd tries to open the ports the proxy manages.
of course that way they conflict and it can't start like that.


[zimbra@zmail ~]$ zmcontrol -v
Release 8.8.15_GA_3953.RHEL8_64_20200629025823 RHEL8_64 FOSS edition.


Package changes:

2022-06-18T19:56:52+0000 DEBUG --> Starting dependency resolution
2022-06-18T19:56:52+0000 DEBUG ---> Package libretls.x86_64 3.5.1-1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package libretls.x86_64 3.5.2-1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package netcat.x86_64 1.218-4.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package netcat.x86_64 1.218-5.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-clamav.x86_64 0.103.2-1zimbra8.8b3.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-clamav.x86_64 0.103.3-1zimbra8.8b3.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-clamav-libs.x86_64 0.103.2-1zimbra8.8b3.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-clamav-libs.x86_64 0.103.3-1zimbra8.8b3.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-core-jar.x86_64 8.8.15.1647325929-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-core-jar.x86_64 8.8.15.1655458176-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-core-libs.x86_64 8.8.15.1647230035-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-core-libs.x86_64 8.8.15.1654854265-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-mbox-conf-attrs.x86_64 8.8.15.1571124020-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-mbox-conf-attrs.x86_64 8.8.15.1652767386-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-mbox-conf-msgs.x86_64 8.8.15.1556130968-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-common-mbox-conf-msgs.x86_64 8.8.15.1652703447-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-core-components.x86_64 2.0.14-1zimbra8.8b1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-core-components.x86_64 2.0.16-1zimbra8.8b1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-jetty-distribution.x86_64 9.4.18.v20190429-2.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-jetty-distribution.x86_64 9.4.46.v20220331-2.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-ldap-components.x86_64 1.0.14-1zimbra8.8b1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-ldap-components.x86_64 1.0.16-1zimbra8.8b1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-admin-console-war.x86_64 8.8.15.1643880751-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-admin-console-war.x86_64 8.8.15.1653031987-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-store-libs.x86_64 8.8.15.1647230035-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-store-libs.x86_64 8.8.15.1654854265-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-war.x86_64 8.8.15.1647325929-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-war.x86_64 8.8.15.1655458176-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-webclient-war.x86_64 8.8.15.1647334948-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mbox-webclient-war.x86_64 8.8.15.1654769776-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mta-components.x86_64 1.0.14-1zimbra8.8b1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mta-components.x86_64 1.0.15-1zimbra8.8b1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mta-patch.x86_64 8.8.15.1647332084.p31-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-mta-patch.x86_64 8.8.15.1655471268.p32-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-nginx.x86_64 1.20.0-1zimbra8.8b2.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-nginx.x86_64 1.20.0-1zimbra8.8b3.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openjdk.x86_64 13.0.1-1zimbra8.8b1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openjdk.x86_64 17.0.2-1zimbra8.8b1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openssl.x86_64 1.1.1l-1zimbra8.7b4.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openssl.x86_64 1.1.1n-1zimbra8.7b4.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openssl-libs.x86_64 1.1.1l-1zimbra8.7b4.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-openssl-libs.x86_64 1.1.1n-1zimbra8.7b4.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-patch.x86_64 8.8.15.1648259498.p31-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-patch.x86_64 8.8.15.1655471268.p32-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-perl-mail-spamassassin.x86_64 3.4.5-1zimbra8.8b4.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-perl-mail-spamassassin.x86_64 3.4.6-1zimbra8.8b4.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-proxy-components.x86_64 1.0.9-1zimbra8.8b1.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-proxy-components.x86_64 1.0.10-1zimbra8.8b1.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-proxy-patch.x86_64 8.8.15.1648259498.p31-1.r8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-proxy-patch.x86_64 8.8.15.1655471268.p32-1.r8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-spamassassin-rules.x86_64 1.0.0-1zimbra8.8b5.el8 will be upgraded
2022-06-18T19:56:52+0000 DEBUG ---> Package zimbra-spamassassin-rules.x86_64 1.0.0-1zimbra8.8b6.el8 will be an upgrade
2022-06-18T19:56:52+0000 DEBUG --> Finished dependency resolution



symptom:
Jun 19 03:48:01 zmail sudo[220050]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 19 03:48:01 zmail zmmailboxdmgr[220052]: stale pid 21616 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jun 19 03:48:01 zmail zmmailboxdmgr[220052]: assuming no other instance is running
Jun 19 03:48:01 zmail zmmailboxdmgr[220052]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jun 19 03:48:01 zmail zmmailboxdmgr[220052]: assuming no other instance is running
Jun 19 03:48:01 zmail zmmailboxdmgr[220052]: no manager process is running
Jun 19 03:48:01 zmail sudo[220050]: pam_unix(sudo:session): session closed for user root
Jun 19 03:48:01 zmail zmconfigd[216832]: Tracking service mailbox
Jun 19 03:48:01 zmail sudo[220065]: zimbra : TTY=unknown ; PWD=/opt/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmmailboxdmgr status
Jun 19 03:48:01 zmail sudo[220065]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice
Jun 19 03:48:01 zmail sudo[220065]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 19 03:48:01 zmail zmmailboxdmgr[220066]: stale pid 21616 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jun 19 03:48:01 zmail zmmailboxdmgr[220066]: assuming no other instance is running
Jun 19 03:48:01 zmail zmmailboxdmgr[220066]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jun 19 03:48:01 zmail zmmailboxdmgr[220066]: assuming no other instance is running
Jun 19 03:48:01 zmail zmmailboxdmgr[220066]: no manager process is running


actual issue:
==> /opt/zimbra/log/zmmailboxd.out <==
2022-06-18 23:26:02.000:INFO::main: Logging initialized @930ms to org.eclipse.jetty.util.log.StdErrLog
JettyMonitor monitoring thread pool QueuedThreadPool[qtp93314457]@58fdd99{STOPPED,10<=0<=250,i=0,r=-1,q=0}[NO_TRY]
2022-06-18 23:26:02.484:WARN:oejx.XmlConfiguration:main: Deprecated constructor public org.eclipse.jetty.util.ssl.SslContextFactory() in file:///opt/zimbra/mailboxd/etc/jetty.xml
2022-06-18 23:26:03.119:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.120:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.120:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.121:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.121:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.122:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.126:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.127:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.127:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.127:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Integer(java.lang.String) throws java.lang.NumberFormatException in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
2022-06-18 23:26:03.128:WARN:oejx.XmlConfiguration:main: Deprecated constructor public java.lang.Boolean(java.lang.String) in file:///opt/zimbra/mailboxd/etc/jetty-setuid.xml
Fatal error: exception while binding to ports
java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target
at com.zimbra.common.soap.W3cDomUtil.<clinit>(W3cDomUtil.java:69)
at com.zimbra.common.localconfig.LocalConfig.<init>(LocalConfig.java:174)
at com.zimbra.common.localconfig.LocalConfig.load(LocalConfig.java:387)
at com.zimbra.common.localconfig.LocalConfig.<clinit>(LocalConfig.java:392)
at com.zimbra.common.localconfig.LC.get(LC.java:1539)
at com.zimbra.common.localconfig.KnownKey.booleanValue(KnownKey.java:158)
at com.zimbra.common.handlers.PrivilegedHandler.openPorts(PrivilegedHandler.java:70)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.invokeMethod(XmlConfiguration.java:765)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.invokeMethod(XmlConfiguration.java:760)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.call(XmlConfiguration.java:979)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.call(XmlConfiguration.java:942)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:515)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:468)
at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:380)
at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$3(XmlConfiguration.java:1893)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1857)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:218)
at org.eclipse.jetty.start.Main.start(Main.java:491)
at org.eclipse.jetty.start.Main.main(Main.java:77)
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:587)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
... 28 more




gonna try to burn down the server and reinstall some of the packages.

i had to go the very long route - cannot say if i had the wrong approach or what was going on.
I did the long postponed/doubted upgrade to zextras OSS v9, with proxy disabled (just to be sure), then did the downgrade of the packages via

Code: Select all

yum downgrade zimbra-core-components-3.0.11-1zimbra8.8b1.el8.x86_64 zimbra-jetty-distribution-9.4.18.v20190429-2.r8.x86_64 zimbra-ldap-components-2.0.5-1zimbra8.8b1.el8.x86_64 zimbra-openjdk-13.0.1-1zimbra8.8b1.el8.x86_64
For that command to work well I also had to disable the other repos in /etc/yum.repos.d/zimbra.repo

Code: Select all

[zimbra]
name=Zimbra RPM Repository
baseurl=https://repo.zimbra.com/rpm/87/rhel8
gpgcheck=1
enabled=0
[zimbra-8815-oss]
name=Zimbra New RPM Repository
baseurl=https://repo.zimbra.com/rpm/8815/rhel8
gpgcheck=1
enabled=0
[zimbra-90-oss]
name=Zimbra New RPM Repository
baseurl=https://repo.zimbra.com/rpm/90/rhel8
gpgcheck=1
enabled=1

My zmmproxy is now half-broken / half-enabled / not installed, but that's really a harmless issue compared to the imaginary port listener of before.

Running version now:

Code: Select all

Release 9.0.0_ZEXTRAS_20220402.RHEL8_64_20220419075929 RHEL8_64 FOSS edition.

I also switched from CentOS8 (the system had an issue with -STREAM-) to Oracle Linux 8 using centos2oel.

My lessons learned are:
- should not have missed this system had fallen out of centos-stream and its repos were dead
- should have switched to OEL right after the centos stream announcement
- a preferred multi-server setup would limit cross-service impact
- should have noticed zmbackup had been dead due to an ip change. point things at 127.0.0.1 unless you have a reason
- it was a massive mistake that this system also didn't have yum-transactions plugin - at least it had etckeeper running
- it does not really appear as if zextras has sufficient build infra / turnaround to deliver better builds than the upstream


if i had a wish, or someone cares about advice:
- it would help iif the header comments in the jetty xml files were a bit more up to date
- disabling/enabling the proxy and switching the ports could use better encapsulation
Post Reply