Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Ask questions about your setup or get help installing ZCS server (ZD section below).
lhtibi
Posts: 1
Joined: Sat Sep 24, 2022 12:38 pm

Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by lhtibi »

Hello Guys,

my problem is the following, after patching our Zimbra to latest patchlevel, the mailbox service can not be started.

zmcontrol -v
Release 9.0.0_GA_3924.RHEL7_64_20200331010312 RHEL7_64 NETWORK edition, Patch 9.0.0_P26.

[zimbra@consact ~]$ cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)

Code: Select all

[zimbra@consact ~]$ zmcontrol status
Host consact.hu
	amavis                  Running
	antispam                Running
	antivirus               Running
	convertd                Running
	dnscache                Running
	ldap                    Running
	logger                  Running
	mailbox                 Stopped
		zmmailboxdctl is not running.
	memcached               Running
	mta                     Running
	opendkim                Running
	proxy                   Running
	service webapp          Stopped
		zmmailboxdctl is not running.
	snmp                    Running
	spell                   Running
	stats                   Running
	zimbra webapp           Stopped
		zmmailboxdctl is not running.
	zimbraAdmin webapp      Stopped
		zmmailboxdctl is not running.
	zimlet webapp           Stopped
		zmmailboxdctl is not running.
	zmconfigd               Running
In the /opt/zimbra/log/zmmailboxd.out I can see following possible problems:

Code: Select all

2022-09-24 14:23:04.859:WARN:oejw.WebAppContext:main: Failed startup of context o.e.j.w.WebAppContext@4d0f2471{/,file:///opt/zimbra/jetty_base/webapps/zimbra/,UNAVAILABLE}{/opt/zimbra/mailboxd/webapps/zimbra}
javax.servlet.ServletException: Malformed rule: zimbraHttpContextPathBasedThreadPoolBalancingFilterRules

Code: Select all

2022-09-24 14:23:04.861:INFO:oejsh.ContextHandler:main: Stopped o.e.j.w.WebAppContext@6ab778a{Zimbra Service,/service,null,STOPPED}{/opt/zimbra/mailboxd/webapps/service}
2022-09-24 14:23:04.862:INFO:oejs.session:main: node0 Stopped scavenging
2022-09-24 14:23:04.871:WARN:oejx.XmlConfiguration:main: 
java.security.PrivilegedActionException: javax.servlet.ServletException: Malformed rule: zimbraHttpContextPathBasedThreadPoolBalancingFilterRules

Code: Select all

Caused by: 
javax.servlet.ServletException: Malformed rule: zimbraHttpContextPathBasedThreadPoolBalancingFilterRules
and lot of entries regarding malformed rules like:

Code: Select all

Caused by: MultiException[java.lang.NumberFormatException: For input string: "%%zimbraHttpDosFilterMaxRequestsPerSec%%", javax.servlet.ServletException: Malformed rule: zimbraHttpContextPathBasedThreadPoolBalancingFilterRules]
	at org.eclipse.jetty.util.MultiException.ifExceptionThrow(MultiException.java:122)
	at org.eclipse.jetty.server.Server.doStart(Server.java:413)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
	at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$3(XmlConfiguration.java:1907)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
	... 8 more
	Suppressed: java.lang.NumberFormatException: For input string: "%%zimbraHttpDosFilterMaxRequestsPerSec%%"
		at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
		at java.base/java.lang.Integer.parseInt(Integer.java:654)
		at java.base/java.lang.Integer.parseInt(Integer.java:786)
		at org.eclipse.jetty.servlets.DoSFilter.init(DoSFilter.java:214)
		at com.zimbra.cs.servlet.DoSFilter.init(DoSFilter.java:41)
		at org.eclipse.jetty.servlet.FilterHolder.initialize(FilterHolder.java:140)
		at org.eclipse.jetty.servlet.ServletHandler.lambda$initialize$0(ServletHandler.java:731)
		at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
		at java.base/java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:734)
		at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
		at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:755)
		at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
		at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449)
		at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414)
		at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916)
		at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
		at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:426)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.server.handler.DebugHandler.doStart(DebugHandler.java:140)
		at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
		at org.eclipse.jetty.server.Server.start(Server.java:423)
		at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
		at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
		at org.eclipse.jetty.server.Server.doStart(Server.java:387)
		... 11 more

