[SOLVED] Job for netctl@wifi0\x2d...service failed

jakhead · 2013-10-06 06:12:29

I'm really not very familiar with networking on Arch, but here goes...

For the longest time, I was using wpa_supplicant to connect to AP's:

wpa_supplicant -B -i wifi0 -c <(wpa_passphrase SSID PSK)

Until I discovered wifi-menu. That worked fine for quite a while, until the other day when I shutdown my laptop while connected to my school's AP. Now connecting to any other AP via wifi-menu returns:

Job for netctl@wifi0\x2dFirefly.service failed. See 'systemctl status netctl@\x2dFirefly.service' and 'journal -xn' for details.

(Firefly is my home SSID)

Appropriately, systemctl status and journalctl follow:

systemctl status netctl@\x2dFirefly.service

netctl@wifi0x2dFirefly.service - Networking for netctl profile wifi0x2dFirefly
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

journalctl -xn

-- Logs begin at Fri 2013-07-19 02:49:30 CDT, end at Sun 2013-10-06 00:56:43 CDT. --
Oct 06 00:56:36 river network[2465]: DHCP IP lease attempt failed on interface 'wifi0'
Oct 06 00:56:36 river kernel: wifi0: deauthenticating from 48:f8:b3:2a:6d:e3 by local choice (reason=3)
Oct 06 00:56:36 river kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 06 00:56:36 river network[2465]: Failed to bring the network up for profile 'wifi0-Firefly'
Oct 06 00:56:36 river systemd[1]: netctl@wifi0\x2dFirefly.service: main process exited, code=exited, status=1/FAILURE
Oct 06 00:56:36 river systemd[1]: Failed to start Networking for netctl profile wifi0-Firefly.
-- Subject: Unit netctl@wifi0\x2dFirefly.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit netctl@wifi0\x2dFirefly.service has failed.
-- 
-- The result is failed.
Oct 06 00:56:36 river systemd[1]: Unit netctl@wifi0\x2dFirefly.service entered failed state.
Oct 06 00:56:36 river sudo[2382]: pam_unix(sudo:session): session closed for user root
Oct 06 00:56:43 river sudo[2661]: hexx : TTY=tty1 ; PWD=/home/hexx ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Oct 06 00:56:43 river sudo[2661]: pam_unix(sudo:session): session opened for user root by hexx(uid=0)

I'm not really sure where to go from here. I see that for some reason dhcp is failing. If I try to go back to using wpa_supplicant I get:

wpa_supplicant -B -i wifi0 -c <(wpa_passphrase Firefly PSK)

Successfully initialized wpa_supplicant
Failed to open config file '/proc/self/fd/11', error: No such file or directory
Failed to read or parse configuration '/proc/self/fd/11'.

However, like I said above, this is only a problem when I'm not on my school's AP. wifi-menu successfully negotiates a connection when I'm on campus.

Any thoughts/help appreciated. Let me know if I need to post more details.

Last edited by jakhead (2013-10-06 19:04:12)

Raynman · 2013-10-06 08:45:00

Unless this is a known bug or something, you probably need to provide some more info. The real status of the systemd service might be a start. The status you posted is for some non-existent profile, because the backslash is an escape character for the shell; to pass that backslash along to systemctl, you need to escape it (with another backslash) or enclose the unit name in quotes. This is especially clear when you look at the description, where the \x2d would be decoded back to a hyphen, but now it says "Networking for netctl profile wifi0x2dFirefly".

What might also be helpful are the lines before the first in the `journalctl -xn` output that says "dhcp lease attempt failed" (but maybe these also show up in the status output). Use something like

# journalctl -u 'netctl@wifi0\x2dFirefly.service'

(you can add -b to limit it to the current boot).

