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