Code: Select all

Caused by: [CIRCULAR REFERENCE: java.lang.NumberFormatException: For input string: "%%zimbraHttpDosFilterMaxRequestsPerSec%%"]
Actually the mailbox service is running for a couple of seconds then fails:

Code: Select all

[zimbra@consact ~]$ zmmailboxdctl start
Starting mailboxd...done.
[zimbra@consact ~]$ zmmailboxdctl status
mailboxd is running.
[zimbra@consact ~]$ zmmailboxdctl status
mailboxd is not running.
Does anyone have an idea about what can we do to fix this?

Thank you for your help in advance!
gmelis
Posts: 6
Joined: Sun Mar 03, 2019 6:46 pm

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by gmelis »

Did you find any solution for that? I seem to be in the same predicament.
stasouv
Advanced member
Advanced member
Posts: 63
Joined: Sat Sep 13, 2014 2:25 am
ZCS/ZD Version: 8.8.15_GA_3869.RHEL7_64_20190917004

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by stasouv »

Hello,

we have the exact same problem after upgrading 8.8.15 to Patch 34.

RHEL7_64 FOSS edition, Patch 8.8.15_P34.

This is rather frustrating, we have a broken server...

It's the 2nd time in 3 updates that there is a huge problem with the patch (Patch 32 broke the LMTP server)

update:
We got through the ivalid number format by manually setting the value in the xml.in files (not a solution), but we are still getting the:

Code: Select all

Caused by: java.security.PrivilegedActionException: javax.servlet.ServletException: Malformed rule: zimbraHttpContextPathBasedThreadPoolBalancingFilterRules
stasouv
Advanced member
Advanced member
Posts: 63
Joined: Sat Sep 13, 2014 2:25 am
ZCS/ZD Version: 8.8.15_GA_3869.RHEL7_64_20190917004

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by stasouv »

We have manage to make the server to run.

However:
- The solution applied is NOT recommended
- It is unknown if other things do not work
- I can't believe I even had to come up with this solution. :roll: :roll: :roll:

-- NOTE: admin web interface not yet fixed, apparently I need to also manually modify <param-value>%%zimbraAdminPort%%</param-value> --


Namely, I had to "fix/patch" the following files and hardcode values into them:

A. Compilation errors in zmmailbox.out

Under /opt/zimbra/jetty:

etc/jetty.xml.in
etc/zimbra.web.xml.in
etc/zimbraAdmin.web.xml.in
webapps/zimbra/WEB-INF/web.xml
webapps/zimbraAdmin/WEB-INF/web.xml
zimbra/WEB-INF/web.xml
zimbraAdmin/WEB-INF/web.xml

In these files, I hard applied the values:

Code: Select all

%%zimbraHttpDosFilterMaxRequestsPerSec%%
to
100 (arbitrary)

Code: Select all

webapps/zimbraAdmin/WEB-INF/web.xml:    
<param-value>%%list VAR:zimbraHttpContextPathBasedThreadPoolBalancingFilterRules ,%%</param-value>
to
<param-value>zimbraAdmin:max=100%</param-value> <!-- arbitrary values -->

Code: Select all

webapps/zimbra/WEB-INF/web.xml:    
<param-value>%%list VAR:zimbraHttpContextPathBasedThreadPoolBalancingFilterRules ,%%</param-value>
to
<param-value>service:max=100%,soap:max=100%,zimbra:max=100%</param-value> <!-- arbitrary values -->
B. And after that, compilation worked, however there was no service. Not until we changed that too:

Code: Select all

<env-entry-value>%%zimbraMailPort%%</env-entry-value>
to
<env-entry-value>8080</env-entry-value>
Last edited by stasouv on Sun Feb 26, 2023 1:48 pm, edited 1 time in total.
User avatar
barrydegraaff
Zimbra Employee
Zimbra Employee
Posts: 242
Joined: Tue Jun 17, 2014 3:31 am
Contact:

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by barrydegraaff »

