Network availability systemd dependency failure at boot

[Ed Greshko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/14 01:00, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> On 07/05/14 20:13, Sam Varshavchik wrote:
>> > So, how should this mess get fixed? Start filing bugs against all these packages, requesting a change to their systemd service file, to state a dependency on network-online.target?
>>
>> FWIW, I'm running a fully updated F20 system and not seeing any problems for httpd and named
>
> Neither did I, until either the last, or the next to last, systemd update.

As I mentioned.  Fully updated.  So I think this is the same for you.

[root at f20f ~]# rpm -q systemd
systemd-208-19.fc20.x86_64
[root at f20f ~]# uname -r
3.14.9-200.fc20.x86_64

>
>> I also run with NetworkManager-wait-online.service enabled.  There was a specific reason I started running with that enabled....don't remember why.  But, you may want to check that.
>
> The server with dhcp, httpd, named, and privoxy does not have NetworkManager installed. Both the WAN and the LAN ports are configured as static IPs.

You may want to try NetworkManager and wait-online.  WAN links can take time to become active.

I suppose the bottom line is I can't confirm your issue.  I've not made any changes to the default systemd config or service files.

- -- 
If you can't laugh at yourself, others will gladly oblige.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlO4eS0ACgkQ4JnKjVbCBvroFwCdHGRby8mzz1HWloufGrGmdlfr
hzYAnRZuglj8pgRISDcozXQZ4B0Zbc/x
=UVR0
-----END PGP SIGNATURE-----