FS#32264 - [dnsmasq] fails to start when network not ready

Attached to Project: Arch Linux
Opened by Jonathan Liu (net147) - Sunday, 28 October 2012, 06:36 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 05 December 2012, 11:05 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
The dnsmasq service fails to start if the network is not ready yet.

Additional info:
* dnsmasq 2.63-1
* netcfg 3.0-1

Steps to reproduce:
* Configure network interface with ethernet-iproute netcfg example
* Enable dnsmasq on startup
* Restart computer

Fix:
* Add "After=network.target" to the [Unit] section in dnsmasq.service
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 05 December 2012, 11:05 GMT
Reason for closing:  Implemented
Additional comments about closing:  dnsmasq-2.64-1
Comment by Dave Reisner (falconindy) - Wednesday, 31 October 2012, 21:07 GMT
Not really interested in adding this globally. Plenty of situations where you're only running dnsmasq off the loopback interface.
Comment by Jonathan Liu (net147) - Wednesday, 31 October 2012, 22:18 GMT
Yes but I was under the impression that After specifies ordering only and not a dependency on network to also be activated unlike Requires.
Comment by hamelg (hamelg) - Friday, 02 November 2012, 18:49 GMT
I have the same issue with syslog-ng when configuring a network source.

ie in syslog-ng.conf :
source net_eth0 {
udp(ip(10.0.0.11) port(6666) default-facility(kern));
};

When booting, I get a ton of message, like that :
syslog-ng.service start request repeated too quickly, refusing to start

However, at the end, systemd starts the syslog-ng service successfully.
Comment by Dave Reisner (falconindy) - Friday, 02 November 2012, 18:51 GMT
This is entirely unrelated to this bug report.

Loading...