[Syslog-ng-maintainers] Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action "stop" failed.

Sebastian Ramacher sramacher at debian.org
Tue Aug 12 21:16:42 BST 2014 

On 2014-08-12 13:51:11, Gergely Nagy wrote:
> Sebastian Ramacher <sramacher at debian.org> writes:
> 
> > Package: syslog-ng-core
> > Version: 3.5.6-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Today the upgrade from 3.5.5-2 to 3.5.6-1 failed with:
> > | Processing triggers for syslog-ng-core (3.5.6-1) ...
> > | Job for syslog-ng.service canceled.
> > | invoke-rc.d: initscript syslog-ng, action "stop" failed.
> > | dpkg: error processing package syslog-ng-core (--configure):
> > |  subprocess installed post-installation script returned error exit status 1
> >
> > Uncommenting invoke-rc.d syslog-ng stop || exit $? in line 6 of the
> > postinst script and running apt install -f fixes the issue and lets the
> > installation complete.
> >
> > I've also seen this issue while installing syslog-ng-core for the first
> > time on another system.
> >
> > Both systems are running systemd if that matters. Let me know if you
> > want more info. My other system waits to be upgraded.
> 
> What does "systemctl status syslog-ng.service" print?

From my second system before the upgrade:

$ systemctl status syslog-ng.service
syslog-ng.service - System Logger Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled)
   Active: active (running) since Tue 2014-08-12 12:40:47 CEST; 7h ago
     Docs: man:syslog-ng(8)
  Process: 4262 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
 Main PID: 737 (syslog-ng)
   CGroup: /system.slice/syslog-ng.service
           └─737 /usr/sbin/syslog-ng -F

Aug 12 12:40:47 mercury2 systemd[1]: Started System Logger Daemon.
Aug 12 14:08:52 mercury2 systemd[1]: Reloading System Logger Daemon.
Aug 12 14:08:52 mercury2 systemd[1]: Reloaded System Logger Daemon.

However, upgrading syslog-ng-core there didn't cause it to fail. So, I tried to
debug the issue a bit, added a set -x to the postinst script and run
dpkg-reconfigure syslog-ng-core some times. Interestingly enough it works most
of the time, but fails every fourth or fifth try.

From a good run:

$ systemctl status syslog-ng.service; dpkg-reconfigure syslog-ng-core
syslog-ng.service - System Logger Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled)
   Active: active (running) since Tue 2014-08-12 20:41:57 CEST; 5s ago
     Docs: man:syslog-ng(8)
 Main PID: 24065 (syslog-ng)
   CGroup: /system.slice/syslog-ng.service
           └─24065 /usr/sbin/syslog-ng -F

Aug 12 20:41:57 mercury2 systemd[1]: Started System Logger Daemon.
Aug 12 20:41:57 mercury2 systemd[1]: Started System Logger Daemon.
+ [ configure = triggered ]
+ dpkg-trigger register-syslog-ng-plugin
+ deb-systemd-helper unmask syslog-ng.service
+ deb-systemd-helper --quiet was-enabled syslog-ng.service
+ deb-systemd-helper enable syslog-ng.service
+ [ -x /etc/init.d/syslog-ng ]
+ update-rc.d syslog-ng defaults 10 90
+ exit 0
Processing triggers for syslog-ng-core (3.5.6-1) ...
+ [ triggered = triggered ]
+ invoke-rc.d syslog-ng stop
Warning: Stopping syslog-ng.service, but it can still be activated by:
  syslog.socket
+ invoke-rc.d syslog-ng start
+ exit 0

From a bad run:

% systemctl status syslog-ng.service; dpkg-reconfigure syslog-ng-core
syslog-ng.service - System Logger Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled)
   Active: active (running) since Tue 2014-08-12 20:42:04 CEST; 1s ago
     Docs: man:syslog-ng(8)
 Main PID: 24163 (syslog-ng)
   CGroup: /system.slice/syslog-ng.service
           └─24163 /usr/sbin/syslog-ng -F

