Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
Package: rsyslog Followup-For: Bug #799346 Dear Maintainer, Reproduced while upgrade from jessie to stretch. Failed messages are: -- cut -- Setting up rsyslog (8.23.0-2) ... Job for rsyslog.service failed because the control process exited with error code. See "systemctl status rsyslog.service" and "journalctl -xe" for details. invoke-rc.d: initscript rsyslog, action "restart" failed. ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2017-01-20 03:02:16 EST; 49ms ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 30165 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 30165 (code=exited, status=1/FAILURE) Jan 20 03:02:16 obs-upgrade systemd[1]: rsyslog.service: Unit entered failed state. Jan 20 03:02:16 obs-upgrade systemd[1]: rsyslog.service: Failed with result 'exit-code'. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) --- cut --- Run rsyslogd directly found the problem: # rsyslogd rsyslogd: pidfile '/var/run/rsyslogd.pid' and pid 30330 already exist. If you want to run multiple instances of rsyslog, you need to specify different pid files for them (-i option). rsyslogd: run failed with error -3000 (see rsyslog.h or try http://www.rsyslog.com/e/3000 to learn what that number means) Workaround: kill -9 `cat /var/run/rsyslogd.pid` ; apt-get install -f Best regards, -Andrew
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
I’m experiencing the same issue here: root@kona:/home/eric# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up rsyslog (8.4.2-1+deb8u1) ... Job for rsyslog.service failed. See 'systemctl status rsyslog.service' and 'journalctl -xn' for details. invoke-rc.d: initscript rsyslog, action "restart" failed. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) root@kona:/home/eric# root@kona:/home/eric# systemctl status rsyslog.service syslog.socket ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled) Active: failed (Result: start-limit) since Mon 2015-10-05 11:33:29 CEST; 50s ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 11021 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 11021 (code=exited, status=1/FAILURE) Oct 05 11:33:29 kona systemd[1]: Failed to start System Logging Service. Oct 05 11:33:29 kona systemd[1]: Unit rsyslog.service entered failed state. Oct 05 11:33:29 kona systemd[1]: rsyslog.service start request repeated too...t. Oct 05 11:33:29 kona systemd[1]: Failed to start System Logging Service. Oct 05 11:33:29 kona systemd[1]: Unit rsyslog.service entered failed state. Oct 05 11:33:29 kona systemd[1]: rsyslog.service start request repeated too...t. Oct 05 11:33:29 kona systemd[1]: Failed to start System Logging Service. ● syslog.socket - Syslog Socket Loaded: loaded (/lib/systemd/system/syslog.socket; static) Active: failed (Result: service-failed-permanent) since Mon 2015-10-05 11:33:29 CEST; 50s ago Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/syslog Listen: /run/systemd/journal/syslog (Datagram) Oct 05 11:33:29 kona systemd[1]: Unit syslog.socket entered failed state. Hint: Some lines were ellipsized, use -l to show in full. root@kona:/home/eric# journalctl -alb -u rsyslog.service -- Logs begin at Tue 2015-09-29 13:24:13 CEST, end at Mon 2015-10-05 11:33:29 CE Sep 29 13:24:23 kona systemd[1]: rsyslog.service: main process exited, code=exit Sep 29 13:24:23 kona systemd[1]: Failed to start System Logging Service. Sep 29 13:24:23 kona systemd[1]: Unit rsyslog.service entered failed state. Sep 29 13:24:26 kona systemd[1]: rsyslog.service: main process exited, code=exit Sep 29 13:24:26 kona systemd[1]: Failed to start System Logging Service. Sep 29 13:24:26 kona systemd[1]: Unit rsyslog.service entered failed state. Sep 29 13:24:28 kona systemd[1]: rsyslog.service: main process exited, code=exit Sep 29 13:24:28 kona systemd[1]: Failed to start System Logging Service. Sep 29 13:24:28 kona systemd[1]: Unit rsyslog.service entered failed state. Sep 29 13:24:31 kona systemd[1]: rsyslog.service: main process exited, code=exit Sep 29 13:24:31 kona systemd[1]: Failed to start System Logging Service. Sep 29 13:24:31 kona systemd[1]: Unit rsyslog.service entered failed state. Sep 29 13:24:32 kona systemd[1]: rsyslog.service: main process exited, code=exit Sep 29 13:24:32 kona systemd[1]: Failed to start System Logging Service. Sep 29 13:24:32 kona systemd[1]: Unit rsyslog.service entered failed state. … If you want me te perform additional checks, feel free to ask.
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
Am 22.09.2015 um 15:34 schrieb Rory Campbell-Lange: > On 18/09/15, Michael Biebl (bi...@debian.org) wrote: >> Since rsyslog is running now correctly, do you at least have something >> in the log files which might indicate why rsyslog failed to start? > > Hi Michael > > Sorry for the delay in my reply -- I'm travelling. > > The problem seems to have started here: > > 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 > > Is that at all helpful? Not really. There aren't any log messages which would indicate a problem in rsyslog. Nothing in the journal either? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
On 18/09/15, Michael Biebl (bi...@debian.org) wrote: > Since rsyslog is running now correctly, do you at least have something > in the log files which might indicate why rsyslog failed to start? Hi Michael Sorry for the delay in my reply -- I'm travelling. The problem seems to have started here: 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 Is that at all helpful? Regards Rory
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
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 systemd[1]: Stopped System Logging Service. >Sep 18 06:21:21 systemd[1]: Starting System Logging > Service... >Sep 18 06:21:21 systemd[1]: rsyslog.service start request > repeated too quickly, refusing to start. >Sep 18 06:21:21 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 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
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 systemd[1]: Stopped System Logging Service. Sep 18 06:21:21 systemd[1]: Starting System Logging Service... Sep 18 06:21:21 systemd[1]: rsyslog.service start request repeated too quickly, refusing to start. Sep 18 06:21:21 systemd[1]: Failed to start System Logging Service. * What exactly did you do (or not do) that was effective (or ineffective)? while apt-get bails out I've verified that rsyslog appears to have restarted anyway * What was the outcome of this action? apt-get fails * What outcome did you expect instead? apt-get succeeds *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.19.1-x86_64-linode53 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsyslog depends on: ii init-system-helpers 1.22 ii initscripts 2.88dsf-59 ii libc62.19-18+deb8u1 ii libestr0 0.1.9-1.1 ii libjson-c2 0.11-4 ii liblogging-stdlog0 1.0.4-1 ii liblognorm1 1.0.1-3 ii libuuid1 2.25.2-6 ii lsb-base 4.1+Debian13+nmu1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages rsyslog recommends: ii logrotate 3.8.7-1+b1 Versions of packages rsyslog suggests: pn rsyslog-doc pn rsyslog-gnutls pn rsyslog-gssapi pn rsyslog-mongodb pn rsyslog-mysql | rsyslog-pgsql pn rsyslog-relp -- no debconf information
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
On 18/09/15, Michael Biebl (bi...@debian.org) 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 systemd[1]: Stopped System Logging Service. > > Sep 18 06:21:21 systemd[1]: Starting System Logging > > Service... > > Sep 18 06:21:21 systemd[1]: rsyslog.service start request > > repeated too quickly, refusing to start. > > Sep 18 06:21:21 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/ 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
Bug#799346: rsyslog upgrade fails with message "start request repeated too quickly, refusing to start."
Since rsyslog is running now correctly, do you at least have something in the log files which might indicate why rsyslog failed to start? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
