Setup requirements for 'netctl-auto-resume' as a service

Cbhihe · 2017-10-09 22:03:16

[4.13.4-1-ARCH]

Hi, I have installed the AUR package 'netctl-auto-resume'. It is described as helping to recover WiFi connectivity when arch lx goes to hibernation (suspend-to-disk) or in suspend (suspend-to-RAM) and resumes... I put the question that follows to the package's AUR page to no avail. Apparently the current AUR page contact person is not the maintainer.

I have 'netctl-auto' and 'netctl-ifplugd' enabled, and started. Everything works as expected there.
Do I need to have power management and in particular suspend and hibernation covered for this to work ?
At present neither GUI nor power-mgt packages are installed. The box is a bare bone console only (with 'tmux', vim and bash configured.)

After a successful clone-install of 'netctl-auto-resume' from GitHub I find that:

$ sudo systemctl enable netctl-auto-resume@wifi0.service
Created symlink /etc/systemd/system/sleep.target.wants/netctl-auto-resume@wifi0.service -> /etc/systemd/system/netctl-auto-resume@.service
$ sudo systemctl start netctl-auto-resume@wifi0.service
A dependency job for netctl-auto-resume@wifi0.service failed. See 'journalctl -xe' for details.
$ sudo journalctl -xe | grep netctl-auto-resume
Oct 09 23:46:18 HOSTNAME sudo[3429]:     USERNAME : TTY=pts/0 ; PWD=/etc/systemd/system ; USER=root ; COMMAND=/usr/bin/systemctl start netctl-auto-resume@wifi0.service
-- Subject: Unit netctl-auto-resume@wifi0.service has failed
-- Unit netctl-auto-resume@wifi0.service has failed.
Oct 09 23:46:18  HOSTNAME systemd[1]: netctl-auto-resume@wifi0.service: Job netctl-auto-resume@wifi0.service/start failed with result 'dependency'.

In the ends that gives me an enabled but dead service, while

$ systemctl status
State: running
Jobs: 0 queued
Failed: 0 units
...

I am not sure which "dependency job" this is about. Plus I may be working out-of-sequence and ahead of a proper power management config...

A nudge in the right direction would be great.
Cheers.

Last edited by Cbhihe (2017-10-10 14:22:50)

loqs · 2017-10-09 22:31:16

What is the output of

# journalctl -u netctl-auto-resume@wifi0.service

As the output from the journal is not very useful after being grepped

Cbhihe · 2017-10-10 12:32:24

Thanks @loqs.

The AUR page only lists 'netctl' as dependency. I run the latest available version from the Arch official repo, which came with the core group install: /usr/bin/netctl v 1.13-2.
And just to be sure, I followed this Arch Wiki doc.

$ journalctl -u netctl-auto-resume@wifi0.service
-- Logs begin at Sat 2017-09-30 19:38:19 CEST, end at Tue 2017-10-10 14:15:57 CEST. --
Oct 08 14:20:01  HOSTNAME systemd[1]: /etc/systemd/system/netctl-auto-resume@.service:4: Failed to add dependency on sys-subsystem-net-devices-wifi0.devices, ignoring: Invalid argument
Oct 08 14:20:01  HOSTNAME systemd[1]: Dependency failed for restart netctl-auto on resume..
Oct 08 14:20:01  HOSTNAME systemd[1]: netctl-auto-resume@wifi0.service: Job netctl-auto-resume@wifi0.service/start failed with result 'dependency'.
Oct 08 14:21:39  HOSTNAME systemd[1]: /etc/systemd/system/netctl-auto-resume@.service:4: Failed to add dependency on sys-subsystem-net-devices-wifi0.devices, ignoring: Invalid argument
Oct 08 14:21:39  HOSTNAM Esystemd[1]: Starting restart netctl-auto on resume....
Oct 08 14:21:41  HOSTNAME systemd[1]: Started restart netctl-auto on resume..
Oct 08 14:24:11  HOSTNAME systemd[1]: /etc/systemd/system/netctl-auto-resume@.service:4: Failed to add dependency on sys-subsystem-net-devices-wifi0.devices, ignoring: Invalid argument
Oct 08 14:30:32  HOSTNAME systemd[1]: Starting restart netctl-auto on resume....
Oct 08 14:30:34  HOSTNAME systemd[1]: Started restart netctl-auto on resume..
Oct 08 14:31:34  HOSTNAME systemd[1]: Starting restart netctl-auto on resume....
Oct 08 14:31:37  HOSTNAME systemd[1]: Started restart netctl-auto on resume..
-- Reboot --
Oct 08 14:38:04  HOSTNAME systemd[1]: Starting restart netctl-auto on resume....
Oct 08 14:38:06  HOSTNAME systemd[1]: Started restart netctl-auto on resume..
-- Reboot --
Oct 09 22:43:06  HOSTNAME systemd[1]: Dependency failed for restart netctl-auto on resume..
Oct 09 22:43:06  HOSTNAME systemd[1]: netctl-auto-resume@wifi0.service: Job netctl-auto-resume@wifi0.service/start failed with result 'dependency'.
Oct 09 23:46:18  HOSTNAME systemd[1]: Dependency failed for restart netctl-auto on resume..
Oct 09 23:46:18  HOSTNAM Esystemd[1]: netctl-auto-resume@wifi0.service: Job netctl-auto-resume@wifi0.service/start failed with result 'dependency'.

... that leaves me still in the dark as to which dependency ...

EDIT:
Looking at '/etc/systemd/system/netctl-auto-resume@.service' :

$ cat /etc/systemd/system/netctl-auto-resume@.service
[Unit]
Description=restart netctl-auto on resume.
Requisite=netctl-auto@%i.service
After=sleep.target sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl restart netctl-auto@%i.service
[Install]
WantedBy=sleep.target
$

.... I come to realize that the dependency job might well be related to 'sleep.target' (first on the 'After=...' line in above profile.)

Last edited by Cbhihe (2017-10-10 14:32:26)

cfr · 2017-10-11 01:12:14

Do you actually need this? Does the laptop have problems resuming wifi after suspend or hibernate? I don't use hibernation, but I've never had any problems after suspending - at least, none which weren't due to buggy network behaviour, as far as I can tell.

Arch Linux

#1 2017-10-09 22:03:16

Setup requirements for 'netctl-auto-resume' as a service

#2 2017-10-09 22:31:16

Re: Setup requirements for 'netctl-auto-resume' as a service

#3 2017-10-10 12:32:24

Re: Setup requirements for 'netctl-auto-resume' as a service

#4 2017-10-11 01:12:14

Re: Setup requirements for 'netctl-auto-resume' as a service

Board footer