Same issue here.Martinwiertz wrote:Agree Kent. I am searching also for the last hours. I found this error happend several times over the last few years but can't find an 100% solution.
I didn't expected these update in the repos but they were there..... Especially update to P25 on v9.0 is more severe or more extensive updates.
mgmailadmin wrote:Hi Martin,
Can't speak for CZV but for us it absolutely started after the apt-get. Very disturbing that a clean install also suffers the same issue.
Again, any insight would be appreciated.
-Kent I.
zmmailboxdctl failing to run after most recent apt-get
Re: zmmailboxdctl failing to run after most recent apt-get
Re: zmmailboxdctl failing to run after most recent apt-get
Did you read the post immediately above yours?primepage wrote: Same issue here.
Re: zmmailboxdctl failing to run after most recent apt-get
Make sure the patch installation did not leave old libraries lying around. In my case old versions of the Apache CXF library had been left behind and caused issues. See viewtopic.php?f=15&t=70897 for details.
Re: zmmailboxdctl failing to run after most recent apt-get
Running Centos7, this has put me back running again. I had to do ldap before core components in order to avoid dependency issues.
yum downgrade zimbra-ldap-components.x86_64 0:2.0.5-1zimbra8.8b1.el7
yum downgrade zimbra-core-components.x86_64 0:3.0.11-1zimbra8.8b1.el7
yum downgrade zimbra-jetty-distribution.x86_64 0:9.4.18.v20190429-2.r7
yum downgrade zimbra-openjdk.x86_64 0:13.0.1-1zimbra8.8b1.el7
yum downgrade zimbra-ldap-components.x86_64 0:2.0.5-1zimbra8.8b1.el7
yum downgrade zimbra-core-components.x86_64 0:3.0.11-1zimbra8.8b1.el7
yum downgrade zimbra-jetty-distribution.x86_64 0:9.4.18.v20190429-2.r7
yum downgrade zimbra-openjdk.x86_64 0:13.0.1-1zimbra8.8b1.el7
-
- Posts: 25
- Joined: Wed Mar 10, 2021 3:35 pm
- Location: Ubuntu 18.04.5 LTS
- ZCS/ZD Version: 9.0.0.ZEXTRAS.202007114.UBUNTU18.64
Re: zmmailboxdctl failing to run after most recent apt-get
This is a life-saver!mgmailadmin wrote:Thanks @livelace. This was essential info.livelace wrote:Just registered to inform you guys about the same problem.
My system is Centos 7. And for avoiding this problem I had to downgrade some packages:
Removed:
zimbra-core-components.x86_64 0:3.0.12-1zimbra8.8b1.el7
zimbra-jetty-distribution.x86_64 0:9.4.46.v20220331-2.r7
zimbra-ldap-components.x86_64 0:2.0.6-1zimbra8.8b1.el7
zimbra-openjdk.x86_64 0:17.0.2-1zimbra8.8b1.el7
Installed:
zimbra-core-components.x86_64 0:3.0.11-1zimbra8.8b1.el7
zimbra-jetty-distribution.x86_64 0:9.4.18.v20190429-2.r7
zimbra-ldap-components.x86_64 0:2.0.5-1zimbra8.8b1.el7
zimbra-openjdk.x86_64 0:13.0.1-1zimbra8.8b1.el7
Right now all services works as expected.
In the Ubuntu world, at least in the 18.04.6 LTS platform I'm running, this translated to doing an apt-get install package=version downgrade operation.
The specifics would be:
To find out what is currently installed:Each line will spit out lots of stuff about dependencies as well as the version history at the bottom with the most current version at the top of the list.Code: Select all
sudo apt-cache showpkg zimbra-core-components sudo apt-cache showpkg zimbra-jetty-distribution sudo apt-cache showpkg zimbra-ldap-components sudo apt-cache showpkg zimbra-openjdk
You may not need to downgrade the zimbra-ldap-compenents package. It wasn't installed in my platform which seems odd but...
Following the versioning @Livelace documentented, The steps to downgrade would then be:You should be able to try to stop/start (or restart) next.Code: Select all
sudo apt-get install zimbra-core-components=3.0.11-1zimbra8.8b1.18.04 sudo apt-get install zimbra-jetty-distribution=9.4.18.v20190429-2.u18 sudo apt-get install zimbra-openjdk=13.0.1-1zimbra8.8b1.18.04 and optionally sudo apt-get install zimbra-ldap-components=2.0.5-1zimbra8.8b1.18.04
As I mentioned I had an issue with the zmcontrol start command in that when LDAP ran, it prompted for a sudo zimbra password.Code: Select all
zmcontrol stop zmcontrol start
After perusing this issue in other contexts, I dug into the /etc/sudoer.d configuration files and found that slapd was not being authorized to run with No password. The wiki article (here)https://wiki.zimbra.com/index.php?title=Sudoers on this subject was informative and helped resolve the issue. The bottom line was that the 02_zimbra-ldap configuration file was missing from /etc/sudoers.d/
The contents of that file is a single line used to authorize slapd:Once I cleaned that up, I was able to restart with all modules loading.Code: Select all
%zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmslapd
Hopefully others have success with this.
Very disappointing experience though.
Thanks!
What a ride... one must wonder why anyone would release a broken version as stable...
Chris