Yes systemd is waiting until the network is up before trying to mount them, and am using the feature of systemd to not load until I need them to load.
From reading the logs further seems to be an issue with systemd not being able to properly check if network is up because I don’t use network manager, because after systemd-networkd-wait-online.service times out the nfs share get’s mounted right away,
If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.
Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.
The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.
Dec 15 14:12:33 arch systemd[1]: mnt-nfs.automount: Got automount request for /mnt/nfs, triggered by 1926 (keepassxc)
Dec 15 14:12:33 arch systemd[1]: Starting Wait for Network to be Configured...
Dec 15 14:12:33 arch systemd-networkd[1612]: enp3s0: DHCPv4 address 192.168.0.3/24, gateway 192.168.0.1 acquired from 192.168.0.1
Dec 15 14:12:33 arch systemd-timesyncd[1587]: Network configuration changed, trying to establish connection.
Dec 15 14:12:33 arch systemd-timesyncd[1587]: Network configuration changed, trying to establish connection.
Dec 15 14:12:38 arch systemd[1778]: Started tmux child pane 2350 launched by process 2106.
Dec 15 14:12:46 arch systemd[1778]: Created slice Slice /app/dbus-:1.15-org.a11y.atspi.Registry.
Dec 15 14:12:46 arch systemd[1778]: Started dbus-:1.15-org.a11y.atspi.Registry@0.service.
Dec 15 14:12:46 arch at-spi2-registryd[2526]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 15 14:12:58 arch kernel: logitech-hidpp-device 0003:046D:4074.0008: HID++ 4.2 device connected.
Dec 15 14:13:03 arch systemd-timesyncd[1587]: Contacted time server 161.53.131.231:123 (2.arch.pool.ntp.org).
Dec 15 14:13:03 arch systemd-timesyncd[1587]: Initial clock synchronization to Sun 2024-12-15 14:13:03.310583 CET.
Dec 15 14:14:33 arch systemd-networkd-wait-online[2039]: Timeout occurred while waiting for network connectivity.
Dec 15 14:14:33 arch systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Dec 15 14:14:33 arch systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Dec 15 14:14:33 arch systemd[1]: Failed to start Wait for Network to be Configured.
Dec 15 14:14:33 arch systemd[1]: Reached target Network is Online.
Dec 15 14:14:33 arch systemd[1]: Mounting /mnt/nfs...
According to log’s it’s a systemd-networkd-wait-online.service issue, which shouldn’t be an issue because I’m using ethernet and share get’s automaunt request when I login into my user and load my xorg server.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Is systemd waiting until the network is up before mounting them?
autofs to mount them on demand might be a viable workaround.
Yes systemd is waiting until the network is up before trying to mount them, and am using the feature of systemd to not load until I need them to load.
From reading the logs further seems to be an issue with systemd not being able to properly check if network is up because I don’t use network manager, because after systemd-networkd-wait-online.service times out the nfs share get’s mounted right away,
It was a systemd issue, after installing network manager, enabling it and disabling systemd-networkd share now mount’s in a matter of second’s.
I don’t like the fact I got to use network manager, but whatever.
If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.
Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.
Run:
sudo systemctl edit systemd-networkd-wait-online.serviceThat adds the override.conf for the service. Add these lines:
The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.
What’s in the log?
According to log’s it’s a systemd-networkd-wait-online.service issue, which shouldn’t be an issue because I’m using ethernet and share get’s automaunt request when I login into my user and load my xorg server.