On 18/09/15, Michael Biebl ([email protected]) wrote:
> Control: tags -1 + moreinfo
>
> Am 18.09.2015 um 08:31 schrieb Rory Campbell-Lange:
> > Package: rsyslog
> > Version: 8.4.2-1+deb8u1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where appropriate
> > ***
> >
> > * What led up to the situation?
> > apt-get update
> > Sep 18 06:21:19 <hostname> systemd[1]: Stopped System Logging Service.
> > Sep 18 06:21:21 <hostname> systemd[1]: Starting System Logging
> > Service...
> > Sep 18 06:21:21 <hostname> systemd[1]: rsyslog.service start request
> > repeated too quickly, refusing to start.
> > Sep 18 06:21:21 <hostname> systemd[1]: Failed to start System Logging
> > Service.
>
> Can you please send me the output of the following command (run them as
> root):
> systemctl status rsyslog.service syslog.socket
> journalctl -alb -u rsyslog.service
Hi Michael
Looks like I might have had a messed up rsyslog or clamav-daemon before the
upgrade. Sorry if this is a waste of your time.
Unfortunately since I filed the report I noticed the rsyslog and clamav daemons
were still running after running /etc/init.d/<daemon> stop. I force killed them
and then I was able to install rsyslog. The clamav-daemon was similarly
affected.
Consequently systemctl status rsyslog.service syslog.socket shows:
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Fri 2015-09-18 08:07:59 UTC; 2h 20min ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 26632 (rsyslogd)
CGroup: /system.slice/rsyslog.service
└─26632 /usr/sbin/rsyslogd -n
Sep 18 08:07:59 clwnew systemd[1]: Starting System Logging Service...
Sep 18 08:07:59 clwnew systemd[1]: Started System Logging Service.
● syslog.socket - Syslog Socket
Loaded: loaded (/lib/systemd/system/syslog.socket; static)
Active: active (running) since Fri 2015-09-18 08:07:59 UTC; 2h 20min ago
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/syslog
Listen: /run/systemd/journal/syslog (Datagram)
journalctl -alb -u rsyslog.service shows this:
root@clwnew:/var/log# journalctl -alb -u rsyslog.service
-- Logs begin at Fri 2015-09-18 06:19:11 UTC, end at Fri 2015-09-18 10:27:23
UTC. --
Sep 18 06:19:14 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:14 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 06:19:14 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:14 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:14 clwnew systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
Sep 18 06:19:14 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:14 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:15 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 06:19:15 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:15 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:15 clwnew systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
Sep 18 06:19:15 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:15 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:15 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 06:19:15 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:15 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:15 clwnew systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
Sep 18 06:19:15 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:15 clwnew systemd[1]: Starting System Logging Service...
...
Sep 18 06:19:18 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:18 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:18 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 06:19:18 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:18 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:19 clwnew systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
Sep 18 06:19:19 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:19 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:19 clwnew systemd[1]: rsyslog.service start request repeated too
quickly, refusing to start.
Sep 18 06:19:19 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:19 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:19 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:19 clwnew systemd[1]: rsyslog.service start request repeated too
quickly, refusing to start.
Sep 18 06:19:19 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:39 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:39 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 06:19:39 clwnew systemd[1]: Failed to start System Logging Service.
Sep 18 06:19:39 clwnew systemd[1]: Unit rsyslog.service entered failed state.
Sep 18 06:19:39 clwnew systemd[1]: rsyslog.service holdoff time over,
scheduling restart.
Sep 18 06:19:39 clwnew systemd[1]: Stopping System Logging Service...
Sep 18 06:19:39 clwnew systemd[1]: Starting System Logging Service...
Sep 18 06:19:39 clwnew systemd[1]: rsyslog.service: main process exited,
code=exited, status=1/FAILURE
/var/log/syslog (in BST time) shows:
Sep 18 08:07:45 clwnew rsyslogd: [origin software="rsyslogd" swVersion="8.4.2"
x-pid="32415" x-info="http://www.rsyslog.com";] exiting on signal 15.
Sep 18 08:07:59 clwnew rsyslogd: [origin software="rsyslogd" swVersion="8.4.2"
x-pid="26632" x-info="http://www.rsyslog.com";] start
Sep 18 08:07:59 clwnew systemd[1]: Starting Syslog Socket.
Sep 18 08:07:59 clwnew systemd[1]: Listening on Syslog Socket.
Sep 18 08:07:59 clwnew systemd[1]: Starting System Logging Service...
Sep 18 08:07:59 clwnew systemd[1]: Started System Logging Service.
Sep 18 08:08:19 clwnew systemd[1]: Starting Socket for Clam AntiVirus userspace
daemon.
Sep 18 08:08:19 clwnew systemd[1]: Listening on Socket for Clam AntiVirus
userspace daemon.
Sep 18 08:08:19 clwnew systemd[1]: Starting Clam AntiVirus userspace daemon...
Sep 18 08:08:19 clwnew systemd[1]: Started Clam AntiVirus userspace daemon.
Sep 18 08:08:19 clwnew clamd[26733]: ERROR: Can't initialize the internal logger
Sep 18 08:08:19 clwnew clamd[26733]: ERROR: /var/log/clamav/clamav.log is
locked by another process
Sep 18 08:08:19 clwnew systemd[1]: clamav-daemon.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 08:08:19 clwnew systemd[1]: Unit clamav-daemon.service entered failed
state.
Sep 18 08:08:35 clwnew systemd[1]: Stopping LSB: exim Mail Transport Agent...
Sep 18 08:08:35 clwnew exim4[26744]: Stopping MTA: exim4_listener.
Sep 18 08:08:35 clwnew exim4[26744]: ALERT: exim paniclog
/var/log/exim4/paniclog has non-zero size, mail system possibly broken
Sep 18 08:08:35 clwnew systemd[1]: Starting LSB: exim Mail Transport Agent...
Sep 18 08:08:35 clwnew exim4[26754]: Starting MTA: exim4.
Sep 18 08:08:35 clwnew exim4[26754]: ALERT: exim paniclog
/var/log/exim4/paniclog has non-zero size, mail system possibly broken
Sep 18 08:08:35 clwnew systemd[1]: Started LSB: exim Mail Transport Agent.
Sep 18 08:08:57 clwnew systemd[1]: Starting Clam AntiVirus userspace daemon...
Sep 18 08:08:57 clwnew systemd[1]: Started Clam AntiVirus userspace daemon.
Sep 18 08:08:57 clwnew clamd[27095]: ERROR: Can't initialize the internal logger
Sep 18 08:08:57 clwnew clamd[27095]: ERROR: /var/log/clamav/clamav.log is
locked by another process
Sep 18 08:08:57 clwnew systemd[1]: clamav-daemon.service: main process exited,
code=exited, status=1/FAILURE
Sep 18 08:08:57 clwnew systemd[1]: Unit clamav-daemon.service entered failed
state.
...
