Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 634096 - sys-apps/systemd-235 - systemd-networkd fails to start - Executable path is not absolute: !!/lib/systemd/systemd-networkd
Summary: sys-apps/systemd-235 - systemd-networkd fails to start - Executable path is n...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo systemd Team
URL: https://github.com/systemd/systemd/bl...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-12 12:08 UTC by Juergen Rose
Modified: 2017-10-12 21:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Rose 2017-10-12 12:08:39 UTC 
After installing systemd-235 systemd-networkd fails to start. 
'systemctl status systemd-networkd' reports:

root@lynx:/root(83)# systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: error (Reason: Exec format error)
   Active: failed (Result: timeout) since Wed 2017-10-11 23:16:08 CEST; 10h ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 17077 (code=exited, status=0/SUCCESS)

Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Unit entered failed state.
Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Failed with result 'timeout'.
Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Failed to schedule restart job: Unit systemd-networkd.service is not loaded properly: Exec format error.
Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Unit entered failed state.
Oct 11 23:16:08 lynx systemd[1]: systemd-networkd.service: Failed with result 'timeout'.
Oct 12 01:00:35 lynx systemd[1]: /lib/systemd/system/systemd-networkd.service:23: Executable path is not absolute: !!/lib/systemd/systemd-networkd
Oct 12 01:00:47 lynx systemd[1]: /lib/systemd/system/systemd-networkd.service:23: Executable path is not absolute: !!/lib/systemd/systemd-networkd
Oct 12 08:10:43 lynx systemd[1]: /lib/systemd/system/systemd-networkd.service:23: Executable path is not absolute: !!/lib/systemd/systemd-networkd
Oct 12 08:11:38 lynx systemd[1]: /lib/systemd/system/systemd-networkd.service:23: Executable path is not absolute: !!/lib/systemd/systemd-networkd


Looking in /lib/systemd/system/systemd-networkd.service for Exec I find:

root@lynx:/root(90)# grep -U3 ExecStart /lib/systemd/system/systemd-networkd.service
Type=notify
Restart=on-failure
RestartSec=0
ExecStart=!!/lib/systemd/systemd-networkd
WatchdogSec=3min
User=systemd-network
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW


Are the two exclamation marks in the ExecStart line intended?
Comment 1 Juergen Rose 2017-10-12 12:20:20 UTC 
After deleting the exclamation marks in /lib/systemd/system/systemd-networkd.service, performing 'systemctl daemon-reload' and 'systemctl restart systemd-networkd' 'systemctl status systemd-networkd' now reports:

● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-10-12 14:14:11 CEST; 5s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 16493 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-networkd.service
           └─16493 /lib/systemd/systemd-networkd

Oct 12 14:14:11 lynx systemd-networkd[16493]: wlan0: Failed to save link data to /run/systemd/netif/links/4: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: eth0: Failed to save link data to /run/systemd/netif/links/3: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: lo: Failed to save link data to /run/systemd/netif/links/1: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: sit0: Failed to save link data to /run/systemd/netif/links/2: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: wlan0: Failed to save link data to /run/systemd/netif/links/4: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: eth0: Failed to save link data to /run/systemd/netif/links/3: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: lo: Failed to save link data to /run/systemd/netif/links/1: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: sit0: Failed to save link data to /run/systemd/netif/links/2: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: wlan0: Failed to save link data to /run/systemd/netif/links/4: Read-only file system
Oct 12 14:14:11 lynx systemd-networkd[16493]: eth0: Failed to save link data to /run/systemd/netif/links/3: Read-only file system
Comment 2 Juergen Rose 2017-10-12 13:10:51 UTC 
After downgrading to systemd-234-r4 the network works again.
Comment 3 Mike Gilbert gentoo-dev 2017-10-12 14:47:25 UTC 
You need to run systemctl daemon-reexec, or reboot your system to restart systemd[1].
Comment 4 Juergen Rose 2017-10-12 21:43:13 UTC 
(In reply to Mike Gilbert from comment #3)
> You need to run systemctl daemon-reexec, or reboot your system to restart
> systemd[1].

Thanks, works now also with systemd-235.