I don't know if it can help but I've a similar bug which involves restarting Rsyslog.
I use Ubuntu 16.04 LTS 64bits with Rsyslog 8.16-0-1ubuntu3 on two kind of hardware:
- docker-machine
- AWS EC2
I noticed that on servers that don't use systemd -- in this case docker-machine -- using the sysV init script doesn't work.
The reason:
L 54 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --exec $DAEMON
If you remove the --quiet:
/etc/init.d/rsyslog stop
* Stopping enhanced syslogd rsyslogd
No /usr/sbin/rsyslogd found running; none killed.
...done.
Then if you remove --exec $DAEMON it works.
I have the same behavior when I use the init script on a systemd based ubuntu. But the systemd job seems to work fine.
And of course, /etc/init.d/rsyslog rotate doesn't work either.
I'm currently debating with my self on how I'm going to handle that..
Hi,
I don't know if it can help but I've a similar bug which involves restarting Rsyslog.
I use Ubuntu 16.04 LTS 64bits with Rsyslog 8.16-0-1ubuntu3 on two kind of hardware:
- docker-machine
- AWS EC2
I noticed that on servers that don't use systemd -- in this case docker-machine -- using the sysV init script doesn't work.
The reason:
L 54 start-stop-daemon --stop --quiet --retry= TERM/30/ KILL/5 --pidfile $PIDFILE --exec $DAEMON
If you remove the --quiet: d/rsyslog stop
/etc/init.
* Stopping enhanced syslogd rsyslogd
No /usr/sbin/rsyslogd found running; none killed.
...done.
Then if you remove --exec $DAEMON it works.
I have the same behavior when I use the init script on a systemd based ubuntu. But the systemd job seems to work fine.
And of course, /etc/init.d/rsyslog rotate doesn't work either.
I'm currently debating with my self on how I'm going to handle that..