statistics not updating

[simonb256]

Hi all,

I have zimbra 5.0.8 (updated from 5.0.6) and came accross a small issue.

For some reason none of the stats show except the mail/spam stats.

Would anyone know as to why this would be the case?

I am running on a Ubuntu server (version 8.04) and other than this error have had no issues.

[bdial]

first thing to do would be to see if the stats are actually being logged like the disk free stats. look in your zimbra.log and see if you see entries like this

Jul 16 10:30:02 hostname zimbramon[11038]: 11038:info: 2008-07-16 10:30:01, DISK: hostname.domain.com: dev: /dev/cciss/c0d0p3, mp: /opt/zimbra, tot: 46690, avail: 42947

[simonb256]

running:

cat zimbra.log |grep DISK

returns nothing, so I guess not.

[bdial]

can you confirm that zimbra is actually logging to zimbra.log? tail it and see if theres entries being made into it. If so, then perhaps the cron job isn't running. in zimbra's cron file you should find.

*/10 * * * * /opt/zimbra/libexec/zmdisklog

That is the process that reports the disk space to the logs. make sure thats in there and verify that cron is running too.

[simonb256]

A tail of the zimbra.log file returns:

Jul 16 15:56:34 boredom sshd[12832]: input_userauth_request: invalid user adelynn
Jul 16 15:56:34 boredom slapd[7380]: conn=1047 fd=26 closed (connection lost)
Jul 16 15:56:36 boredom sshd[12831]: Failed password for invalid user adelynn from 91.121.30.89 port 45996 ssh2
Jul 16 15:56:36 boredom sshd[12833]: warning: /etc/hosts.deny, line 20: missing ":" separator
Jul 16 15:56:36 boredom sshd[12833]: Invalid user adept from 91.121.30.89
Jul 16 15:56:36 boredom sshd[12834]: input_userauth_request: invalid user adept
Jul 16 15:56:38 boredom sshd[12833]: Failed password for invalid user adept from 91.121.30.89 port 46263 ssh2
Jul 16 15:56:38 boredom sshd[12835]: warning: /etc/hosts.deny, line 20: missing ":" separator
Jul 16 15:56:39 boredom sshd[12835]: Invalid user aderbery from 91.121.30.89
Jul 16 15:56:39 boredom sshd[12836]: input_userauth_request: invalid user aderbery

Cron is running:

root      5852  0.0  0.0   2104   884 ?        Ss   Jul05   0:02 /usr/sbin/cron

and I may be stupid here but where would the cron file be hiding?

EDIT: I checked the /etc/con.daily weekly and monthly and there is no meantion of anything zimbra related that I can see, same with the crontad and the /etc/cron.d/ directory

[bdial]

it usually depends on hte system you're on. In SuSE it's /var/spool/cron/tabs/zimbra

It sounds to me like maybe your syslog is a bit messed up. I don't know why you're seeing sshd logs in your zimbra.log. zimbra.log should only have stuff from zimbra processes, and you should see at least a few entries per minute since by default it is pretty chatty. What version of linux are you using?

[simonb256]

Originally Posted by simonb256

I am running on a Ubuntu server (version 8.04) and other than this error have had no issues.

I too was confused as to why I was seeing sshd entries in there...

I found the cron file, it was pretty much the same path:

/var/spool/cron/crontabs/zimbra

and the entry is question was there:

root@boredom:/var/spool/cron/crontabs# cat zimbra | grep disk
*/10 * * * * /opt/zimbra/libexec/zmdisklog

[bdial]

i'm not that familiar with ubuntu but maybe you can try running

/opt/zimbra/bin/zmsyslogsetup

again and see if that fixes it. make sure to restart the syslog too when thats done. If that doesn't fix your problem you maybe post your /etc/syslog.conf here and see if anyone sees suspicious stuff.

[simonb256]

I ran zmsyslogsetup again and left it overnight to no avail. unfortunatly.
I'm guessing it is possible that its due to me running a non-supported OS? (ie Ubuntu 8.04 rather than 6.04).

MY etc/syslog.conf is as follows anyway:

simons@boredom:~$ cat /etc/syslog.conf
#  /etc/syslog.conf     Configuration file for syslogd.
#
#                       For more information see syslog.conf(5)
#                       manpage.

#
# First some standard logfiles.  Log by facility.
#

auth,authpriv.*                 /var/log/auth.log
*.*;auth,authpriv.none          -/var/log/syslog
#cron.*                         /var/log/cron.log
daemon.*                        -/var/log/daemon.log
kern.*                          -/var/log/kern.log
lpr.*                           -/var/log/lpr.log
mail.*                          -/var/log/mail.log
user.*                          -/var/log/user.log

#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info                       -/var/log/mail.info
mail.warn                       -/var/log/mail.warn
mail.err                        /var/log/mail.err

# Logging for INN news system
#
news.crit                       /var/log/news/news.crit
news.err                        /var/log/news/news.err
news.notice                     -/var/log/news/news.notice

#
# Some `catch-all' logfiles.
#
*.=debug;\
        auth,authpriv.none;\
        news.none;mail.none     -/var/log/debug
*.=info;*.=notice;*.=warn;\
        auth,authpriv.none;\
        cron,daemon.none;\
        mail,news.none          -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg                         *

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
#       news.=crit;news.=err;news.=notice;\
#       *.=debug;*.=info;\
#       *.=notice;*.=warn       /dev/tty8

# The named pipe /dev/xconsole is for the `xconsole' utility.  To use it,
# you must invoke `xconsole' with the `-file' option:
#
#    $ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
#      busy site..
#
daemon.*;mail.*;\
        news.err;\
        *.=debug;*.=info;\
        *.=notice;*.=warn       |/dev/xconsole

local0.*                -/var/log/zimbra.log
auth.*                  -/var/log/zimbra.log
mail.*                -/var/log/zimbra.log
simons@boredom:~$

[bdial]

I think thats right (I'm on suse it looks a bit different with syslog-ng) have you confirmed that zimbra logger is running?

su - zimbra
zmcontrol status

look for logger