[syslog-ng] [Bug 125] [systemd] refuses stop request from systemctl on socket activated start

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=125





--- Comment #2 from Balazs Scheidler <bazsi at balabit.hu>  2011-06-24 13:45:34 ---
Hi,

my systemd fu is not complete (having just installed F15 in a virtualbox environment), but after some fiddling, syslog-ng seems to cope with systemd just fine.

I've used this syslog-ng.service file (not the same as the example in the source tarball):

[Unit]
Description=syslog-ng

[Service]
ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
ExecStart=/usr/local/sbin/syslog-ng -F -dv
ExecReload=/bin/kill -HUP $MAINPID
Sockets=syslog.socket

Then, I've changed syslog.socket to activate syslog-ng, instead of systemd-kmsg-syslogd.service, by setting:

Service=syslog-ng.service

Once having done that, and rebooting the system, syslog-ng was properly activated whenever logger sent messages to /dev/log:

# ps axwu | grep syslog-ng
root      1586  0.0  0.2  43464  2124 ?        Ss   12:08   0:00 /usr/local/sbin/syslog-ng -F -dv
root      1615  0.0  0.1 108608   840 pts/2    S+   12:12   0:00 grep --color=auto syslog-ng
[root at f15 ~]# systemctl stop syslog-ng.service
[root at f15 ~]# ps axwu | grep syslog-ng
root      1620  0.0  0.1 108608   840 pts/2    S+   12:12   0:00 grep --color=auto syslog-ng
[root at f15 ~]# logger foobar
[root at f15 ~]# ps axwu | grep syslog-ng
root      1624  3.0  0.2  43464  2124 ?        Ss   12:13   0:00 /usr/local/sbin/syslog-ng -F -dv
root      1630  0.0  0.1 108608   836 pts/2    S+   12:13   0:00 grep --color=auto syslog-ng
[root at f15 ~]# tail -1 /var/log/messages 
Jun 22 12:13:04 f15 bazsi: foobar
[root at f15 ~]# systemctl stop syslog-ng.service
[root at f15 ~]# ps axwu | grep syslog-ng
root      1637  0.0  0.1 108608   836 pts/2    S+   12:13   0:00 grep --color=auto syslog-ng
[root at f15 ~]# exit

SIGTERM is indeed caught by syslog-ng, in order to properly execute exit strategies. One difference is that you were using 3.2, whereas I was using the
latest git tree (post 3.3.0beta1)

Let me retest with 3.2.x


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.