wifi-menu fails because the control process exited with error code.

lambdaislove · 2016-09-26 20:21:38

throughout this I will replace my router's ssid with the string "<ssid>" because it's actual name gives away my location and other information about me. I've also changed my username to <uname>.

When I run wifi-menu the first thing it says is

Could not read interface p2p-dev-wlp4s0 flags: No such device

however p2p-dev-wlp4s0 is not an interface that I recognize

then after I select the network I want I get the following error message

Job for netctl@wlp4s0\x2d<ssid>.service failed because the control process exited with error code.
See "systemctl status "netctl@wlp4s0\\x2d<ssid>.service"" and "journalctl -xe" for details.

So I run journalctl -xe and I get the following relevant information

Sep 26 14:51:50 lambda-is-love sudo[1712]:     <uname> : TTY=pts/0 ; PWD=/home/<uname> ; USER=root ; COMMAND=/usr/bin/wifi-menu
Sep 26 14:51:50 lambda-is-love sudo[1712]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 26 14:51:55 lambda-is-love systemd[1]: Starting Networking for netctl profile wlp4s0-<ssid>...
-- Subject: Unit netctl@wlp4s0\x2d<ssid>.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp4s0\x2d<ssid>.service has begun starting up.
Sep 26 14:51:55 lambda-is-love network[1772]: Starting network profile 'wlp4s0-<ssid>'...
Sep 26 14:51:55 lambda-is-love network[1772]: Line 5: Invalid passphrase length 0 (expected: 8..63) '"'.
Sep 26 14:51:55 lambda-is-love network[1772]: Line 5: failed to parse psk '""'.
Sep 26 14:51:55 lambda-is-love network[1772]: Line 7: failed to parse network block.
Sep 26 14:51:55 lambda-is-love network[1772]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp4s0.conf'.
Sep 26 14:51:56 lambda-is-love network[1772]: The WPA supplicant did not start for interface 'wlp4s0'
Sep 26 14:51:56 lambda-is-love network[1772]: Failed to bring the network up for profile 'wlp4s0-<ssid>'
Sep 26 14:51:56 lambda-is-love systemd[1]: netctl@wlp4s0\x2d<ssid>.service: Main process exited, code=exited, status=1/FAILURE
Sep 26 14:51:56 lambda-is-love systemd[1]: Failed to start Networking for netctl profile wlp4s0-<ssid>.
-- Subject: Unit netctl@wlp4s0\x2d<ssid>.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp4s0\x2d<ssid>.service has failed.
-- 
-- The result is failed.

when I run systemctl status "netctl@wlp4s0\\x2d<ssid>.service" I get the following

netctl@wlp4s0\x2d<ssid>.service - Networking for netctl profile wlp4s0-<ssid>
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2016-09-26 15:05:22 CDT; 13s ago
     Docs: man:netctl.profile(5)
  Process: 1904 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 1904 (code=exited, status=1/FAILURE)

Sep 26 15:05:21 lambda-is-love network[1904]: Line 5: Invalid passphrase length 0 (expected: 8..63) '"'.
Sep 26 15:05:21 lambda-is-love network[1904]: Line 5: failed to parse psk '""'.
Sep 26 15:05:21 lambda-is-love network[1904]: Line 7: failed to parse network block.
Sep 26 15:05:21 lambda-is-love network[1904]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp4s0.conf'.
Sep 26 15:05:22 lambda-is-love network[1904]: The WPA supplicant did not start for interface 'wlp4s0'
Sep 26 15:05:22 lambda-is-love network[1904]: Failed to bring the network up for profile 'wlp4s0-<ssid>'
Sep 26 15:05:22 lambda-is-love systemd[1]: netctl@wlp4s0\x2d<ssid>.service: Main process exited, code=exited, status=1/FAILURE
Sep 26 15:05:22 lambda-is-love systemd[1]: Failed to start Networking for netctl profile wlp4s0-<ssid>.
Sep 26 15:05:22 lambda-is-love systemd[1]: netctl@wlp4s0\x2d<ssid>.service: Unit entered failed state.
Sep 26 15:05:22 lambda-is-love systemd[1]: netctl@wlp4s0\x2d<ssid>.service: Failed with result 'exit-code'.

I googled some of these issues and the wikie has the following work around/kludge that I tried: https://wiki.archlinux.org/index.php/ne … ice_failed. Mine was down so I did number to

so my current file looks like this (after installing dhclient of course):

Description='Automatically generated profile by wifi-menu'
Interface=wlp4s0
Connection=wireless
Security=wpa
ESSID=<ssid>
IP=dhcp
DHCPClient='dhclient'
ForceConnect=yes

doing this did not change the above output.

I made it though all of the checks without doing anything in the "device drivers" part of the following wiki link: https://wiki.archlinux.org/index.php/Wi … figuration
And then went to automatic wifi setup with out looking at manual setup

How do I resolve this issue? Also please inform me of anything information you would like to have.

Head_on_a_Stick · 2016-09-26 20:44:21

Are there any conflicting or broken systemd unit files?

ls -lR /etc/systemd/system

Any dangling symlinks should be deleted manually.

There should only one one networking .service enabled per interface.

Last edited by Head_on_a_Stick (2016-09-26 20:45:09)

lambdaislove · 2016-09-26 20:54:40

I get the following output which appears to me to indicate that I have nothing conflicting with it

/etc/systemd/system:
total 8
lrwxrwxrwx 1 root root   35 Sep 26 13:07 display-manager.service -> /usr/lib/systemd/system/gdm.service
drwxr-xr-x 2 root root 4096 Sep 26 11:57 getty.target.wants
drwxr-xr-x 2 root root 4096 Sep 26 11:57 multi-user.target.wants

/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Sep 26 11:57 getty@tty1.service -> /usr/lib/systemd/system/getty@.service

/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Sep 26 11:57 remote-fs.target -> /usr/lib/systemd/system/remote-fs.targe

Head_on_a_Stick · 2016-09-27 21:39:58

Can you connect manually?

https://wiki.archlinux.org/index.php/Wi … nual_setup

lambdaislove · 2016-09-27 22:20:28

No but I was able to connect with connman finally. There were some other variables going on here as well that I didn't report on. I was trying to connect to an enterprise WPA connection which connman also has trouble with. I never quite got netctl working but it's possible that it was just an issue with enterprise WPA. I also had to download a certificate to connect to my institution's wifi. At home connman worked without hitch. I don't know if this constitutes a solution mind you, just an acceptable work around for me.

I'll try connecting manually when I get home to see if I can solve this issue independent of that variable. Hopefully someone with my same problem trying to use netctl can do something other than just use connman.

Arch Linux

#1 2016-09-26 20:21:38

wifi-menu fails because the control process exited with error code.

#2 2016-09-26 20:44:21

Re: wifi-menu fails because the control process exited with error code.

#3 2016-09-26 20:54:40

Re: wifi-menu fails because the control process exited with error code.

#4 2016-09-27 21:39:58

Re: wifi-menu fails because the control process exited with error code.

#5 2016-09-27 22:20:28

Re: wifi-menu fails because the control process exited with error code.

Board footer