rsyslog.service: Start request repeated too quickly.

KPryor · 01-14-2023, 08:39 PM

Hello all,

I'm running Debian 11 in an lxc container on Proxmox and can't get rsyslog to start. When I check systemctl status rsyslog I get this:

Code:

root@fs1 ~# systemctl status rsyslog
* rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Sun 2023-01-15 02:21:29 UTC; 14min ago
TriggeredBy: * syslog.socket
       Docs: man:rsyslogd(8)
             man:rsyslog.conf(5)
             https://www.rsyslog.com/doc/
   Main PID: 20513 (code=exited, status=1/FAILURE)
        CPU: 2ms

Jan 15 02:21:29 fs1 systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 5.
Jan 15 02:21:29 fs1 systemd[1]: Stopped System Logging Service.
Jan 15 02:21:29 fs1 systemd[1]: rsyslog.service: Start request repeated too quickly.
Jan 15 02:21:29 fs1 systemd[1]: rsyslog.service: Failed with result 'exit-code'.
Jan 15 02:21:29 fs1 systemd[1]: Failed to start System Logging Service.

I checked journalctl -xe and got this:

Code:

root@fs1 ~# journalctl -xe
Jan 15 02:21:29 fs1 systemd[1]: Stopped System Logging Service.
-- Subject: A stop job for unit rsyslog.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit rsyslog.service has finished.
-- 
-- The job identifier is 1420 and the job result is done.
Jan 15 02:21:29 fs1 systemd[1]: rsyslog.service: Start request repeated too quickly.
Jan 15 02:21:29 fs1 systemd[1]: rsyslog.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit rsyslog.service has entered the 'failed' state with result 'exit-code'.
Jan 15 02:21:29 fs1 systemd[1]: Failed to start System Logging Service.
-- Subject: A start job for unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit rsyslog.service has finished with a failure.
-- 
-- The job identifier is 1420 and the job result is failed.
Jan 15 02:21:29 fs1 systemd[1]: syslog.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit syslog.socket has entered the 'failed' state with result 'service-start-limit-hit'.
Jan 15 02:21:47 fs1 systemd[1]: Reloading.
Jan 15 02:29:01 fs1 CRON[21499]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 15 02:29:01 fs1 CRON[21500]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 15 02:29:01 fs1 CRON[21499]: pam_unix(cron:session): session closed for user root

I've been searching and trying to figure this out but finally gave up and thought I'd ask here. Anyone have any ideas on this?

Thanks!
Ken