Arch Linux

hooya

Member

Registered: 2011-10-09

Posts: 99

[SOLVED] Forced to wait 1:30 at every boot due to a job wait service

I've searched around and tried various things regarding masking/enabling/disabling services, but my system was already set up the way most of the troubleshooters describe fixing the issue.

Boot log relevant section:

Aug 14 12:17:45 trenix systemd[1]: Network Manager is not active.
Aug 14 12:17:45 trenix systemd[1]: Dependency failed for Network Manager Wait Online.
Aug 14 12:17:45 trenix systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
Aug 14 12:17:45 trenix systemd[1]: Starting Save/Restore Sound Card State...
Aug 14 12:17:45 trenix systemd[1]: Started Daily rotation of log files.
Aug 14 12:17:45 trenix systemd[1]: Reached target Timers.
Aug 14 12:17:45 trenix systemd[1]: Started Login Service.
Aug 14 12:17:45 trenix systemd[1]: Started Save/Restore Sound Card State.
Aug 14 12:19:14 trenix systemd[1]: sys-subsystem-net-devices-enp9s0.device: Job sys-subsystem-net-devices-enp9s0.device/start timed out.
Aug 14 12:19:14 trenix systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp9s0.device.
Aug 14 12:19:14 trenix systemd[1]: Dependency failed for dhcpcd on enp9s0.
Aug 14 12:19:14 trenix systemd[1]: dhcpcd@enp9s0.service: Job dhcpcd@enp9s0.service/start failed with result 'dependency'.
Aug 14 12:19:14 trenix systemd[1]: sys-subsystem-net-devices-enp9s0.device: Job sys-subsystem-net-devices-enp9s0.device/start failed with result 'timeout'.
Aug 14 12:19:14 trenix systemd[1]: Reached target Network.
Aug 14 12:19:14 trenix systemd[1]: Reached target Network is Online.

The job times out after the "waiting for a start job" for a minute and a half. I don't have any idea what enp9s0 is. This is not a new installation and I have made no hardware or networking changes on this machine, unless a standard -Syyu update did it.

I have tried:

enabling/disabling networkmanager-wait-online.service, which is currently masked after disabling. I can't actually enable it because it's masked.

disable enp9s0.device (it doesn't exist according to netctl)

Help?

Last edited by hooya (2016-08-17 14:47:08)

berbae

Member

From: France

Registered: 2007-02-12

Posts: 1,302

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

Do you have an internet connection? And how do you connect?
enp9s0 is the device name of the network interface, and it seems slow to start for you.

hooya

Member

Registered: 2011-10-09

Posts: 99

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

Yes I have a connection. Dhcpcd, requires no interaction from me at boot. Wired. I posted this from my arch install. I dual boot and windows doesn't lag on opening network connection. Network speeds are perfectly fine. I just don't understand why there is a lag at boot. There hasn't been in the past on the same install.

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

If dhcpcd@enp9s0 times out but you still have a connection, it seems like you must have another service that starts dhcpcd on enp9s0, or you have another network device that's being brought up successfully.

systemctl list-dependencies doesn't seem to be of any use with devices (see edit), so the best I can suggest is that you post the output of
'systemctl list-dependencies --reverse network.target' and
'systemctl list-units'.

Edit: Try 'systemctl list-dependencies --before sys-subsystem-net-devices-enp9s0.device'

Last edited by alphaniner (2016-08-16 20:17:50)

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

hooya

Member

Registered: 2011-10-09

Posts: 99

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

# systemctl list-dependencies --before sys-subsystem-net-devices-enp9s0.device
sys-subsystem-net-devices-enp9s0.device
● └─dhcpcd@enp9s0.service

systemctl enable dhcpcd@enp9s0.service

runs without a hitch, but when I try

systemctl start dhcpcd@enp9s0.service

the command prompt hangs for a while then outputs:

A dependency job for dhcpcd@enp9s0.service failed. See 'journalctl -xe' for details.

journalctl -xe displays the exact same output as in my original post, just run again.

Aug 17 09:22:23 trenix systemd[1]: sys-subsystem-net-devices-enp9s0.device: Job sys-subsystem-net-devices-enp9s0.device/start timed out.
Aug 17 09:22:23 trenix systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp9s0.device.
-- Subject: Unit sys-subsystem-net-devices-enp9s0.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sys-subsystem-net-devices-enp9s0.device has failed.
-- 
-- The result is timeout.
Aug 17 09:22:23 trenix systemd[1]: Dependency failed for dhcpcd on enp9s0.
-- Subject: Unit dhcpcd@enp9s0.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd@enp9s0.service has failed.
-- 
-- The result is dependency.
Aug 17 09:22:23 trenix systemd[1]: dhcpcd@enp9s0.service: Job dhcpcd@enp9s0.service/start failed with result 'dependency'.
Aug 17 09:22:23 trenix systemd[1]: sys-subsystem-net-devices-enp9s0.device: Job sys-subsystem-net-devices-enp9s0.device/start failed with result 'timeout'.

$ systemctl list-dependencies --reverse network.target
network.target
● ├─dhcpcd.service <green dot
● ├─dhcpcd@enp9s0.service << white dot
● ├─NetworkManager.service <<white dot
● ├─systemd-networkd.service <<green dot
● └─wpa_supplicant.service <<green dot

This is interesting though. The output of systemctl list-units gives me references to a similar but not exactly the same device as an ethernet controller:

sys-subsystem-net-devices-enp8s0.device                                                          loaded active plugged   RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (P8 series motherboard)

There is no reference to a n enp9s0.device in that output.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,544

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

Why do you have both dhcpcd and NetworkManager enabled?

hooya

Member

Registered: 2011-10-09

Posts: 99

Re: [SOLVED] Forced to wait 1:30 at every boot due to a job wait service

OK. Solved, at least to my satisfaction.

Running the list-units command basically told me that whatever the "9" device was, I didn't want it active at all, and running the list-dependencies told me the exact service name I was dealing with.

So I tried, as an experiment to disable the enp9s0.service.

systemctl disable dhcpcd@enp9s0.service

Rebooted in 15 seconds to desktop and I'm typing this from a working network connection.

So I have no idea how that service got created in the first place, but it appears to have no reason to exist on my system, so I'll leave it all gone.

Last edited by hooya (2016-08-17 14:47:51)