[SOLVED] service STAT problem

[warcries]

hi guys,

service STAT had stopped. Already, restarted the zmcontrol but it can't RUN.

Any advised will be appreciated.

Thank you.

[uxbod]

su - zimbra
zmcontrol status
zmstatctl status
zmcontrol -v
ls -l /opt/zimbra/zmstat

[Spencer]

I am having the same issues..

Host ######
antispam Running
antivirus Running
convertd Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Stopped

process 20224 in /opt/zimbra/zmstat/pid/zmstat-io.pid not running
process 20867 in /opt/zimbra/zmstat/pid/zmstat-vm.pid not running
process 6568 in /opt/zimbra/zmstat/pid/zmstat-cpu.pid not running
process 20983 in /opt/zimbra/zmstat/pid/zmstat-convertd.pid not running
process 20875 in /opt/zimbra/zmstat/pid/zmstat-fd.pid not running
process 20220 in /opt/zimbra/zmstat/pid/zmstat-io-x.pid not running
process 21013 in /opt/zimbra/zmstat/pid/zmstat-mtaqueue.pid not running
Running: zmstat-allprocs
Running: zmstat-df
Running: zmstat-mysql

Release 6.0.5_GA_2213.UBUNTU6_64 UBUNTU6_64 NETWORK edition.

ls -l /opt/zimbra/zmstat

lists a bunch of files.

I can restart the service, but then it stops after a week or so.

[uxbod]

The reason why I asked for a list of those files, instead of "a bunch of files", is to check the permissions Try the following

su - zimbra
zmstatctl stop
exit
chown -R zimbra:zimbra /opt/zimbra/zmstat
su - zimbra
zmstatctl start
zmstatctl status

[Spencer]

The files in zmstat all had zimbra:zimbra ownership. I did that anyways and restarted the service and its running.

I will keeep and eye on it, but generally the stats service fails after a week or so of running. Unfortunatly I don't know what to look for in the logs to find any errors.

[Mark Daniel]

I'm having the same affliction, but it appears that zmstats is running, and the zmstats folder is stuffed full of active, non-zero-byte files all owned by zimbra. However, when I sign into the Admin console, I'm getting red X's for each service (server is running perfectly otherwise, besides getting zero'ed out mail reports).

[Mark Daniel]

Ah, just realized: /opt/log/mail.log and /opt/log/zimbra.log are zero-byte in length.

-rw-r-----    1 root    admin           0 Jul  3 03:17 mail.log
-rw-r--r--    1 zimbra  zimbra          0 May 26 03:15 zimbra-stats.log
-rw-r--r--    1 zimbra  zimbra          0 Jul  8 03:16 zimbra.log

What would prevent Zimbra from being able to write to those files? (I know mail.log *used* to be written to, but not sure if that should still be the case).