Package: rsyslog
Version: 8.24.0-1
Severity: minor

Dear Maintainer,

I noticed some 'FAILED' lines scroll by quickly at boot; upon investigation:

root@stretch:/home/test# systemctl status | head -2
● stretch
    State: degraded
root@stretch:/home/test# systemctl list-units --state=failed 
  UNIT            LOAD   ACTIVE SUB    DESCRIPTION                              
                         
● rsyslog.service loaded failed failed System Logging Service                   
                         

LOAD   = ...
root@stretch:/home/test# systemctl status rsyslog
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Tue 2017-03-21 16:48:05 EDT; 25min 
ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
  Process: 760 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE)
 Main PID: 760 (code=exited, status=1/FAILURE)

Mar 21 16:48:04 stretch systemd[1]: Failed to start System Logging Service.
Mar 21 16:48:04 stretch systemd[1]: rsyslog.service: Unit entered failed state.
Mar 21 16:48:04 stretch systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
Mar 21 16:48:05 stretch systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
Mar 21 16:48:05 stretch systemd[1]: Stopped System Logging Service.
Mar 21 16:48:05 stretch systemd[1]: rsyslog.service: Start request repeated too 
quickly.
Mar 21 16:48:05 stretch systemd[1]: Failed to start System Logging Service.
Mar 21 16:48:05 stretch systemd[1]: rsyslog.service: Unit entered failed state.
Mar 21 16:48:05 stretch systemd[1]: rsyslog.service: Failed with result 
'exit-code'.

I don't *think* this happened right after fresh install, but this system was
hung and reset a few times while looking into unrelated #858162. However, after
several clean reboots, the situation persists, and the pidfile appears to be
correctly updated each time.

Also, rsyslogd prints stuff on stderr when refusing to start because of a
pidfile, but I don't see these, or any other messages from rsyslogd anywhere --
only from systemd itself, above.

So, I don't think this is a dupe of #594112.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=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.47
ii  libc6                2.24-9
ii  libestr0             0.1.10-2
ii  libfastjson4         0.99.4-1
ii  liblogging-stdlog0   1.0.5-2+b2
ii  liblognorm5          2.0.1-1.1+b1
ii  libsystemd0          232-19
ii  libuuid1             2.29.1-1
ii  lsb-base             9.20161125
ii  zlib1g               1:1.2.8.dfsg-5

Versions of packages rsyslog recommends:
ii  logrotate  3.11.0-0.1

Versions of packages rsyslog suggests:
pn  rsyslog-doc                    <none>
pn  rsyslog-gnutls                 <none>
pn  rsyslog-gssapi                 <none>
pn  rsyslog-mongodb                <none>
pn  rsyslog-mysql | rsyslog-pgsql  <none>
pn  rsyslog-relp                   <none>

-- no debconf information

Reply via email to