You are not logged in.
Pages: 1
Hi,
My newly installed system (Oct 1 iso) is using iwd with the following /etc/iwd/main.conf:
[General]
EnableNetworkConfiguration=true
[Network]
NameResolvingService=systemdsystemd-resolved is enabled. openresolv , networkmanager not installed.
When booting, there is an error message: Failed to start Wireless service. The journal shows a restart was successful. And indeed, after logging in, the network has no issue at all.
systemd[1]: Starting Wireless service...
systemd[391]: iwd.service: Failed to set up mount namespacing: /run/systemd/unit-root/run/systemd/resolve/stub-resolv.conf: No such file >
systemd[391]: iwd.service: Failed at step NAMESPACE spawning /usr/lib/iwd/iwd: No such file or directory
systemd[1]: iwd.service: Main process exited, code=exited, status=226/NAMESPACE
systemd[1]: iwd.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Wireless service.
systemd[1]: iwd.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Wireless service.
systemd[1]: Starting Wireless service...
iwd[418]: Wireless daemon version 1.9
iwd[418]: Loaded configuration from /etc/iwd/main.conf
systemd[1]: Started Wireless service.As it seems the error message is not really impacting anything, it's just an eyesore. Is there anyway to remove it?
Thanks a lot
Last edited by learnarch (2020-10-06 03:08:25)
Offline
IWD starts too early, and systemd-resolved's voodo is not available on /run for some reason it seems.
YET it's not an actual issue, probably even upstream & packager are aware of it.
To reduce logging that? Idk about ways that preserve the rest of logging...
Btw this post title insinuates an actual & persistent issue...which is not the case.
Offline
systemd[391]: iwd.service: Failed at step NAMESPACE spawning /usr/lib/iwd/iwd: No such file or directory
This doesn't looks like a dependency on systemd-resolved to me. You can try this:
$ cat /lib/systemd/system/iwd.service
[Unit]
Requires=systemd-resolved.service
...Restart and then:
$ systemd-analyze blameTo confirm the iwd.service indeed started after systemd-resolved.
Last edited by solskog (2020-10-06 09:22:53)
Offline
This:
systemd[391]: iwd.service: Failed to set up mount namespacing: /run/systemd/unit-root/run/systemd/resolve/stub-resolv.conf: No such file >Is reported by this:
systemd[391]: iwd.service: Failed at step NAMESPACE spawning /usr/lib/iwd/iwd: No such file or directoryLet's call it voodo logging...
Btw OP, analyzing the boot chain is indeed a good idea.
Maybe a race condition? IWD starts too early and resolved is not ready yet?
IIRC IWD caused me race conditions (very frequently) when mixed with systemd-{networkd,resolved} when I tested it as vanilla.
OP I just noticed according to the documentation that the usage of systemd-resolved is the default, so the config entry is em...redundant. But that's ok.
Last edited by GaKu999 (2020-10-06 15:55:21)
Offline
Pages: 1