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

Quote:

---

zmconfigd Stopped
zmconfigd is not running

---

main culprits are three things
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
Raj

If neither nc/netcat nor which are installed then a normal server installation of the OS was not done, which is one of the basic requirements for installing ZCS as noted in the installation guide.

well.. done more than 500+ zimbra installs and never installed these till v7

even the latest install guide dont mention it in requirements:
http://www.zimbra.com/docs/os/latest...uirements.html

Quote:

---

Other Dependencies
For Red Hat Enterprise, Fedora Core and SUSE operating systems, the server must also have the following installed:
• NPTL. Native POSIX Thread Library
• Sudo. Superuser, required to delegate admins.
• libidn. For internationalizing domain names in applications (IDNA)
• GMP. GNU Multiple-Precision Library.
• compat-libstdc ++-33. Compatibility Standard C++ libraries.
For RHEL servers only

For SLES10 - compat-libstdc++-5.0.7
For SLES11 - libstdc++33

For Ubuntu 8.04
• Sudo
• libidn11
• libpcre3
• libexpat1
• libstdc++6
• libstdc++5
• libgmp3C2
Note: Ubuntu 8 (64-bit) requires libperl 5.8.

---

Even the installer dont complaint for these packages and happily install everything breaking zmconfigd servcie even after patch 2

it was a surprise to me as even i who installs zimbra thru PXE/KS in < 10 min spent few hours looking thru everything.

we should either update the documentation or install sctipt to catch these

Thanks
Raj

What package do I need to install for the "which" constraint under Ubuntu 10.04 64 bit?

apt-get install which doesn't find the right package.

Quote:

---

Originally Posted by Heatryn

What package do I need to install for the "which" constraint under Ubuntu 10.04 64 bit?

apt-get install which doesn't find the right package.

---

did you tried apt-cache search which ?

Quote:

---

Originally Posted by Heatryn

What package do I need to install for the "which" constraint under Ubuntu 10.04 64 bit?

apt-get install which doesn't find the right package.

---

There is no "which" package.
I bet it's already installed, just try:

Code:

---

which which

---

If you get

Code:

---

/usr/bin/which

---

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

Code:

---

#disable ipv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

---

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:

1. stop zmlogger with
   Code:

   ---

   zmloggerctl stop

   ---

2. 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:
   
   Code:

   ---

   local0.* @mail.yourserver.com
local1.* @mail.yourserver.com
auth.* @mail.yourserver.com
local0.* -/var/log/zimbra.log
local1.* -/var/log/zimbra-stats.log
auth.* -/var/log/zimbra.log
mail.* @mail.yourserver.com
mail.* -/var/log/zimbra.log

   ---

   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.
   
3. now disable the logging service and prevent it from being run by the logrotate script:
   
   Code:

   ---

   zmprov ms $(hostname) -zimbraServiceEnabled logger

   ---

   comment out the starting commands in the logrotate script /etc/logrotate.d/zimbra.
   Look for lines including one of the following (I found 4):
   
   Code:

   ---

   su - zimbra -c "/opt/zimbra/bin/zmswatchctl ..
su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl ..

   ---

   (comes from this post)

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.

Quote:

---

Originally Posted by raj

well.. done more than 500+ zimbra installs and never installed these till v7

even the latest install guide dont mention it in requirements:
http://www.zimbra.com/docs/os/latest...uirements.html


Even the installer dont complaint for these packages and happily install everything breaking zmconfigd servcie even after patch 2

it was a surprise to me as even i who installs zimbra thru PXE/KS in < 10 min spent few hours looking thru everything.

we should either update the documentation or install sctipt to catch these

Thanks
Raj

---

We only list packages that are not part of a standard installation as requirements. It has always been this way. I've never had to install which, nc/netcat, file, or any number of utilities separately when doing OS installs, because they are standard packages to the OS. I.e., which, netcat/nc, file, etc are all part of RedHat, Ubuntu, SLES, etc, standard installations. If you've managed to install these without those utilities present, you've done something odd.

--Quanah

Quote:

---

Originally Posted by rosch

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.

---

I'm unclear why you think the 7.1.1 P2 patch has not been tested on Ubuntu 64. All of our patches are tested on every supported platform prior to release.

Quote:

---

Originally Posted by quanah

I'm unclear why you think the 7.1.1 P2 patch has not been tested on Ubuntu 64. All of our patches are tested on every supported platform prior to release.

---

Well I wrote that because I spent a whole night trying to make 7.1.1 work and I was not in the best of moods :). Please don't take it personally.

I was not talking specifically about the patch but since I found at least one other user with similar symptoms I dare say that the testing was not thorough enough. Or else my system differs enough from the tested one allowing the race condition to occur..