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

[brian]

These are unrelated items. There are 2 distinct services here, logger (admin ui stats) and stats. The stats service collects background stats like iostats/vmstats/mysql stats but these are not currently displayed in the admin ui.

The logger service is responsible for updating the logger database from which the admin ui graphs are generated.

[fisch09]

Thank you for this information. BUT how do I get the stats back?

having the same issue after upgrade 4.5.6 NE to 4.5.7 NE on Ubuntu 6.06.1

Cheers
Andre

[centrex]

Originally Posted by fisch09

Thank you for this information. BUT how do I get the stats back?

having the same issue after upgrade 4.5.6 NE to 4.5.7 NE on Ubuntu 6.06.1

Cheers
Andre

According to the bug tracker it has been fixed with 5.0.0, so presumably us 4.5.7'ers will have to wait a few months and upgrade to 5.0.0 to get rid of this.

[VJM]

I am having this issue. I just upgraded to 4.5.7 on Centos 5. I have not had any stats gathered since the upgrade. zimbra.log shows that the service is not running. I found some errors in the /opt/zimbra/zmstat/zmstat.out. not sure what they mean.

No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
Warning: Not possible to monitor process stats

[jholder]

Originally Posted by VJM

I am having this issue. I just upgraded to 4.5.7 on Centos 5. I have not had any stats gathered since the upgrade. zimbra.log shows that the service is not running. I found some errors in the /opt/zimbra/zmstat/zmstat.out. not sure what they mean.

No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
Warning: Not possible to monitor process stats

It's a bug. See Bug 17977 - Server Status in admin console shows incorrect info.
Somehow the fix didn't make it into 4.5.7

CC yourself on the bug to keep updated.

[glitch23]

I believe the confusion lies in the terminology.

The "stats" service only collects information about the processes running in background and on the server itself. See attached image. Thats the result of the zmstat-chart as it creates a index.html file and images for all the graphs.

The "Server Statistics" problem has to do with 1) rrdtool-1.0.49 and 2) letting the server stay up long enough to gather stats and 3) /opt/zimbra/libexec/zmgengraphs

If you manually run "/opt/zimbra/libexec/zmstatuslog" before the next cronjob run, the "stats" service will appear correctly. But when cron runs it for whatever reason the status gets returned as "0" which gives us the annoying "X" and the incorrect entry in the /var/log/zimbra.log file.

Is any there anyway to fix this? The files relating to the stats service are easily readable but I just don't know where to start since manually running it works but cron does not.

I need the a majority of the bug fixes in 4.5.7 especially bug 18312 and 18606 which was a showstopper for 4.5.6, and I'm not about to upgrade the whole system twice as the move to NE is already being a pain to schedule.

[centrex]

Originally Posted by VJM

I am having this issue. I just upgraded to 4.5.7 on Centos 5. I have not had any stats gathered since the upgrade. zimbra.log shows that the service is not running. I found some errors in the /opt/zimbra/zmstat/zmstat.out. not sure what they mean.

No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
Warning: Not possible to monitor process stats

You could try yum install sysstat which will install the sysstat package. It includes iostat. That might get rid of the message you posted.

Won't fix the stats service not showing bug though.

[glitch23]

No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
No iostat installed on this host at /opt/zimbra/libexec/zmstat-io line 37.
Warning: Not possible to monitor process stats

After a bit more digging to get rid of the first two lines in /opt/zimbra/zmstat/zmstat.out you have to install iostat or systat which is not a default depending on your distribution.

On Ubuntu 6.06:

sudo apt-get install sysstat

Will get you what you need, just make sure "Universe" is enabled.

Now for the third line...

Bug 17977 references these two file as being the problem and fixed:

Affected files ...

... //depot/main/ZimbraBuild/lib/Zimbra/Mon/Zmstat.pm#5 edit
... //depot/main/ZimbraServer/src/bin/zmstatctl#3 edit

Though I'm not exactly sure why but if you stop "/opt/zimbra/libexec/zmstat/zmstat-proc" (by killing its pid) and then run it again you will get that warning about that stats service. It turns out that the array containing the list of running procs is correct but the function:

my $ps_sub = $ps_subs{$proc};

Does not return a valid value

CODE(0x82100f0)
mailbox
CODE(0x8210324)
mysql
CODE(0x8210408)
convertd
CODE(0x82104c8)
ldap
CODE(0x8210588)
postfix
CODE(0x8210618)
amavis
CODE(0x82bcfac)
clam
Use of uninitialized value in print at ./zmstat-proc line 553.
 at ./zmstat-proc line 553

stats
Warning: Not possible to monitor process stats

So there might be more to this bug than it not showing up when zmstatuslog runs.

[hogne]

Originally Posted by glitch23

I believe the confusion lies in the terminology.

The "stats" service only collects information about the processes running in background and on the server itself. See attached image. Thats the result of the zmstat-chart as it creates a index.html file and images for all the graphs.

The "Server Statistics" problem has to do with 1) rrdtool-1.0.49 and 2) letting the server stay up long enough to gather stats and 3) /opt/zimbra/libexec/zmgengraphs

I left a 4.5.7 server on for 5 days. I never got any server statistics to show at all. With 4.5.6, in that amount of time, it did eventually show up.

Originally Posted by centrex

According to the bug tracker it has been fixed with 5.0.0, so presumably us 4.5.7'ers will have to wait a few months and upgrade to 5.0.0 to get rid of this.

I would really like to see this fix go into 4.5.x as 5.x imo need to reach final and mature quite a bit before it's production ready. I couldn't even get the latest beta to work at all when I tested it, the admin web login shows an empty page and the user login miss the logo and was misaligned.

I really would like to migrate to Zimbra at work, but there just seem to be to many glitches in the scripts to make me feel comfortable with it. Also the presence of Bug 19915 - code assumptions about postfix_qid: max length of 12, on some systems they are longer forces me to modify both some code and a table in the DB which is rather unfortunate as it could cause all sorts of upgrade problems later on.

[bradb21]

Same problem here. I was running 4.5.6 on Suse 10, and then upgraded to 4.5.7