zmconfigd not running error - all possible fix
Hi..so if anyone *still* getting zmconfigd not running error on 7.1.1 even after Patch 2
Following is the information on tested fix
OS: RHEL/CentOS 5 fresh minimal install
Zimbra NE (OSS version should behave same): 7.1.1 + Patch 2 (link for Patch http://files2.zimbra.com/downloads/7....1_GA_3213.tgz )
the zimbra install will give
main culprits are three things
zmconfigd is not running
1) NetCat package: yum install nc
2) Which package: yum install which
3) IPV6: NETWORKING_IPV6=no in /etc/sysconfig/network
* I don't know if this is of any problem but i did see "address already in use" for 7171 port in /opt/zimbra/log/zmconfigd.log
Hope this helps
I bet which is already installed / not solved for me
There is no "which" package.
Originally Posted by Heatryn
I bet it's already installed, just try:
If you get
then you're fine.
By the way I find this a really serious issue and it looks like the OS version has not been tested on Ubuntu 64 although the package is available. Zimbra reminded me that 7.1.1 is a "critical update"..
I installed the patch (zcs-patch-7.1.1_GA_3213) but the issue persists.
Starting zimbra makes my cpu stay put at 100%, makes grow /var/log/zimbra-stats.log at a reate of 3Gb in 15min... it's really not pretty.
According to quanah it's unwise to downgrade but at this point I really don't see any alternative.
ps: disabling ipv6 in Ubuntu-like systems:
add the following to /etc/sysctl.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
found a workaround: disable all logging
Yay :), disabling all logging was the workaround. This is perfectly ok if you can live with the fact that the admin console is not showing correct information about the server status.
What I did:
- stop zmlogger with
- fix file /etc/rsyslog.conf which doesn't get cleaned up by the zimbra install script.
I removed all entries (at the end of the file) that look similar to these:
I found this valuable information at Daniel's blog at numlock.ch. :cool:
This prevents rsyslog from doing crazy logging but I still had zmlogger acting up.
- now disable the logging service and prevent it from being run by the logrotate script:
comment out the starting commands in the logrotate script /etc/logrotate.d/zimbra.
zmprov ms $(hostname) -zimbraServiceEnabled logger
Look for lines including one of the following (I found 4):
(comes from this post)
su - zimbra -c "/opt/zimbra/bin/zmswatchctl ..
su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl ..
Now my cpus were finally back to <2% again with a load average of 0.10.
I hope somebody can save a couple of hours and grey hair with this.
Also I'll open a bug report.