I occasionally hit this when transitioning to a VPN connection or
shutting one down:
Mar 16 17:19:29 vfr NetworkManager[559]: <info> VPN connection 'cbeyond'
(IP Config Get) complete.
Mar 16 17:19:29 vfr NetworkManager[559]: <info> Policy set 'Built-in
Ethernet' (em1) as default for IPv4 routing and DNS.
Mar 16 17:19:29 vfr NetworkManager[559]: <info> DNS: starting dnsmasq...
Mar 16 17:19:29 vfr dnsmasq[740]: exiting on receipt of SIGTERM
Mar 16 17:19:29 vfr dnsmasq[31273]: failed to create listening socket for
127.0.0.1: Address already in use
Mar 16 17:19:29 vfr dnsmasq[31273]: FAILED to start up
Mar 16 17:19:30 vfr NetworkManager[559]: <info> VPN plugin state changed:
started (4)
Mar 16 17:19:30 vfr dbus[610]: [system] Activating service
name='org.freedesktop.nm_dispatcher' (using servicehelper)
Mar 16 17:19:30 vfr NetworkManager[559]: <warn> dnsmasq exited with error:
Network access problem (address in use; permissions; etc) (2)
It seems that NM kills the running dnsmasq and then restarts it. The
new instance sometimes fails to bind because the old instance hasn't
finished closing the port.
My work-around is to:
sudo systemctl start dnsmasq.service
when I notice the failure.
How can I eliminate this race?
--
Garry T. Williams
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
