Logger stops by itself after 5.0.15 upgrade

[nufan]

Just upgraded to latest version over the weekend, now I see the "logger" service stopping by itself in the web admin console. A "zmcontrol status" also shows the logger service stopped. I can start it again by typing zmloggerctl start in the console. I have not experienced this occuring up until this recent upgrade.

Is there anything I can do to keep the logger from stopping by itself? Thanks for any input

[uxbod]

Anything reported in your logfiles at all ? Need a little bit more information please

[nufan]

thanks for the reply ! Would you be so kind as to point me in the right direction as to what log files you would like to see? Also the easiest way for me to read them? I find when i just cat them in terminal it can only show so much.

Thanks !

[uxbod]

/var/log/zimbra.log you can also check /opt/zimbra/log/mysql_error.log aswell.

[nufan]

thanks for that, the mysql_error.log didn't have much in it, just a few entries from when I updated over the weekend. The last time I noticed the logger was down was first thing this morning so its possible it happened over night, unfortunately in terminal I can only go back about half an hour since there is so many entries, so I'm thinking I will need to search those logs (zimbra.log) pretty close to the next time it goes down, will paste results when it occurs.

[shibu]

Please check Logger - Zimbra :: Wiki

it has docs on how to determine why logger isn't working

[Bill Brock]

yesterday I received Admin e-mails telling me my logger had stopped. Looking at the status, both GUI and CLI showed it to be working. Not sure why it would stop or better yet why it would start back on its own. Since it was running when I checked I didn't go to the logs for further details. If it happens again I guess I will do some more digging.

[nufan]

Thanks for the replies, I am still trying to work this out. Again this morning I came in and the logger is not working. I checked my admin account and noticed the following:

Since the upgrade to 5.15 on March 14th, the logger has gone down on the following dates and times with the following messages:

Mar 15 03:16:07 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
Mar 16 17:01:49 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
Mar 17 03:15:54 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
Mar 17 03:39:21 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
Mar 17 03:40:35 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
Mar 17 03:15:54 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
Mar 17 03:39:21 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n
Mar 17 03:40:35 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from running to stopped\n
Mar 17 13:15:10 xsrv1 zimbramon[12701]: 12701:err: Service status change: xsrv1.intranet.brandonsun.com logger changed from stopped to running\n

I have followed that link for logger problems without much luck. When I am doing zmcontrol status I am getting that the logger is stopped and zmlogswatchctl is not running.

As per the links directions it says:

2. If "zmlogswatchctl is not running", verify whether A) the file /opt/zimbra/log/logswatch.pid exists, and B) there is a single /opt/zimbra/libexec/logswatch process.

cat /opt/zimbra/log/logswatch.pid
ps aux | grep logswatch

I ran both those commands and got the following output:

xsrv1:/Users/systemsadministrator zimbra$ cat /opt/zimbra/log/logswatch.pid
26388
xsrv1:/Users/systemsadministrator zimbra$ ps aux | grep logswatch
zimbra   28055   0.0 -0.0    18060    196  p1  R+    8:47AM   0:00.00 grep logswatch

Unfortunately the article doesn't say what to do after those commands.

Appreciate any further comments, thanks !

[phoenix]

That would indicate that it's not running as you should get an output like your entry above plus the running one like this:

zimbra   12282  0.0  0.3   6736  4880 ?        S    04:03   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --script-dir=/tmp -t /var/log/zimbra.log

[nufan]

Originally Posted by phoenix

That would indicate that it's not running as you should get an output like your entry above plus the running one like this:

zimbra   12282  0.0  0.3   6736  4880 ?        S    04:03   0:00 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --script-dir=/tmp -t /var/log/zimbra.log

ok fair enough, and I can start the logger fine, so I'm still curious why its stopping by itself though, any suggestions ? :|