Bug#757903: [Syslog-ng-maintainers] Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
% 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. Turns out this is a known issue with systemd and socket activated services (such as syslog-ng), see #736258 and #751744. However, we do not use the recommended --restart-after-upgrade mechanism, and I'm unsure whether that would fix the issue. Nevertheless, I have a far better idea of what is happening, and will try to reproduce the issue locally. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: [Syslog-ng-maintainers] Bug#757903: Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Processing control commands: reassign 757903 dh-systemd Bug #757903 [syslog-ng-core] syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed. Bug reassigned from package 'syslog-ng-core' to 'dh-systemd'. No longer marked as found in versions syslog-ng/3.5.6-1. Ignoring request to alter fixed versions of bug #757903 to the same values previously set forcemerge 751741 757903 Bug #751741 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #736258 [dh-systemd] acpid fails to upgrade on amd64 Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Bug #757903 [dh-systemd] syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed. Severity set to 'normal' from 'grave' Added indication that 757903 affects acpid,monopd,cups-daemon,gpsd Bug #736258 [dh-systemd] acpid fails to upgrade on amd64 Bug #751744 [dh-systemd] dh-systemd: postinst snippets should stop foo.socket during upgrades too Merged 736258 751741 751744 757903 affects + 751741 syslog-ng-core Unknown command or malformed arguments to command. -- 736258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736258 751741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751741 751744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751744 757903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: [Syslog-ng-maintainers] Bug#757903: Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Control: reassign 757903 dh-systemd Control: forcemerge 751741 757903 Control: affects + 751741 syslog-ng-core Gergely Nagy alger...@balabit.hu writes: Turns out this is a known issue with systemd and socket activated services (such as syslog-ng), see #736258 and #751744. However, we do not use the recommended --restart-after-upgrade mechanism, and I'm unsure whether that would fix the issue. I'm changing syslog-ng-core to use --restart-after-upgrade, but that will likely not solve the problem completely (although I have not been able to reproduce it locally), so I'm reassigning the bug to dh-systemd, and merging it with other similar issues. 3.5.6-2 will likely hit unstable by tonight, I would be very interested in hearing whether the problem persists with that version. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
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. Cheers -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (650, 'unstable'), (601, 'testing'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslog-ng-core depends on: ii init-system-helpers 1.20 ii libc62.19-7 ii libcap2 1:2.24-4 ii libevtlog0 0.2.12-6 ii libglib2.0-0 2.40.0-4 ii libivykis0 0.36.2-1 ii libnet1 1.1.6+dfsg-3 ii libpcre3 1:8.35-3 ii libssl1.0.0 1.0.1i-2 ii libsystemd-daemon0 208-7 ii libwrap0 7.6.q-25 ii util-linux 2.20.1-5.8 Versions of packages syslog-ng-core recommends: ii logrotate 3.8.7-1 Versions of packages syslog-ng-core suggests: pn syslog-ng-mod-amqp none pn syslog-ng-mod-geoipnone iu syslog-ng-mod-json 3.5.6-1 iu syslog-ng-mod-mongodb 3.5.6-1 pn syslog-ng-mod-redisnone pn syslog-ng-mod-smtp none iu syslog-ng-mod-sql 3.5.6-1 pn syslog-ng-mod-stompnone -- no debconf information -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
Sebastian Ramacher sramac...@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? -- |8] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757903: syslog-ng-core: invoke-rc.d: initscript syslog-ng, action stop failed.
On 2014-08-12 13:51:11, Gergely Nagy wrote: Sebastian Ramacher sramac...@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 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,
