You are not logged in.
Hello everyone,
When I boot my Wi-Fi does not work. That's because wpa_supplicant.service has not loaded correct.
Systemctl status wpa_supplicant.service gives this output:
wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled)
Active: failed (Result: exit-code) since Mi 2013-12-18 14:17:20 CET; 53min ago
Process: 1793 ExecStart=/usr/sbin/wpa_supplicant -u (code=exited, status=203/EXEC)
Main PID: 1793 (code=exited, status=203/EXEC)
CGroup: /system.slice/wpa_supplicant.service
Now I see that wpa_supplicant -u exited with Status 203. If i now open a Terminal, login as root and execute
wpa_supplicant -u
everything works fine.
Now I don't know where to look next for my problem (Is it a DBUS fault? Or Systemd? Or wpa_supplicant? Or NetworkManager???)
I'm using NetworkManager with Gnome 3.10.
Thanks in advance
Last edited by remggo (2013-12-18 18:44:46)
Offline
Did you try following the steps in
to diagnose the problem further?
Last edited by captaincurrie (2013-12-18 17:24:35)
Offline
$systemctl --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
dhcpcd@wlp2s0.service loaded failed failed dhcpcd on wlp2s0
wpa_supplicant.service loaded failed failed WPA supplicant
So apperently dhcpcd also failed. Status dhcpcd:
dhcpcd@wlp2s0.service - dhcpcd on wlp2s0
Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
Active: failed (Result: exit-code) since Mi 2013-12-18 14:06:59 CET; 4h 30min ago
Process: 346 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)
Wpa_supplicant status:
wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled)
Active: failed (Result: exit-code) since Mi 2013-12-18 14:17:20 CET; 4h 24min ago
Process: 1793 ExecStart=/usr/sbin/wpa_supplicant -u (code=exited, status=203/EXEC)
Main PID: 1793 (code=exited, status=203/EXEC)
CGroup: /system.slice/wpa_supplicant.service
When I run journalctl it can't find any entry with dhcpcd or wpa_supplicant in it
Last edited by remggo (2013-12-18 17:42:37)
Offline
Of course dhcpcd will fail if wpa_supplicant hasn't connected. I was going to check what exit code 203 means, but the upstream source for wpa_supplicant is down and the source can't currently be obtained. I suspect it will be due to the interface not yet being up, or perahps not even yet being named by udev if you have a fairly fast boot time. The latter would be fixed by using the wpa_supplicant@.service instead of the "regular" version.
Last edited by Trilby (2013-12-18 18:11:06)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I figured it out. After looking at this
Process: 1793 ExecStart=/usr/sbin/wpa_supplicant -u (code=exited, status=203/EXEC)
line, I realized that wpa_supplicant is not in /usr/sbin/ but in /usr/bin --> Changed that line in
/usr/lib/systemd/system/wpa_supplicant.service
and everything is back to normal
Thanks for your help
Offline
remggo, that may be indicative of deeper issues. /usr/sbin/ should be a symlink to /usr/bin/ and calling /usr/sbin/wpa_supplicant should work just fine.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline