FS#39544 - [netctl] Pid file error during connection to wifi

Attached to Project: Arch Linux
Opened by Jáchym Barvínek (kamahl) - Wednesday, 19 March 2014, 19:58 GMT
Last edited by Jouke Witteveen (jouke) - Friday, 21 March 2014, 14:07 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I cannot connect to a wpa2 wifi with the new version 1.6 of netctl.
The error message it produces is

chmod: cannot access '/run/dhcpcd-wls1.pid': No such file or directory

There exists a file /run/dhcpcd.pid, though.
Symlinking ln -s /run/dhcpcd.pid /run/dhcpcd-wls1.pid did not help, the symling apparently gets deleted somehow before the error occurs.

Downgrading netctl to 1.4-2 fixed the problem.
This task depends upon

Closed by  Jouke Witteveen (jouke)
Friday, 21 March 2014, 14:07 GMT
Reason for closing:  Not a bug
Additional comments about closing:  netctl can only manage dhcpcd if dhcpcd is not already managed by something else
Comment by Jouke Witteveen (jouke) - Thursday, 20 March 2014, 10:09 GMT
Are there other dhcpcd pid files in /run? Are there any relevant messages in the journal? What debugging messages are generated if you add NETCTL_DEBUG=yes to your profile?
Comment by Johan (zenolijo) - Friday, 21 March 2014, 09:46 GMT
I have had the same issue for some days now on both wpa2-personal (home) and wpa2-enterprise (school) routers, and i can confirm that the only dhcpcd files in /run are dhcpcd.pid and and dhcpcd.sock=

When adding NETCTL_DEBUG, netctl status returns:
DEBUG: wpa_call: wpa_cli -i wlp3s0 -p /run/wpa_supplicant status
DEBUG: wpa_call: wpa_cli -i wlp3s0 -p /run/wpa_supplicant status
sending commands to master dhcpcd process
DEBUG: DEBUG: dhcpcd_start: dhcpcd -4qL -t 30 wlp3s0
chmod: cannot access '/run/dhcpcd-wlp3s0.pid': No such file or directory
DEBUG: wpa_call: wpa_cli -i wlp3s0 -p /run/wpa_supplicant terminate
Failed to bring the network up for profile 'wlp3s0-xxx'
Comment by Jouke Witteveen (jouke) - Friday, 21 March 2014, 11:01 GMT
¿Is a pid file created when you manually run
dhcpcd -4qL -t 30 wlp3s0
Comment by Jouke Witteveen (jouke) - Friday, 21 March 2014, 11:12 GMT
Do you have the dhcpcd service enabled? If so, disable it (or remove dhcp from your netctl profile).
Comment by Jáchym Barvínek (kamahl) - Friday, 21 March 2014, 14:03 GMT
When I run the command dhcpcd -4qL -t 30 wlp3s0, no file in /run is created.

But disabling dhcpcd seems to fix the problem.

Loading...