% 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:
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
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
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
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
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
6 matches
Mail list logo