Aug 12 20:42:04 mercury2 systemd[1]: Started System Logger Daemon.
Aug 12 20:42:04 mercury2 systemd[1]: Started System Logger Daemon.
+ [ configure = triggered ]
+ dpkg-trigger register-syslog-ng-plugin
+ deb-systemd-helper unmask syslog-ng.service
+ deb-systemd-helper --quiet was-enabled syslog-ng.service
+ deb-systemd-helper enable syslog-ng.service
+ [ -x /etc/init.d/syslog-ng ]
+ update-rc.d syslog-ng defaults 10 90
+ exit 0
Processing triggers for syslog-ng-core (3.5.6-1) ...
+ [ triggered = triggered ]
+ invoke-rc.d syslog-ng stop
Job for syslog-ng.service canceled.
invoke-rc.d: initscript syslog-ng, action "stop" failed.
+ exit 1
dpkg: error processing package syslog-ng-core (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 syslog-ng-core

I was suspecting a systemd rate limit at first, but the upgrade that failed
today didn't include any other packages shipping anything systemd related. See
the attached history.log for the packages involved in the failing upgrade.

Cheers
-- 
Sebastian Ramacher
-------------- next part --------------
Start-Date: 2014-08-12  09:23:59
Commandline: apt upgrade -V
Upgrade: libgl1-mesa-dev:amd64 (10.2.4-1, 10.2.5-1), liblqr-1-0:amd64 (0.4.2-1, 0.4.2-2), libegl1-mesa:amd64 (10.2.4-1, 10.2.5-1), libopenvg1-mesa:amd64 (10.2.4-1, 10.2.5-1), syslog-ng-mod-json:amd64 (3.5.5-2, 3.5.6-1), libssl1.0.0:amd64 (1.0.1i-1, 1.0.1i-2), libproc-processtable-perl:amd64 (0.50-1, 0.50-2), libegl1-mesa-drivers:amd64 (10.2.4-1, 10.2.5-1), syslog-ng-core:amd64 (3.5.5-2, 3.5.6-1), libegl1-mesa-dev:amd64 (10.2.4-1, 10.2.5-1), libfreerdp1:amd64 (1.1.0~git20140809.1.b07a5c1+dfsg-1, 1.1.0~git20140809.1.b07a5c1+dfsg-2), python-pil:amd64 (2.5.1-2, 2.5.1-4), maxima:amd64 (5.33.0-14, 5.33.0-15), libgl1-mesa-dri:amd64 (10.2.4-1, 10.2.5-1), libgl1-mesa-dri:i386 (10.2.4-1, 10.2.5-1), libwxbase3.0-0:amd64 (3.0.1-2, 3.0.1-3), parted:amd64 (3.2-3, 3.2-4), syslog-ng:amd64 (3.5.5-2, 3.5.6-1), python-imaging:amd64 (2.5.1-2, 2.5.1-4), libparted2:amd64 (3.2-3, 3.2-4), libglapi-mesa:amd64 (10.2.4-1, 10.2.5-1), libglapi-mesa:i386 (10.2.4-1, 10.2.5-1), gdbserver:amd64 (7.7.1-2, 7.7.1+dfsg-1), python-reportlab-accel:amd64 (3.0-1+b1, 3.1.8-2), syslog-ng-mod-sql:amd64 (3.5.5-2, 3.5.6-1), python-reportlab:amd64 (3.0-1, 3.1.8-2), libgles2-mesa:amd64 (10.2.4-1, 10.2.5-1), blender:amd64 (2.71+dfsg0-3, 2.71+dfsg0-4), libgl1-mesa-glx:amd64 (10.2.4-1, 10.2.5-1), libgl1-mesa-glx:i386 (10.2.4-1, 10.2.5-1), gdb:amd64 (7.7.1-2, 7.7.1+dfsg-1), libssl-dev:amd64 (1.0.1i-1, 1.0.1i-2), blender-data:amd64 (2.71+dfsg0-3, 2.71+dfsg0-4), libwayland-egl1-mesa:amd64 (10.2.4-1, 10.2.5-1), libqt5webkit5:amd64 (5.3.1+dfsg-2, 5.3.1+dfsg-3), build-essential:amd64 (11.6, 11.7), libgbm1:amd64 (10.2.4-1, 10.2.5-1), libwxgtk3.0-0:amd64 (3.0.1-2, 3.0.1-3), libparted-fs-resize0:amd64 (3.2-3, 3.2-4), maxima-share:amd64 (5.33.0-14, 5.33.0-15), mesa-common-dev:amd64 (10.2.4-1, 10.2.5-1), openssl:amd64 (1.0.1i-1, 1.0.1i-2), libgles2-mesa-dev:amd64 (10.2.4-1, 10.2.5-1), syslog-ng-mod-mongodb:amd64 (3.5.5-2, 3.5.6-1)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2014-08-12  09:26:24
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/syslog-ng-maintainers/attachments/20140812/93cbd630/attachment-0001.sig>

More information about the Syslog-ng-maintainers mailing list