Thanks for sharing the work-around, the development team is investigating the cause of the issue.
--
Barry de Graaff
Email: barry.degraaff [at] synacor [dot] com
Admin of Zimbra-Community Github: https://github.com/orgs/Zimbra-Community/ and the
Zimlet Gallery https://gallery.zetalliance.org/extend/
uttam.takalkar
Zimbra Employee
Zimbra Employee
Posts: 53
Joined: Wed Jul 27, 2022 6:16 am

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by uttam.takalkar »

Please open the zimbra support case and provide patch install logs, it seems incomplete installation
stasouv
Advanced member
Advanced member
Posts: 63
Joined: Sat Sep 13, 2014 2:25 am
ZCS/ZD Version: 8.8.15_GA_3869.RHEL7_64_20190917004

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by stasouv »

We have FOSS edition, so no support case.

Here is the yum log

Code: Select all

Oct 17 22:53:21 Updated: zimbra-mbox-admin-console-war-8.8.15.1663579957-1.r7.x86_64
Oct 17 22:53:21 Updated: zimbra-os-requirements-1.0.2-1zimbra8.7b1.el7.x86_64
Oct 17 22:53:21 Updated: zimbra-core-components-2.0.19-1zimbra8.8b1.el7.x86_64
Oct 17 22:53:24 Updated: zimbra-common-core-jar-8.8.15.1663929866-1.r7.x86_64
Oct 17 22:53:34 Updated: zimbra-common-core-libs-8.8.15.1663926687-1.r7.x86_64
Oct 17 22:53:41 Updated: zimbra-mbox-store-libs-8.8.15.1663926687-1.r7.x86_64
Oct 17 22:53:41 Updated: zimbra-amavisd-2.10.1-1zimbra8.7b2.el7.x86_64
Oct 17 22:53:41 Updated: zimbra-mta-components-1.0.16-1zimbra8.8b1.el7.x86_64
Oct 17 22:54:33 Updated: zimbra-mbox-webclient-war-8.8.15.1664792862-1.r7.x86_64
Oct 17 22:59:37 Updated: zimbra-patch-8.8.15.1664798903.p34-1.r7.x86_64
Oct 17 22:59:39 Updated: zimbra-mta-patch-8.8.15.1664292023.p34-1.r7.x86_64
Oct 17 23:00:07 Updated: zimbra-proxy-patch-8.8.15.1664359370.p34-1.r7.x86_64
Oct 17 23:00:07 Updated: zimbra-ldap-components-1.0.19-1zimbra8.8b1.el7.x86_64
Oct 18 10:47:22 Installed: zimbra-ldap-patch-8.8.15.1664359370.p34-1.r7.x86_64
Ldap patch was not installed automatically, we had to install it manually (following the "manual installation" directive, as we shouldn't have to).

Also, in the release notes it is stated that this should be installed:

Code: Select all

zimbra-patch                                      -> 8.8.15.1664798903.p34-2
Yet only .p34-1 was available (still, p34-2 not available).

Here is the installation log, from yum.

Code: Select all

747:98a12025dcd5f019358763a13c6a20099df8f33e
0
1
installed:747:e19f0a53e05f4b4d9a8491fadf9206b89ffd1b14
26
mbr: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1664792862,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1658466576,1.r7@i:updates zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson
  depends_on: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a
  updates: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1658466576,1.r7@i
mbr: zimbra-core-components,x86_64,0,2.0.18,1zimbra8.8b1.el7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-core-components,x86_64,0,2.0.19,1zimbra8.8b1.el7@a:updatedby
  updated_by: zimbra-core-components,x86_64,0,2.0.19,1zimbra8.8b1.el7@a
mbr: zimbra-common-core-jar,x86_64,0,8.8.15.1658837424,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-common-core-jar,x86_64,0,8.8.15.1663929866,1.r7@a:updatedby
  updated_by: zimbra-common-core-jar,x86_64,0,8.8.15.1663929866,1.r7@a
mbr: zimbra-ldap-components,x86_64,0,1.0.18,1zimbra8.8b1.el7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-ldap-components,x86_64,0,1.0.19,1zimbra8.8b1.el7@a:updatedby
  updated_by: zimbra-ldap-components,x86_64,0,1.0.19,1zimbra8.8b1.el7@a
mbr: zimbra-common-core-jar,x86_64,0,8.8.15.1663929866,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-common-core-jar,x86_64,0,8.8.15.1658837424,1.r7@i:updates zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a:dependson zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a:dependson
  depends_on: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a
  updates: zimbra-common-core-jar,x86_64,0,8.8.15.1658837424,1.r7@i
mbr: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i:updates
  updates: zimbra-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i
mbr: zimbra-common-core-libs,x86_64,0,8.8.15.1654854265,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-common-core-libs,x86_64,0,8.8.15.1663926687,1.r7@a:updatedby
  updated_by: zimbra-common-core-libs,x86_64,0,8.8.15.1663926687,1.r7@a
mbr: zimbra-os-requirements,x86_64,0,1.0.0,1zimbra8.7b1.el7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: dep
  reinstall: False
  relatedto: zimbra-os-requirements,x86_64,0,1.0.2,1zimbra8.7b1.el7@a:updatedby
  updated_by: zimbra-os-requirements,x86_64,0,1.0.2,1zimbra8.7b1.el7@a
mbr: zimbra-mta-patch,x86_64,0,8.8.15.1658841204.p33,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a:updatedby
  updated_by: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a
mbr: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mta-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i:updates
  updates: zimbra-mta-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i
mbr: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b2.el7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: dep
  reinstall: False
  relatedto: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b1.el7@i:updates zimbra-mta-components,x86_64,0,1.0.16,1zimbra8.8b1.el7@a:dependson
  depends_on: zimbra-mta-components,x86_64,0,1.0.16,1zimbra8.8b1.el7@a
  updates: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b1.el7@i
mbr: zimbra-patch,x86_64,0,8.8.15.1658841204.p33,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:updatedby
  updated_by: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a
mbr: zimbra-core-components,x86_64,0,2.0.19,1zimbra8.8b1.el7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-core-components,x86_64,0,2.0.18,1zimbra8.8b1.el7@i:updates zimbra-common-core-jar,x86_64,0,8.8.15.1663929866,1.r7@a:dependson zimbra-common-core-libs,x86_64,0,8.8.15.1663926687,1.r7@a:dependson zimbra-ldap-components,x86_64,0,1.0.19,1zimbra8.8b1.el7@a:dependson zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a:dependson zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a:dependson
  depends_on: zimbra-common-core-jar,x86_64,0,8.8.15.1663929866,1.r7@a zimbra-common-core-libs,x86_64,0,8.8.15.1663926687,1.r7@a zimbra-ldap-components,x86_64,0,1.0.19,1zimbra8.8b1.el7@a zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a
  updates: zimbra-core-components,x86_64,0,2.0.18,1zimbra8.8b1.el7@i
mbr: zimbra-mbox-store-libs,x86_64,0,8.8.15.1663926687,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-store-libs,x86_64,0,8.8.15.1654854265,1.r7@i:updates zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson
  depends_on: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a
  updates: zimbra-mbox-store-libs,x86_64,0,8.8.15.1654854265,1.r7@i
mbr: zimbra-os-requirements,x86_64,0,1.0.2,1zimbra8.7b1.el7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: dep
  reinstall: False
  relatedto: zimbra-os-requirements,x86_64,0,1.0.0,1zimbra8.7b1.el7@i:updates zimbra-core-components,x86_64,0,2.0.19,1zimbra8.8b1.el7@a:dependson
  depends_on: zimbra-core-components,x86_64,0,2.0.19,1zimbra8.8b1.el7@a
  updates: zimbra-os-requirements,x86_64,0,1.0.0,1zimbra8.7b1.el7@i
mbr: zimbra-ldap-components,x86_64,0,1.0.19,1zimbra8.8b1.el7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-ldap-components,x86_64,0,1.0.18,1zimbra8.8b1.el7@i:updates
  updates: zimbra-ldap-components,x86_64,0,1.0.18,1zimbra8.8b1.el7@i
mbr: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1658466576,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1664792862,1.r7@a:updatedby
  updated_by: zimbra-mbox-webclient-war,x86_64,0,8.8.15.1664792862,1.r7@a
mbr: zimbra-mta-components,x86_64,0,1.0.15,1zimbra8.8b1.el7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mta-components,x86_64,0,1.0.16,1zimbra8.8b1.el7@a:updatedby
  updated_by: zimbra-mta-components,x86_64,0,1.0.16,1zimbra8.8b1.el7@a
mbr: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b1.el7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: dep
  reinstall: False
  relatedto: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b2.el7@a:updatedby
  updated_by: zimbra-amavisd,x86_64,0,2.10.1,1zimbra8.7b2.el7@a
mbr: zimbra-common-core-libs,x86_64,0,8.8.15.1663926687,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-common-core-libs,x86_64,0,8.8.15.1654854265,1.r7@i:updates zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a:dependson zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a:dependson
  depends_on: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a
  updates: zimbra-common-core-libs,x86_64,0,8.8.15.1654854265,1.r7@i
mbr: zimbra-proxy-patch,x86_64,0,8.8.15.1658841204.p33,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a:updatedby
  updated_by: zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7@a
mbr: zimbra-mbox-store-libs,x86_64,0,8.8.15.1654854265,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-store-libs,x86_64,0,8.8.15.1663926687,1.r7@a:updatedby
  updated_by: zimbra-mbox-store-libs,x86_64,0,8.8.15.1663926687,1.r7@a
mbr: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1663579957,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1653031987,1.r7@i:updates zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a:dependson
  depends_on: zimbra-patch,x86_64,0,8.8.15.1664798903.p34,1.r7@a
  updates: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1653031987,1.r7@i
mbr: zimbra-mta-components,x86_64,0,1.0.16,1zimbra8.8b1.el7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mta-components,x86_64,0,1.0.15,1zimbra8.8b1.el7@i:updates zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a:dependson
  depends_on: zimbra-mta-patch,x86_64,0,8.8.15.1664292023.p34,1.r7@a
  updates: zimbra-mta-components,x86_64,0,1.0.15,1zimbra8.8b1.el7@i
mbr: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1653031987,1.r7 20
  repo: installed
  ts_state: ud
  output_state: 90
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1663579957,1.r7@a:updatedby
  updated_by: zimbra-mbox-admin-console-war,x86_64,0,8.8.15.1663579957,1.r7@a
mbr: zimbra-proxy-patch,x86_64,0,8.8.15.1664359370.p34,1.r7 70
  repo: zimbra-8815-oss
  ts_state: u
  output_state: 10
  isDep: False
  reason: user
  reinstall: False
  relatedto: zimbra-proxy-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i:updates
  updates: zimbra-proxy-patch,x86_64,0,8.8.15.1658841204.p33,1.r7@i
yogesh.dasi
Zimbra Employee
Zimbra Employee
Posts: 54
Joined: Tue Oct 18, 2022 11:22 am

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by yogesh.dasi »

Check if the /tmp folder has permission for zimbra user, if the permissions are not there updating the configs will be restricted to web.xml
Refer https://wiki.zimbra.com/wiki/King0770-N ... ons-on-tmp

Set right permission to /tmp folder and restart the services with zmcontrol restart

Check the mailbox is running with zmcontrol status
gmelis
Posts: 6
Joined: Sun Mar 03, 2019 6:46 pm

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by gmelis »

The /tmp directory was and is writeable. It was not a permissions problem, it was more like not finding values for the variables defined in the XML files.
deepak.gautam
Zimbra Employee
Zimbra Employee
Posts: 19
Joined: Sun Jun 19, 2022 1:41 pm

Re: Zimbra 9: zmmailboxdctl is not starting after applying latest patches(p26)

Post by deepak.gautam »

stasouv wrote:We have FOSS edition, so no support case.



Ldap patch was not installed automatically, we had to install it manually (following the "manual installation" directive, as we shouldn't have to).


[/code]
LDAP patch is not getting installed automatically.
Post Reply