Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I gave up on systemd. Sorry. I simply had to restart the security-patched dnsmasq, anything else would not have been safe. I had to use killall dnsmasq and then systemctl restart libvirtd or dnsmasq would not restart.

Mostly I gave up on systemd when I found this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1450327

Here's a transcript of the work-around I used in action:

[metta@crawler ~]$ rpm -q dnsmasq dnsmasq-2.76-3.fc26.x86_64 [metta@crawler ~]$ ps -O lstart ax | grep dnsm 1304 Fri Sep 29 20:41:33 2017 S ? 00:00:54 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 1305 Fri Sep 29 20:41:33 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 1343 Fri Sep 29 20:41:33 2017 S ? 00:00:53 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 1344 Fri Sep 29 20:41:33 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 25928 Thu Oct 5 14:29:52 2017 S pts/11 00:00:00 grep --color=auto dnsm [metta@crawler ~]$ sudo killall dnsmasq [metta@crawler ~]$ ps -O lstart ax | grep dnsm 26284 Thu Oct 5 14:30:14 2017 S pts/11 00:00:00 grep --color=auto dnsm [metta@crawler ~]$ sudo systemctl restart libvirtd.service [metta@crawler ~]$ ps -O lstart ax | grep dnsm 26366 Thu Oct 5 14:30:20 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 26367 Thu Oct 5 14:30:20 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 26373 Thu Oct 5 14:30:20 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 26374 Thu Oct 5 14:30:20 2017 S ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper 26376 Thu Oct 5 14:30:21 2017 S pts/11 00:00:00 grep --color=auto dnsm [metta@crawler ~]$

I look forward to a beautiful day with systemd someday but until then I hope this helps you stay safe with the dnsmasq update: https://bodhi.fedoraproject.org/updates/FEDORA-2017-24f067299e

I gave up on systemd. Sorry. I simply had to restart the security-patched dnsmasq, anything else would not have been safe. I had to use killall dnsmasq and then systemctl restart libvirtd or dnsmasq would not restart.

Mostly I gave up on systemd when I found this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1450327

Here's a transcript of the work-around I used in action:

[metta@crawler ~]$ rpm -q dnsmasq
dnsmasq-2.76-3.fc26.x86_64
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
 1304 Fri Sep 29 20:41:33 2017 S ?        00:00:54 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1305 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1343 Fri Sep 29 20:41:33 2017 S ?        00:00:53 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1344 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
25928 Thu Oct  5 14:29:52 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ sudo killall dnsmasq
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
26284 Thu Oct  5 14:30:14 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ sudo systemctl restart libvirtd.service 
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
26366 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26367 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26373 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26374 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26376 Thu Oct  5 14:30:21 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ 

I look forward to a beautiful day with systemd someday but until then I hope this helps you stay safe with the dnsmasq update: https://bodhi.fedoraproject.org/updates/FEDORA-2017-24f067299e

I gave up on systemd. Sorry. I simply had to restart the security-patched dnsmasq, anything else would not have been safe. I had to use killall dnsmasq and then systemctl restart libvirtd or dnsmasq would not restart.

Mostly I gave up on systemd when I found this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1450327

Here's a transcript of the work-around I used in action:

[metta@crawler ~]$ rpm -q dnsmasq
dnsmasq-2.76-3.fc26.x86_64
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
 1304 Fri Sep 29 20:41:33 2017 S ?        00:00:54 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1305 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1343 Fri Sep 29 20:41:33 2017 S ?        00:00:53 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1344 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
25660 Thu Oct  5 14:28:59 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ sudo systemctl restart dnsmasq
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
 1304 Fri Sep 29 20:41:33 2017 S ?        00:00:54 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1305 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1343 Fri Sep 29 20:41:33 2017 S ?        00:00:53 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1344 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
25693 Thu Oct  5 14:29:15 2017 S pts/11   00:00:00 grep --color=auto dnsm

Start time of dnsmasq did not change when sudo systemctl restart libvirtd was used. Trying killall:

[metta@crawler ~]$ ps -O lstart ax | grep dnsm
 1304 Fri Sep 29 20:41:33 2017 S ?        00:00:54 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1305 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1343 Fri Sep 29 20:41:33 2017 S ?        00:00:53 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
 1344 Fri Sep 29 20:41:33 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
25928 Thu Oct  5 14:29:52 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ sudo killall dnsmasq
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
26284 Thu Oct  5 14:30:14 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ sudo systemctl restart libvirtd.service 
[metta@crawler ~]$ ps -O lstart ax | grep dnsm
26366 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26367 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26373 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26374 Thu Oct  5 14:30:20 2017 S ?        00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/heartbeat.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
26376 Thu Oct  5 14:30:21 2017 S pts/11   00:00:00 grep --color=auto dnsm
[metta@crawler ~]$ 

I look forward to a beautiful day with systemd someday but until then I hope this helps you stay safe with the dnsmasq update: https://bodhi.fedoraproject.org/updates/FEDORA-2017-24f067299e