Setting up syslog fails during upgrade

[simonfishley]

Hi All

Has anyone else experienced this problem? While upgrading from 7.1.0 to 7.1.1 on my FOSS install on Debian5 the process runs smoothly until:

Checking for default IM conference room...already initialized.
Setting up syslog.conf...

And there it sits. I have an identical server on a different site which I am upgrading simultaneously and it happily starts syslog. After 10 mins I did the following:

# ps aux |grep syslog

Which showed:

mail:/var/log# ps -aux |grep log

root 24643 0.0 0.0 10124 1248 pts/3 S+ 14:11 0:00 sh -c /opt/zimbra/libexec/zmsyslogsetup >> /tmp/zmsetup.08142011-140559.log 2>&1
root 24644 0.0 0.0 39912 5900 pts/3 S+ 14:11 0:00 /usr/bin/perl /opt/zimbra/libexec/zmsyslogsetup
root 24888 0.0 0.0 10124 1252 pts/3 S+ 14:11 0:00 sh -c /etc/init.d/rsyslog restart> /dev/null 2>&1
root 24889 0.0 0.0 10264 1432 pts/3 S+ 14:11 0:00 /bin/sh /etc/init.d/rsyslog restart
root 24892 0.0 0.0 10268 1460 pts/3 S+ 14:11 0:00 /bin/sh /etc/init.d/rsyslog start
root 24893 0.0 0.0 142020 1628 pts/3 Sl+ 14:11 0:00 /usr/sbin/rsyslogd -c3 -d

I then did:

# kill 24643

The install then tells me it Failed (just the syslog part) and continues and finishes the upgrade.

I have observed this on my last 2 upgrades so I would like to try and identify the cause and solve it.

Thanks
Simon

[phoenix]

I haven't seen that and the only bug report that I found was this: Bug 41750 – Debian 5-64 incorrect syslog-ng configuration

[simonfishley]

Hi Bill

Thanks for the link. That seems to suggest a conflict with having both rsyslog and syslog-ng installed. This does not seem to be the case:

mail:~/zimbra# dpkg -l |grep syslog
ii libsys-syslog-perl 0.26-1 Perl interface to the UNIX syslog(3) calls
ii rsyslog 3.18.6-4 enhanced multi-threaded syslogd

Can you think of any complications we may have because I had to kill the syslog restart process during the install?

Thanks
Simon

[simonfishley]

More information. I have been out of the office since the upgrade. Have just returned to discover that the server is not logging anything at all. mail.log, messages, syslog are all 0 in size.

zmcontrol status says everything is running 100%