[SOLVED] Upgrade from 4.5.6 CE to 4.5.7 CE: stats service shown as stopped

[bjquinn]

For what it's worth, I'll just post a "me too".

Fresh install of 4.5.7, not an upgrade
CentOS5

I did a yum install sysstat which seemed to make zmcontrol status show the stats service as running.

However, I still have the problems mentioned by everyone else, namely -

1. I only seem to get anything interesting in the Admin interface stats page if I run zmgengraphs and such by hand, and even then I don't seem to get everything.

2. I *NEVER* get any AS/AV stats. Sadly, that's really one of the main reasons I was upgrading to Zimbra was to improve spam blocking and to keep track of those kinds of stats better.

Surely they can't only put the fix in 5.0? An upgrade is far too dangerous and time-consuming for me to do right after upgrading to 4.5.7 just recently!

[mikets]

show 5.0 Beta zmstat don't work on openSUSE10.2

[cvidal]

It looks like a path problem. If you run:

/opt/zimbra/libexec/zmstatuslog

as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

*/2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog

That's it! :-)

Carlos

[centrex]

It looks like a path problem. If you run:

/opt/zimbra/libexec/zmstatuslog

as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

*/2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog

That's it! :-)

Carlos

Excellent workaround Carlos, I implemented it now and so far, so good Service is showing as running now in admin console. Tomorrow I will know if the stats are logging correctly..

[centrex]

Carlos' fix works!

But now that stats are running again, a new issue has been revealed: The most important (to me) tab, "Anti-Spam/Anti-Virus Activity" is not being populated.

There must be another glitch in 4.5.7 somewhere.

Can anyone tell me which script gathers data for this tab ?

[cvidal]

Carlos' fix works!

But now that stats are running again, a new issue has been revealed: The most important (to me) tab, "Anti-Spam/Anti-Virus Activity" is not being populated.

There must be another glitch in 4.5.7 somewhere.

Can anyone tell me which script gathers data for this tab ?

May be you don't receive any spam at all!

Jokes appart, the script responsible for generating the graphs is called zmgengraphs and is also triggered by cron every 10 minutes. Here the script behavior is the same when you run it manually, so the previous fix doesn't work in this case :-(

Looking at the code, I see the graphs are generating by querying MySQL (the zimbra_logger database). Looking at the database I see that the counts are in zero and no stats are grabbed, so the bug is in the data grabbing process (swatch?).

Looking in bugzilla, there is already an open item (bug 20578).

Carlos

[centrex]

Looking in bugzilla, there is already an open item (bug 20578).

Carlos

20578 indeed looks like my thing. I voted for it. Good find

[randall]

It looks like a path problem. If you run:

/opt/zimbra/libexec/zmstatuslog

as user zimbra and then click "Refresh" on the Server Status screen, everything is OK (the zimbra.log also), but if the same command is triggered by cron it fails.

The solution (quick and dirty = Q&D) is to replace the zmsatuslog line in the crontab by:

*/2 * * * * . /opt/zimbra/.bashrc ; LANG=C /opt/zimbra/libexec/zmstatuslog

That's it! :-)

Carlos

Is this one specific to OS? I'm using Ubuntu 6.06, and I tried the same line, but it's not working.

Any idea?

Thanks in advance.

[fisch09]

Hi,

I also came across the issue with cron / .bashrc .
I wrote some scripts that worked fine when run as user zimbra from the command line but did not work from cron. Adding a "source ~/.bashrc" as first line into this scripts fixed this. OS is as well Ubuntu 6.06.

Kind Regards
Andre

[randall]

Hi,

I also came across the issue with cron / .bashrc .
I wrote some scripts that worked fine when run as user zimbra from the command line but did not work from cron. Adding a "source ~/.bashrc" as first line into this scripts fixed this. OS is as well Ubuntu 6.06.

Kind Regards
Andre

Thanks for the post Andre.

Should I add that script to the crontab or to the .bashrc?

Many thanks again.