Server status data is not available

[riogd]

This just happened to me after upgrading from 4.5.5 NE Ubuntu -> 4.5.6 NE Ubuntu. Prior to the upgrade it worked fine, presently the status page reports the same error reported:

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

I have verified that cron is installed which it is. And again this worked pre-upgrade to 4.5.6 NE. Also "zmcontrol status" reports everything as running.
Lastly a "ps auxw | grep logger" reports the following:

zimbra   24175  0.0  0.0   4268  1792 pts/0    S    12:44   0:00 /bin/sh /opt/zimbra/logger/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.logger.cnf --ledir=/opt/zimbra/logger/mysql/libexec
zimbra   24221  0.0  0.2   8172  4396 pts/0    S    12:44   0:00 /usr/bin/perl /opt/zimbra/libexec/zmlogger
zimbra   24236  0.1  0.7 102068 14828 pts/0    Sl   12:44   0:23 /opt/zimbra/logger/mysql/libexec/mysqld --defaults-file=/opt/zimbra/conf/my.logger.cnf --basedir=/opt/zimbra/logger/mysql --datadir=/opt/zimbra/logger/db/data --pid-file=/opt/zimbra/logger/db/mysql.pid --skip-external-locking --port=7307 --socket=/opt/zimbra/logger/db/mysql.sock

If any workarounds are found for the bug I would be happy to try them.

Cheers,

RioGD

[jholder]

I reopened this bug:
Bug 11441 - ubuntu: logging and server statistics not working after install

[riogd]

This is very mysterious. I left the admin login open over the weekend, just went to access it right now and had to login due to it being expired.
Without any attempts at fixing the logger page on my end it is working again.
I have no idea what would cause it to sometimes work and sometimes not. The only thing which appeared to be the trigger in my case was the upgrade from 4.5.5 to 4.5.6 but since I didn't do anything to fix it and it magically started working again I suspect it didn't have anything to do with the upgrade.
Thanks for reopening the bug. If I notice anything which would help contribute to finding the problem I will update it.

Cheers,

RioGD

[danfluidmind]

I just did a fresh install of 4.5.6 from the Ubuntu package and had the exact same problem. Cron is installed and running and the zimbra logger is running. Yesterday, all day, I got the message that no status info was available. But today it gives me the status. Very mysterious indeed.

[Stergil]

Originally Posted by danfluidmind

I just did a fresh install of 4.5.6 from the Ubuntu package and had the exact same problem. Cron is installed and running and the zimbra logger is running. Yesterday, all day, I got the message that no status info was available. But today it gives me the status. Very mysterious indeed.

I had the same problem, which seems to have cleared up when I resolved my issue with the antivirus not starting properly. Since I increased the interval to the recommended 180 seconds the av works perfectly and the logger always shows as being started. Grant it, it's only been a couple of days.

Follow this post for details on what I'm referring to. (Specifically post #10 in that thread)
http://www.zimbra.com/forums/install...happening.html

[gareth]

I've recently seen this problem on 4.5.5, 4.5.6 and 5.0B3.

My "fix" (doesn't work) is to run zmsyslogsetup, depending in the system, after potentially "fixing" LOCALHOST to a 'correct' value.

This leaves me with the zmcontrol status reporting Ok, and the status page in the control panel working, but with a red cross against "stats".

It will look Ok for a minute or so, then it will say "(data is stale)" next to each entry (following a refresh). Then I get bored and go away, when I come back "later" and hit refresh, it comes back with blue ticks (bar stats) .. then refreshing a minute lated gives me he "(data is stale)" entry again.

So, I'm wondering if this is hostname related?

Everything else seems to be running Ok ... (?!)

I've tried this on 4 machine, 1 64 bit in a chroot and 3 native 32 bit, all are running Ubuntu Feisty.

[riogd]

Well it turns out this wasn't as fixed as I thought it was. The logger shows that it is running, but the graphs are not displaying any new data for the last month. I hadn't looked at them and thus hadn't noticed they were no longer populating with data. zmmsgtrace also shows no data newer than the same amount of time.
It is as if whatever watches the log files isn't working correctly, however the following is shown as running:

zimbra    6753  0.0  0.2   5688  3948 ?        S    Aug04   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/zimbra.log
zimbra   18261  0.0  0.2   7060  4252 ?        S    Aug05   9:43 /usr/bin/perl /opt/zimbra/libexec/zmlogger
zimbra    8898  0.0  0.2   6928  4168 pts/0    S    Sep05   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/zimbra.log
zimbra    9459  0.0  0.2   6932  4188 pts/0    S    Sep05   0:00 /usr/bin/perl /opt/zimbra/libexec/swatch --config-file=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/zimbra.log
zimbra   31737  0.0  0.2   8296  4452 pts/0    S    06:25   0:02 /usr/bin/perl /opt/zimbra/libexec/zmlogger

Any ideas ?

Cheers,

RioGD

[tgx]

Running 5.0 Beta 3 on OpenSuSE 10.2

Same logger problems as reported elsewhere, but I have
this piece of info to add that I captured during my install:

Setting up zimbra crontab...cp: cannot stat '/var/spool/cron/tabs/zimbra': No such file or directory
Done
Setting up syslog.conf...Starting SuSEconfig, the SuSE Configuration Tool...
Running module syslog-ng only
Reading /etc/sysconfig and updating the system...
Module syslog-ng does not exist
Finished.

[tgx]

FWIW, the crontab file IS created and I just checked syslog-ng IS installed.

just did a grep and /sbin/syslog-ng is running also
zmcontrol status says logger is running.

I checked in /etc/sysconfig and in that file there is 'syslog' but no mention of 'syslog-ng'
Could this be a simple naming problem?

[jbwiv]

I'm having the same problems you guys are on Fedora Core 5. Hoping there's a solution soon!