| Summary: | sys-apps/systemd-234-r2: systemd-networkd.service requires After=dbus.service | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bernd Feige <Bernd.Feige> |
| Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | gentoo, jstein, sbraz |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://github.com/systemd/systemd/issues/6618 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
That does not sound right. Please report the issue upstream. (In reply to Mike Gilbert from comment #1) > That does not sound right. Please report the issue upstream. I already found it on the bug tracker - See URL (https://github.com/systemd/systemd/issues/6435) Does adding "After=dbus.socket" also resolve the issue? To clarify, please replace After=dbus.service with After=dbus.socket and re-test. Yes, After=dbus.socket is sufficient too! The upstream issue you found was unrelated to this bug. Reported a new issue upstream. Could someone test the changes from this pull request? https://github.com/systemd/systemd/pull/6659 Thanks for reporting upstream! I can confirm that the fix in pull request https://github.com/systemd/systemd/pull/6659 works (lets systemd-networkd start rather than fail on my systems). As I see, the fix extends an internal retry loop to also include the error occurring when dbus is not yet up. I cannot imagine that this solution is really what the systemd authors intend, as it hides the information on the condition for which a service is waiting from the system. As I understand it, it would be cleaner to add dbus.socket as a dependency. Then this dependency is explicit and systemd-networkd may simply fail if it isn't met, just as before. I'll post the same on the pull request now. (In reply to Bernd Feige from comment #9) Well my musings are obsolete - Poettering just merged the pull request, so this appears to adhere to policy... Should be resolved in 235. I am still facing this issue on one machine with sys-apps/systemd-246-r1 But it does also not seem to wait after connecting to dbus failed and rapidly tries 5 times and ultimately fails: -- Reboot -- Okt 11 23:06:10 heisenberg systemd[1]: Starting Network Service... Okt 11 23:06:10 heisenberg systemd-networkd[1228]: Failed to connect to bus: Permission denied Okt 11 23:06:10 heisenberg systemd-networkd[1228]: Could not connect to bus: Permission denied Okt 11 23:06:10 heisenberg systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Okt 11 23:06:10 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:10 heisenberg systemd[1]: Failed to start Network Service. Okt 11 23:06:10 heisenberg systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. Okt 11 23:06:10 heisenberg systemd[1]: Stopped Network Service. Okt 11 23:06:10 heisenberg systemd[1]: Starting Network Service... Okt 11 23:06:11 heisenberg systemd-networkd[1259]: Failed to connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd-networkd[1259]: Could not connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:11 heisenberg systemd[1]: Failed to start Network Service. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 2. Okt 11 23:06:11 heisenberg systemd[1]: Stopped Network Service. Okt 11 23:06:11 heisenberg systemd[1]: Starting Network Service... Okt 11 23:06:11 heisenberg systemd-networkd[1268]: Failed to connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd-networkd[1268]: Could not connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:11 heisenberg systemd[1]: Failed to start Network Service. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 3. Okt 11 23:06:11 heisenberg systemd[1]: Stopped Network Service. Okt 11 23:06:11 heisenberg systemd[1]: Starting Network Service... Okt 11 23:06:11 heisenberg systemd-networkd[1270]: Failed to connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd-networkd[1270]: Could not connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:11 heisenberg systemd[1]: Failed to start Network Service. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4. Okt 11 23:06:11 heisenberg systemd[1]: Stopped Network Service. Okt 11 23:06:11 heisenberg systemd[1]: Starting Network Service... Okt 11 23:06:11 heisenberg systemd-networkd[1292]: Failed to connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd-networkd[1292]: Could not connect to bus: Permission denied Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:11 heisenberg systemd[1]: Failed to start Network Service. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Okt 11 23:06:11 heisenberg systemd[1]: Stopped Network Service. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Start request repeated too quickly. Okt 11 23:06:11 heisenberg systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Okt 11 23:06:11 heisenberg systemd[1]: Failed to start Network Service. When adding After=dbus.socket the issue disappears. |
After the systemd-234 upgrade, systemd-networkd ("enabled" in multi-user.target.wants) would fail during system startup: systemd-networkd[132]: Could not connect to bus: Connection refused leading to the service failing with "Failed with result 'protocol'" This was also on a completely empty /etc/systemd/system directory, enabling only systemd-networkd. It works fine if "dbus.service" is added to "After=" in systemd-networkd.service.