On Sat, 2017-12-16 at 10:03 -0500, Sam Varshavchik wrote:
Just had another boot that utterly failed because services that were supposed to start only after the network interfaces came up, didn't. They started too soon. Privoxy's logfile has the smoking gun:
2017-12-16 09:42:39.875 7f4acdaa6740 Fatal error: can't bind to 192.168.0.1:8000: Cannot assign requested address
This is despite that NetworkManager-wait-online was enabled and active. This is what everyone kept telling me was the only thing that needed to be done. Well, it was enabled:
[root@shorty system]# systemctl status NetworkManager-wait-online ● NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait- online.service; e Active: active (exited) since Sat 2017-12-16 09:42:39 EST; 12min ago Docs: man:nm-online(1) Process: 977 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited, sta Main PID: 977 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/NetworkManager-wait-online.service
Dec 16 09:42:32 shorty.email-scan.com systemd[1]: Starting Network Manager Wait Dec 16 09:42:39 shorty.email-scan.com systemd[1]: Started Network Manager Wait O
It came up at 09:42:39. And, at 09:42:39 privoxy also came up. And privoxy still blew chunks because the primary network interface wasn't up yet.
Why is it so friggin difficult to get something this simple, this basic concept of starting things only after the network interfaces are up, working correctly, and reliably?
Oh yeah, I know. systemd.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Similar problem here Latest updates mean that my nfs mounts in /etc/fstab fail on boot because network is said to be running before DHCP has sorted itself out! This assumes I am interpreting journalctl output correctly.
Dec 16 13:26:33 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430793.6518] manager: startup complete Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Started Network Manager Wait Online. Dec 16 13:26:33 hayling.jaa.org.uk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Reached target Network is Online. <<<<<<<<<<<<<<<<<<<<< Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Mounting /global... Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Starting Notify NFS peers of a restart... Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Mounting /home... Dec 16 13:26:33 hayling.jaa.org.uk sm-notify[2847]: Version 2.2.1 starting Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Started Notify NFS peers of a restart. Dec 16 13:26:33 hayling.jaa.org.uk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpc-statd-notify comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 16 13:26:33 hayling.jaa.org.uk kernel: FS-Cache: Loaded Dec 16 13:26:33 hayling.jaa.org.uk kernel: FS-Cache: Netfs 'nfs' registered for caching Dec 16 13:26:33 hayling.jaa.org.uk kernel: Key type dns_resolver registered Dec 16 13:26:33 hayling.jaa.org.uk kernel: NFS: Registering the id_resolver key type Dec 16 13:26:33 hayling.jaa.org.uk kernel: Key type id_resolver registered Dec 16 13:26:33 hayling.jaa.org.uk kernel: Key type id_legacy registered Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: global.mount: Mount process exited, code=exited status=32 Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Failed to mount /global. Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Dependency failed for Remote File Systems. Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'. Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: global.mount: Unit entered failed state. Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: home.mount: Mount process exited, code=exited status=32 Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: Failed to mount /home. Dec 16 13:26:33 hayling.jaa.org.uk systemd[1]: home.mount: Unit entered failed state.
1 second later??!!! ...
Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4301] device (enp0s31f6): state change: config -> ip-config (reason 'none', internal state 'managed') Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4306] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4383] dhcp4 (enp0s31f6): dhclient started with pid 2886 Dec 16 13:26:34 hayling.jaa.org.uk dhclient[2886]: DHCPREQUEST on enp0s31f6 to 255.255.255.255 port 67 (xid=0x77026130) Dec 16 13:26:34 hayling.jaa.org.uk dhclient[2886]: DHCPACK from 148.197.29.5 (xid=0x77026130) Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): address 148.197.29.202 Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): plen 24 (255.255.255.0) Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): gateway 148.197.29.254 Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): lease time 86400 Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): nameserver '148.197.29.5' Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): nameserver '212.104.130.9' Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): domain name 'jaa.org.uk' Dec 16 13:26:34 hayling.jaa.org.uk NetworkManager[1148]: <info> [1513430794.4715] dhcp4 (enp0s31f6): state changed unknown -> bound
Anyone else with the same problem/
John