zmconfigd.log warnings

[frosticus]

I am seeing the following warnings in \opt\zimbra\log\zmconfigd.log at roughly one minute intervals.

Starting zmconfigd...zmconfigd is already running.
2012-02-02 07:58:17,552 zmconfigd WARNING [1207-MainThread] Fetching All configs
2012-02-02 07:58:17,956 zmconfigd WARNING [1207-MainThread] All configs fetched in 0.40 seconds
2012-02-02 07:58:21,772 zmconfigd WARNING [1207-MainThread] Watchdog: skipping service antivirus. Service not yet available for restarts.
2012-02-02 07:58:22,153 zmconfigd WARNING [1207-MainThread] All rewrite threads completed in 0.00 sec
2012-02-02 07:58:22,155 zmconfigd WARNING [1207-MainThread] All restarts completed in 0.00 sec
Starting zmconfigd...zmconfigd is already running.
2012-02-02 07:59:22,338 zmconfigd WARNING [1207-MainThread] Fetching All configs
2012-02-02 07:59:22,875 zmconfigd WARNING [1207-MainThread] All configs fetched in 0.54 seconds
2012-02-02 07:59:27,384 zmconfigd WARNING [1207-MainThread] Watchdog: skipping service antivirus. Service not yet available for restarts.

Oddly, there are portions of the log file that have no warning, just the following w/o timestamps:

Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.
Starting zmconfigd...zmconfigd is already running.

Is there something I can do resolve the issue, both the warnings and the "already running" restart attempts?

Regards,
Matt

[quanah]

I'm not sure why you believe services are being restarted. Nothing that you've posted indicates any such things. Those are informative message of what zmconfigd is doing. In order:

1) It fetched all configuration information from LDAP & localconfig. That took 0.40 seconds.

2) It skipped doing any restarts.

3) It completed rewriting anything that needed rewriting. Since nothing required a rewrite, this took 0 seconds.

4) Since there were no rewrites, no restarts were required. This took zero seconds.

The other set of information bits is the program that makes sure zmconfigd is running, named zmconfigdctl. It indicates that zmconfigd is running without needing any restart.

zmconfigd logs extensively due to the issues we initially had with its stability in the 7.0.0 time frame, which, as I already answered you, have long since been fixed.

There is ZERO indication of any service restarts occurring in the lines from the log file you have pasted.

I will note the express purpose of zmconfigd IS to restart services IF YOU MAKE CONFIGURATION CHANGES that REQUIRE a restart of a service. So, for example, if you change the NETWORKS you want postfix to consider as "MY" networks via the admin console or the command line with zmprov, zmconfigd will update the postfix configuration FOR YOU and then restart it.

I hope this explanation helps.

Regards,
Quanah