You are not logged in.
- Topics: Active | Unanswered
#1 2019-12-08 02:19:18
- atomikegg
- Member
- Registered: 2019-08-14
- Posts: 99
[Solved] Can't restart netctl-auto on resume
pure arch, updated.
wiki says:
Sometimes netctl-auto fails to reconnect when the system resumes from suspend, hibernate or hybrid-sleep. An easy solution is to restart the service for netctl-auto.
https://wiki.archlinux.org/index.php/Ne … _on_resume
But when i try that, i get an error.
# systemctl start netctl-auto@wlp0s26f7u2.service
Job for netctl-auto@wlp0s26f7u2.service failed because the control process exited with error code.
See "systemctl status netctl-auto@wlp0s26f7u2.service" and "journalctl -xe" for details.
[root@myegg johny]# systemctl status netctl-auto@wlp0s26f7u2.service
* netctl-auto@wlp0s26f7u2.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2019-12-07 18:14:19 PST; 3s ago
Docs: man:netctl.special(7)
Process: 2335 ExecStart=/usr/bin/netctl-auto start wlp0s26f7u2 (code=exited, status=1/FAILURE)
Process: 2337 ExecStopPost=/usr/bin/netctl-auto clean wlp0s26f7u2 (code=exited, status=0/SUCCESS)
Dec 07 18:14:19 myegg systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Dec 07 18:14:19 myegg netctl-auto[2335]: The interface 'wlp0s26f7u2' is already up
Dec 07 18:14:19 myegg systemd[1]: netctl-auto@wlp0s26f7u2.service: Control process exited, code=exited, status=1/FAILURE
Dec 07 18:14:19 myegg systemd[1]: netctl-auto@wlp0s26f7u2.service: Failed with result 'exit-code'.
Dec 07 18:14:19 myegg systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
[root@myegg johny]# journalctl -xe
--
-- A start job for unit netctl-auto@wlp0s26f7u2.service has finished with a failure.
--
-- The job identifier is 1531 and the job result is failed.
Dec 07 18:13:44 myegg kernel: audit: type=1130 audit(1575771224.353:91): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp0s26f7u2 comm="s>
Dec 07 18:13:44 myegg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp0s26f7u2 comm="systemd" exe="/usr/lib/syste>
Dec 07 18:14:19 myegg systemd[1]: Starting Automatic wireless network connection using netctl profiles...
-- Subject: A start job for unit netctl-auto@wlp0s26f7u2.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit netctl-auto@wlp0s26f7u2.service has begun execution.
--
-- The job identifier is 1601.
Dec 07 18:14:19 myegg netctl-auto[2335]: The interface 'wlp0s26f7u2' is already up
Dec 07 18:14:19 myegg systemd[1]: netctl-auto@wlp0s26f7u2.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- An ExecStart= process belonging to unit netctl-auto@wlp0s26f7u2.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Dec 07 18:14:19 myegg systemd[1]: netctl-auto@wlp0s26f7u2.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit netctl-auto@wlp0s26f7u2.service has entered the 'failed' state with result 'exit-code'.
Dec 07 18:14:19 myegg systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
-- Subject: A start job for unit netctl-auto@wlp0s26f7u2.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit netctl-auto@wlp0s26f7u2.service has finished with a failure.
--
-- The job identifier is 1601 and the job result is failed.
Dec 07 18:14:19 myegg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp0s26f7u2 comm="systemd" exe="/usr/lib/syste>
Dec 07 18:14:19 myegg kernel: audit: type=1130 audit(1575771259.485:92): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl-auto@wlp0s26f7u2 comm="s>
# systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
dbus.service loaded active running D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
kmod-static-nodes.service loaded active exited Create list of static device nodes for the current kernel
ldconfig.service loaded active exited Rebuild Dynamic Linker Cache
lvm2-lvmetad.service loaded active running LVM2 metadata daemon
lvm2-monitor.service loaded active exited Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
* netctl-auto@wlp0s26f7u2.service loaded failed failed Automatic wireless network connection using netctl profiles
netctl@wlp0s26f7u2\x2dORBI64.service loaded active exited Networking for netctl profile wlp0s26f7u2-ORBI64
polkit.service loaded active running Authorization Manager
systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_video0
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_backlight
systemd-journal-catalog-update.service loaded active exited Rebuild Journal Catalog
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-done.service loaded active exited Update is Completed
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
udisks2.service loaded active running Disk Manager
user-runtime-dir@1000.service loaded active exited User Runtime Directory /run/user/1000
user@1000.service loaded active running User Manager for UID 1000
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
30 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.Last edited by atomikegg (2019-12-08 03:34:00)
Offline
#2 2019-12-08 02:36:08
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: [Solved] Can't restart netctl-auto on resume
That is hardly surprising...
things are ok now. I'm using wpa_supplicant, dhcpcd, wifi-menu, netctl, and netctl-auto
Rather than continuing to spam the boards with your "issues", perhaps you could just read the wiki:
There are many solutions to choose from, but remember that all of them are mutually exclusive; you should not run two daemons simultaneously.
https://wiki.archlinux.org/index.php/Ne … k_managers
Last edited by jasonwryan (2019-12-08 02:38:52)
Offline
#3 2019-12-08 03:22:37
- atomikegg
- Member
- Registered: 2019-08-14
- Posts: 99
Re: [Solved] Can't restart netctl-auto on resume
Please stop being disrespectful. The forum rules specify that we're supposed to treat each other with respect.
Respect other users. Arch Linux is a respectful, inclusive community. Anti-social or offensive behaviour will not be tolerated. Simply put, treat others as you would be treated.
https://wiki.archlinux.org/index.php/Co … ct#Respect
i'm not trying to 'spam', i'm a beginner and still learning.
obviously i read the wiki, since i quoted it.
i understand that we can't run multiple daemons at the same time, since I read that in the netctl page.
Warning: Do not enable concurrent, conflicting network services. Use systemctl --type=service to ensure that no other network service is running before enabling a netctl profile/service.
https://wiki.archlinux.org/index.php/Ne … stallation
i carefully removed any other network daemons, as far as i can tell as a Newb. i'm not running ConnMan, NetworkManager, wicd, or systemd-networkd.
Since you quoted my other post about wpa_supplicant, dhcpcd, and wifi-menu, you're implying one of those is the problem (my eventual fix, below, indicates they weren't the problem, so not sure why you mentioned them). Rather, they are all listed as "optional dependencies", to be installed side-by-side with netctl.
Other optional dependencies are shown in the table below.
Feature Dependency
WPA wpa_supplicant
DHCP dhcpcd or dhclient
wifi-menu dialog
PPPoE ppp
The wiki also states
Profiles must use Security=wpa-configsection or Security=wpa to work with netctl-auto rather than Security=wpa-config
i carefully checked my profiles to ensure they are using Security=wpa.
On boot, netctl-auto connect automatically, as expected.
The wiki described a known issue where netctl-auto may not reconnect on resume. Conflicting daemons ISN'T listed as a probable cause.
Your comment doesn't actually provide a helpful explanation. What conflicting daemons am i running? i shared my output above, from `systemctl --type=service` to help find the issue.
i'll try deleting the profiles and recreating, since they were created before i started using netctl-auto.
Last edited by atomikegg (2019-12-08 03:42:54)
Offline
#4 2019-12-08 03:33:35
- atomikegg
- Member
- Registered: 2019-08-14
- Posts: 99
Re: [Solved] Can't restart netctl-auto on resume
i'll try deleting the profiles and recreating, since they were created before i started using netctl-auto.
Bingo. That fixed it. On recreating the profiles with wifi-menu while netctl-auto service is running, netctl-auto manages them properly. They reconnect on resume, as expected.
cheers
Last edited by atomikegg (2019-12-08 03:41:30)
Offline
#5 2019-12-08 03:44:37
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: [Solved] Can't restart netctl-auto on resume
Please stop being disrespectful. The forum rules specify that we're supposed to treat each other with respect.
Respect other users. Arch Linux is a respectful, inclusive community. Anti-social or offensive behaviour will not be tolerated. Simply put, treat others as you would be treated.
https://wiki.archlinux.org/index.php/Co … ct#Respect
Respect is a two-way street. Continuing to expect to be hand held is help vampirism: it erodes the goodwill of the community.
Ask yourself before you open a thread "what am I bringing to Arch?", instead of "what can I get?". The former is respectful, the latter is selfish and that, therefore, is disrespectful.
Offline
#6 2019-12-08 06:57:07
- atomikegg
- Member
- Registered: 2019-08-14
- Posts: 99
Re: [Solved] Can't restart netctl-auto on resume
what am i bringing? I'm a newb. There's not a lot i can bring.
i demonstrated an obvious effort to solve it on my own. i obviously read the wiki, and shared what i believed were the relevant parts.
No one is forcing you to participate. You're just using the forum to treat people badly. If you don't want to help, then just don't.
Edit:
"Respect":
You misrepresent the Forum Rules about respect. The passage i quoted is clearly talking about verbal abuse, not "asking too many questions".
"Bring to arch":
Sharing my pain-points as a newb is exactly how i help arch. If a person of reasonable intelligence reads the wiki and makes their best effort (which i've obviously done) still doesn't achieve expected results, that's a clue that maybe the documentation, or the software, have a gap or weakness.
Which is exactly the problem in this case, apparently. I may be wrong, but based on my experience here, it seems the problem came down to:
netctl profiles created before netctl-auto is enabled will conflict with netctl-auto.
- The wiki makes no mention of this.
- netctl-auto fails to automatically integrate the previous profiles.
Either the wiki should be revised to explain this gotcha, or netctl software should be revised to prevent the problem.
Wiki suggestion:
If netctl-auto software isn't revised, then there are at least two potential user-fixes. The fix that worked for me was:
- Disable the services associated with the old profiles
- Delete the old profile files
- Recreate the profiles with wifi-menu when those networks are in range.
This is my preferred fix. Had the wiki offered the above solution, i wouldn't be here in the forum asking how to fix it.
I assume there's another fix, which involves manually editing various configuration files so that netctl-auto can manage the pre-existing profiles, instead of deleting them. The wiki could also explain how to do that.
Last edited by atomikegg (2019-12-09 12:35:25)
Offline