FS#65217 - [syslog-ng] 3.25.1-2 service doesn't stop normally, has to be killed by systemd

Attached to Project: Arch Linux
Opened by Ash (eta-carinae) - Monday, 20 January 2020, 10:39 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 24 January 2020, 23:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

The syslog-ng 'default' service, started with systemctl start syslog-ng@default.service, doesn't stop with
SIGTERM as previous versions did, so systemd runs a stop job and SIGKILLs it after 90 seconds:

Jan 20 05:29:10 host systemd[1]: syslog-ng@default.service: State 'stop-sigterm' timed out. Killing.
Jan 20 05:29:10 host systemd[1]: syslog-ng@default.service: Killing process 909 (syslog-ng) with signal SIGKILL.
Jan 20 05:29:10 host systemd[1]: syslog-ng@default.service: Main process exited, code=killed, status=9/KILL
Jan 20 05:29:10 host systemd[1]: syslog-ng@default.service: Failed with result 'timeout'.
Jan 20 05:29:10 host systemd[1]: Stopped System Logger Daemon "default" instance.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 24 January 2020, 23:48 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#65206 
Comment by freswa (frederik) - Monday, 20 January 2020, 14:24 GMT
Could you provide the journal log of the syslog-ng@default unit please?
Comment by Ash (eta-carinae) - Monday, 20 January 2020, 15:04 GMT
I don't have any journal entries from the syslog-ng@default unit, only the entries from systemd I included above and
the SERVICE_START/SERVICE_STOP entries from audit. I seem to recall seeing logging from syslog-ng in the past but even
on a debian system I'm running with 3.19 I don't see anything other than some connection failures. Even adding -v doesn't
produce any entries. This is with the packaged service file.
Comment by freswa (frederik) - Monday, 20 January 2020, 15:26 GMT
Could you try to backup your syslog-ng folder and check if the issue persists with a clean data directory?
Comment by Ash (eta-carinae) - Monday, 20 January 2020, 18:24 GMT
I went ahead and completely uninstalled syslog-ng and deleted everything it left behind from my system
(/var/lib/syslog-ng, /etc/syslog-ng, /run/syslog-ng.*), disabled the service, then reinstalled and started
it with the default configuration. Same problem shutting down.
Comment by Lone_Wolf (Lone_Wolf) - Monday, 20 January 2020, 23:03 GMT
This is the same bug as described in https://bugs.archlinux.org/task/65206

From my description there: On shutdown a message about a stop job is shown.

I didn't go into detail about the message and waiting 90 seconds before system continues shutdown,
because the main problem is nothing is logged.

Downgrading to 3.25.1-1 is the best workaround for now.

Loading...