Logger says "running" on start but stopped in web admin

[techmeisterv]

I'm running Zimbra on a Mac OS X machine, and I'm getting the same problem. When I try to follow these steps, I get lost because there is no "/etc/syslog-ng" directory. Does anybody know how to fix this problem on a Mac?

Originally Posted by Achim.Theobald

Hello,

Make following steps.

-- work es root --
su zimbra
zmcontrol stop

-- work es root --
killall tail
look for all mounted /dev/shm (multiple mounts possible), umount them

Check the permissions for /var/log/zimbra.log. It's the owner zimbra and rw? Change them if necessary
Check also the size. It's zero byte? --> Bug 1

Have you make any changes in your /etc/syslog-ng/syslog-ng.conf? Yes?
Copy the zimbra changes from "/etc/syslog-ng/syslog-ng.conf.in" to "/etc/syslog-ng/syslog-ng.conf" (the last 5 lines with "#zimbra" comment at end)

Bug 1: Change the line with "killall -HUP syslogd" in this files to "/sbin/rcsyslog restart"

/opt/zimbra/bin/zmsyslogsetup
/opt/zimbra/bin/zmlogrotate
/etc/logrotate.d/zimbra

Restart syslog-ng with: "/sbin/rcsyslog restart"
mount -a
su zimbra
start zimbra (zmcontrol start)


And with some luck, it will work....

Cu

[SmokinX]

several issues/questions here after upgrade from 3 to 4 on MacOS X 10.4.8:

status in webadmin yesterday stated logger, spam and av are not running.
today it states only logger, spam and av is running (!)

- verified av by sending a virus and it is running
- spam is yet to be received (!) i'm sure it does...
- logger seems to work for my logfile is now 520MB big, mostly with statusreports which are saying all is running (does anyone now what to edit to get it recycled every month?)

Clicking on Serverstatistics shows nice graphs for message counts and sizes but my virus-mail does not show up in the graph.
Clicking on the server itself shows only Data not yet available except for the Mailbox quota which is nicely populated.

any ideas anyone?

[jonas33432]

Originally Posted by Achim.Theobald

Hello,

Make following steps.

-- work es root --
su zimbra
zmcontrol stop

-- work es root --
killall tail
look for all mounted /dev/shm (multiple mounts possible), umount them

Check the permissions for /var/log/zimbra.log. It's the owner zimbra and rw? Change them if necessary
Check also the size. It's zero byte? --> Bug 1

Have you make any changes in your /etc/syslog-ng/syslog-ng.conf? Yes?
Copy the zimbra changes from "/etc/syslog-ng/syslog-ng.conf.in" to "/etc/syslog-ng/syslog-ng.conf" (the last 5 lines with "#zimbra" comment at end)

Bug 1: Change the line with "killall -HUP syslogd" in this files to "/sbin/rcsyslog restart"

/opt/zimbra/bin/zmsyslogsetup
/opt/zimbra/bin/zmlogrotate
/etc/logrotate.d/zimbra

Restart syslog-ng with: "/sbin/rcsyslog restart"
mount -a
su zimbra
start zimbra (zmcontrol start)


And with some luck, it will work....

Cu

Finally i got it.
Zimbra 4.0.4 on SuSE 10.1 works.
Guys - you rock!

[kschwab]

same problem here
logger reports its running on startup but mesasge in admin app says it is not installed. Had this problem in every install i've tried on X - ZM 3.x on OS-X 10.4 client and server, ZM 4.0 OSS on 10.4 client and server, 4.0 4 network dem on on both client and server, all clean installs, after 6 tries we got zimbra to work mostly correctly (currently testing 4.0.4 demo network on 10.4 8 client) but I've never seen logs in the admin app.

[brian]

There were a lot of fixes for graphing and the logger process in general put into the 4.5.0 beta and rc1 releases. If you are running 4.0.x Network on a Mac most of the fixes are detailed in this post http://www.zimbra.com/forums/installation/4579-logger-service-issues-post32474.html

We will also be updating the openSUSE builds to support 10.1/10.2 in an upcoming release.

[Achim.Theobald]

Originally Posted by brian

There were a lot of fixes for graphing and the logger process in general put into the 4.5.0 beta and rc1 releases. If you are running 4.0.x Network on a Mac most of the fixes are detailed in this post http://www.zimbra.com/forums/showthread.php?p=32474

We will also be updating the openSUSE builds to support 10.1/10.2 in an upcoming release.

I hope a x86_64 Build come also....


Cu

Achim

[noerenberg]

Originally Posted by Achim.Theobald

Hello,

Make following steps.

-- work es root --
su zimbra
zmcontrol stop

-- work es root --
killall tail
look for all mounted /dev/shm (multiple mounts possible), umount them

Check the permissions for /var/log/zimbra.log. It's the owner zimbra and rw? Change them if necessary
Check also the size. It's zero byte? --> Bug 1

Have you make any changes in your /etc/syslog-ng/syslog-ng.conf? Yes?
Copy the zimbra changes from "/etc/syslog-ng/syslog-ng.conf.in" to "/etc/syslog-ng/syslog-ng.conf" (the last 5 lines with "#zimbra" comment at end)

Bug 1: Change the line with "killall -HUP syslogd" in this files to "/sbin/rcsyslog restart"

/opt/zimbra/bin/zmsyslogsetup
/opt/zimbra/bin/zmlogrotate
/etc/logrotate.d/zimbra

Restart syslog-ng with: "/sbin/rcsyslog restart"
mount -a
su zimbra
start zimbra (zmcontrol start)


And with some luck, it will work....

Cu

... and it does work
this was very helpful! Thanks!
but did you really have a logrotate in /opt/zimbra/bin?
I think it should be /opt/zimbra/conf/zmlogrotate

This changes ("killall -HUP syslogd" in this files to "/sbin/rcsyslog restart") have to be done after each upgrade of zimbra server.

[noerenberg]

... and it does work
this was very helpful! Thanks!
but did you really have a logrotate in /opt/zimbra/bin?
I think it should be /opt/zimbra/conf/zmlogrotate

This changes ("killall -HUP syslogd" in this files to "/sbin/rcsyslog restart") have to be done after each upgrade of zimbra server.

[brian]

At least until you upgrade to 5.0.6 where the syslog-ng logrotate bug is fixed.