And because you make it sound like shutting down with the active school profile ruined things, have you been able to find any left-over files that might conflict with netctl/wpa_supplicant/dhcpcd? Hard to say what it would be exactly (more so since I'm not that familiar with netctl) ... netctl@school.service permanently enabled and now conflicting with others?

jakhead · 2013-10-06 17:46:57

Thanks for the help!

Escaping the backslash produces:

systemctl status netctl@wifi0\\x2dFirefly.service

netctl@wifi0\x2dFirefly.service - Networking for netctl profile wifi0-Firefly
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Sun 2013-10-06 11:53:07 CDT; 3min 18s ago
     Docs: man:netctl.profile(5)
  Process: 1635 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 1635 (code=exited, status=1/FAILURE)

Oct 06 11:52:56 river dhcpcd[1754]: wifi0: rebinding lease of 192.168.2.7
Oct 06 11:53:01 river dhcpcd[1754]: wifi0: soliciting a DHCP lease
Oct 06 11:53:02 river dhcpcd[1754]: wifi0: offered 192.168.1.113 from 192.168.1.1
Oct 06 11:53:06 river dhcpcd[1754]: timed out
Oct 06 11:53:06 river dhcpcd[1754]: exited
Oct 06 11:53:06 river network[1635]: DHCP IP lease attempt failed on interface 'wifi0'
Oct 06 11:53:07 river network[1635]: Failed to bring the network up for profile 'wifi0-Firefly'
Oct 06 11:53:07 river systemd[1]: netctl@wifi0\x2dFirefly.service: main process exited, code=exited, status=1/FAILURE
Oct 06 11:53:07 river systemd[1]: Failed to start Networking for netctl profile wifi0-Firefly.
Oct 06 11:53:07 river systemd[1]: Unit netctl@wifi0\x2dFirefly.service entered failed state.

journalctl -u didn't produce anything useful, but from the above I guess I need to extend the timeout for dhcpcd. I'm not sure where to change that. I didn't see anything relevant in /etc/dhcpcd.conf.

Raynman · 2013-10-06 17:59:57

dhcpcd has a command-line option for the timeout; `man netctl.profile` tells me there's a DhcpcdOptions= variable.

WonderWoofy · 2013-10-06 18:48:33

jakhead wrote:

wpa_supplicant -B -i wifi0 -c <(wpa_passphrase Firefly PSK)
Successfully initialized wpa_supplicant
Failed to open config file '/proc/self/fd/11', error: No such file or directory
Failed to read or parse configuration '/proc/self/fd/11'.

I don't think this has anything to do with your problem, but I just want to point out that although I have seen somewhere in the wiki where this kind of command substitution is given as an example, I have never actually gotten this to work. So if you continue to try to debug by using wpa_supplicant directly, you might want to use shell redirection of wpa_passphrase to a temporary file (might I recommend something in /tmp so it doesn't persist between reboots) and then run wpa_supplicant using that temporary config (so with wpa_supplicant… -c /tmp/wpa-temp.conf for example).

Also I find it kind of curious that it is trying to rebind to 192.168.2.7 then being offered 192.168.1.113. But maybe simply increasing the timeout of dhcpcd in your netctl profile might help?

jakhead · 2013-10-06 19:03:44

Solved! I will update the subject.

Thank you both Raynman and WonderWoofy!

@WonderWoofy, thanks for the tip about wpa_passphrase. Also, 192.168.2.7 was from my campus AP.

@Raynman Thanks for the suggestion!

For anyone else having similar issues, I used the TimeoutDHCP= option in my netctl profile as suggested by bohoomil
here

Explicitly:

hexx@river# echo 'TimeoutDHCP=20' >> /etc/netctl/wifi0-Firefly

Arch Linux

#1 2013-10-06 06:12:29

[SOLVED] Job for netctl@wifi0\x2d...service failed

#2 2013-10-06 08:45:00

Re: [SOLVED] Job for netctl@wifi0\x2d...service failed

#3 2013-10-06 17:46:57

Re: [SOLVED] Job for netctl@wifi0\x2d...service failed

#4 2013-10-06 17:59:57

Re: [SOLVED] Job for netctl@wifi0\x2d...service failed

#5 2013-10-06 18:48:33

Re: [SOLVED] Job for netctl@wifi0\x2d...service failed

#6 2013-10-06 19:03:44

Re: [SOLVED] Job for netctl@wifi0\x2d...service failed

Board footer