Logger Issues After Upgrade

[xtreme-one]

I am running SLES 10 and upgraded from 4.5.0 to 4.5.3 and now I have some funny issues with logs. First the admin console says that the logger is not installed or running and it is on both accounts, and I thought it might be an issue with the syslog-ng that I had on initial install, but that looks good to me too. In my var/log/ folder I have these files zimbra.log zimbra.log.1.bz2, zimbra.log.2.bz2 where the zimbra.log is empty and looks like zimbra.log.2.bz2 is yesterdays data and zimbra.log.1.bz2 is todays? Any suggestions?

[dav01]

I've exactly the same problem with a new installation on openSuse 10.2

I've a zimbra.log.1.bz2 dated today at 19:15, but the new zimbra.log is empty and the admin console tell me that the logger is not installed or running.

Which process bzip che zimbra.log file? I checked che zimbra's crontab but I haven't found something interesting...

@D!

[xtreme-one]

The logger is related to the syslog daemon. The SuSE system runs syslog-ng. You need to make some changes to the system logger files and all works just fine. There is a sticky on the forums related to installation on SuSE 10.2 system, follow the instructions there and you should have no problem!

Let me know if you hit a hard spot. I'll be happy to help!

[dav01]

Thank you extreme.
I did the changes in /etc/syslog-ng/syslog-ng.conf and now everything seems to work.
The only "strange" thing is that the file /var/log/zimbra.log is owned by zimbra:root

zimbra@myserver:/var/log> ls -l zimbra* 
-rw-r----- 1 zimbra root   550548 Mar 27 08:44 zimbra.log
-rw-r----- 1 zimbra zimbra  44181 Mar 26 19:15 zimbra.log.1.bz2
-rw-r----- 1 zimbra root    54112 Mar 25 19:15 zimbra.log.2.bz2

is it "normal" ?

Thanks again
Marco

[xtreme-one]

I believe that is normal. I cannot say why the permissions are set that way, but for me it works. Keep an eye on your server, make sure it operates through a 24 hour cycle, Zimbra does somethings on the crontab that can cause logger issues. Once it runs for 24 I think you are good to go!

Good Luck.

[dav01]

Thanks again.

The only thing I don't understand now is "who" bzips zimbra log and "why" it's done at 19:15, and not at 00:00.

Marco

[AimanA]

This is a wierd one, but bear with me:

dav01 what timezone are you in?
xtreme-one, also the same question.

do you have the tzupdate patch installed on your servers? Is your bios clock set to UTC or local time?

I am trying to narrow down a question I am having in my own head about this issue, which I am also having (I posted about it in a separate thread, here: openSuSE 10.2 logger )

I have already made the changes to my syslog-ng files as others have suggested and I STILL have the problem, but it occurs at a different time than everyone elses. You are the first also that I have heard that it doesnt happen at 2:15am.

[dav01]

It happened, again.

Yesterday, exactly at 19:15, my /var/log/zimbra.log rotate and since that the new zimbra.log is empty and I get Logger service must be installed in admin console.

zimbra@myserver:~> ls -lrt /var/log/zimbra*
-rw-r----- 1 zimbra root    54112 Mar 25 19:15 /var/log/zimbra.log.4.bz2
-rw-r----- 1 zimbra zimbra  44181 Mar 26 19:15 /var/log/zimbra.log.3.bz2
-rw-r----- 1 zimbra root    43452 Mar 27 19:15 /var/log/zimbra.log.2.bz2
-rw-r--r-- 1 zimbra zimbra      0 Mar 28 19:15 /var/log/zimbra.log
-rw-r----- 1 zimbra root   136127 Mar 28 19:15 /var/log/zimbra.log.1.bz2

Answering your answer, my timezone is CEST and I haven't installed tzupdate (is it useful?)

I tryed also:

logmysql zimbra_logger
mysql> select * from service_status;
Empty set (0.00 sec)

@D!

[dav01]

Light at the end of the tunnel?

Following your post and bug 7904 I reached this post and I did this:

• Check the permissions for /var/log/zimbra.log. It's the owner zimbra and rw?
• Verify the changes in /etc/syslog-ng/syslog-ng.conf, or adding these lines at the end:
  

  filter f_local0       { facility(local0); }; # zimbra
  destination zmail { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
  log { source(src); filter(f_mail); destination(zmail); }; # zimbra
  destination local0 { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
  log { source(src); filter(f_local0); destination(local0); }; # zimbra
  filter f_auth       { facility(auth); }; # zimbra
  destination zmauth { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
  log { source(src); filter(f_auth); destination(zmauth); }; # zimbra

• Change the whole line with "killall -HUP syslogd" in these files to "/sbin/rcsyslog restart" :
  /opt/zimbra/bin/zmsyslogsetup
  /opt/zimbra/conf/zmlogrotate
  /etc/logrotate.d/zimbra
  
  
• As root, restart syslog-ng with: "/sbin/rcsyslog restart"
• As zimbra, restart the logger service "zmloggerctl status"

Now the /var/log/zimbra.log file is logging again and the admin console show the services' status.
I'm waiting for the rotation of the log, at 19:15

@D!

PS=Release 4.5.3_GA_733.SuSE10_20070228101815 openSUSE_10.2 FOSS edition

[dav01]

After some days (and some log rotation) I confirm that now my zimbra installation works.

Thanks all

@D!