[SOLVED] Logging Service to Admin Console Problem

[Phloyd]

After the upgrade to 5.0.11, everything seems to be up and running. All of the logging is working, all of the entries are going to the database, etc. However, the admin console does not reflect this. The admin console states:

Server status data is not available. To see the server status, logger service must be installed.

Additionally, all of the server statistics with respect to message count, message volume, anti-spam/antivirus are no longer working. The graphs only show the data up to the upgrade and are blank thereafter. I am able to see the session and mailbox quota information.

Any suggestions as to where I should start looking on this?

[phoenix]

Stop Zimbra with a 'zmcontrol stop', check to see if there's any zimbra threads running and kill them - restart Zimbra and see if that fixes the problem. failing that, check the log files for any errors.

[Phloyd]

Thanks, I will try that tonight after users are logged off.

[Phloyd]

Well, I did as you suggested at about 5AM this morning. Stopped Zimbra, checked to make sure no zimbra related processes were running. Not sure on how to check threads as well?

Everything stopped and restarted without a problem, but the Initial problem with the admin console persists. I have looked at the log files and cannot see any obvious errors. Is there a particular log file that I need to be looking at?

[Phloyd]

when we did the update zimbra updated logrotate with this:

/var/log/zimbra.log {
daily
missingok
notifempty
create 0644 zimbra zimbra
postrotate
killall -HUP syslogd 2> /dev/null || true
kill -HUP `cat /opt/zimbra/log/swatch.pid 2> /dev/null` 2> /dev/null || true
kill -HUP `cat /opt/zimbra/log/logswatch.pid 2> /dev/null` 2> /dev/null || true
endscript
compress
}

We changed line 7 to read:

killall -HUP rsyslogd 2> /dev/null || true

[phoenix]

Sorry about the late reply, it seems you might have hit this bug. I'd suggest you use the script in comment #7 to replace the current zmlogswatchctl (keep a copy of the original) this should fix the problems with ghost processes being left running. You should also reverse you modification mentioned in your last post.