Arch Linux

rmmonster

Member

Registered: 2014-03-20

Posts: 2

device specific dhcpcd pid file missing?

Hi,

a few days ago I have tried building a working gnunet configuration. At some point all went to hell and my network devices wont work anymore. After a short panic attack I figured that the lan device was still working and I was just to stupid to use netctl correct.

The wlan device was disabled trough the rfkill soft switch, which I didn't know existed, but it worked allright. Today I ran into network problems again. This time at university, where I use the eduroam network. My configuration worked fine in the past and was derived from the linke wiki article.

Today I tried to change the wlan network from my configuration at home to the configuration for university. It didn't worked and I wasn't expecting persistant problems, so I rebooted (old Windows habit). After reboot, I set the network device down, because it comes up in state "up" after boot.

ifconfig <wlan_device>    
wlp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether <mac>  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip link show <wlan_device>
#: <wlan_device>: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether <mac> brd ff:ff:ff:ff:ff:ff

# ip link set <wlan_device> down

which worked fine, as far as I can see.

# ip link show <wlan_device>    
#: <wlan_device>: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether <mac> brd ff:ff:ff:ff:ff:ff

Next I tried to start the eduroam profil with netctl

 # netctl start <wlan_device>-eduroam 

which fails

Job for netctl@<wlan_device>\x2deduroam.service failed. See 'systemctl status netctl@<wlan_device>\x2deduroam.service' and 'journalctl -xn' for details.

with the following logs

# systemctl status netctl@<wlan_device>\x2deduroam.service           :(
netctl@<wlan_device>x2deduroam.service - Networking for netctl profile <wlan_device>x2deduroam
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
     Docs: man:netctl.profile(5)

# journalctl -xn
-- Logs begin at Mon 2014-02-10 17:43:54 CET, end at Thu 2014-03-20 19:25:28 CET. --
Mar 20 19:17:25 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:17:39 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:18:09 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:18:38 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:18:57 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:19:48 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:20:08 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:20:27 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:20:58 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:21:45 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:22:17 <hostname> systemd[1]: Starting system-netctl.slice.
-- Subject: Unit system-netctl.slice has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit system-netctl.slice has begun starting up.
Mar 20 19:22:17 <hostname> systemd[1]: Created slice system-netctl.slice.
-- Subject: Unit system-netctl.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit system-netctl.slice has finished starting up.
--
-- The start-up result is done.
Mar 20 19:22:17 <hostname> systemd[1]: Starting Networking for netctl profile <wlan_device>-eduroam...
-- Subject: Unit netctl@<wlan_device>\x2deduroam.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@<wlan_device>\x2deduroam.service has begun starting up.
Mar 20 19:22:17 <hostname> network[6651]: Starting network profile '<wlan_device>-eduroam'...
Mar 20 19:22:17 <hostname> kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Mar 20 19:22:17 <hostname> kernel: iwlwifi 0000:03:00.0: Radio type=0x2-0x0-0x0
Mar 20 19:22:17 <hostname> kernel: IPv6: ADDRCONF(NETDEV_UP): <wlan_device>: link is not ready
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: authenticate with <mac>
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: send auth to <mac> (try 1/3)
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: authenticated     
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: associate with <mac> (try 1/3)
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: RX AssocResp from <mac> (capab=0x431 status=0 aid=62)
Mar 20 19:22:17 <hostname> kernel: <wlan_device>: associated
Mar 20 19:22:17 <hostname> kernel: IPv6: ADDRCONF(NETDEV_CHANGE): <wlan_device>: link becomes ready
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: carrier acquired
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: IAID 66:bc:f8:c2
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: soliciting an IPv6 router
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: soliciting a DHCP lease
Mar 20 19:22:18 <hostname> dhcpcd[6746]: sending commands to master dhcpcd process
Mar 20 19:22:18 <hostname> dhcpcd[408]: control command: dhcpcd -4qL -t 30 <wlan_device>
Mar 20 19:22:18 <hostname> network[6651]: chmod: cannot access ‘/run/dhcpcd-<wlan_device>.pid’: No such file or directory
Mar 20 19:22:18 <hostname> kernel: <wlan_device>: deauthenticating from <mac> by local choice (reason=3)
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: carrier lost
Mar 20 19:22:18 <hostname> kernel: cfg80211: Calling CRDA for country: DE
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: carrier acquired
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: IAID 66:bc:f8:c2
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: soliciting an IPv6 router
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: soliciting a DHCP lease
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: ipv4_sendrawpacket: Network is down
Mar 20 19:22:18 <hostname> dhcpcd[408]: <wlan_device>: carrier lost
Mar 20 19:22:18 <hostname> network[6651]: Failed to bring the network up for profile '<wlan_device>-eduroam'
Mar 20 19:22:18 <hostname> systemd[1]: netctl@<wlan_device>\x2deduroam.service: main process exited, code=exited, status=1/FAILURE
Mar 20 19:22:18 <hostname> systemd[1]: Failed to start Networking for netctl profile <wlan_device>-eduroam.
-- Subject: Unit netctl@<wlan_device>\x2deduroam.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@<wlan_device>\x2deduroam.service has failed.
--
-- The result is failed.
Mar 20 19:22:18 <hostname> systemd[1]: Unit netctl@<wlan_device>\x2deduroam.service entered failed state.
Mar 20 19:22:25 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:22:52 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:23:37 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:24:23 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:24:53 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available
Mar 20 19:25:28 <hostname> dhcpcd[408]: <lan_device>: <some_ipv6_address> router available

My guess is that the problem is this:

Mar 20 19:22:18 <hostname> network[6651]: chmod: cannot access ‘/run/dhcpcd-<wlan_device>.pid’: No such file or directory

which is just an uneducated guess. Any ideas?

Some version numbers:

# uname -r
3.13.6-1-ARCH
# systemctl --version
systemd 211
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR
# netctl --version
netctl version 1.6
# dhcpcd --version
dhcpcd 6.3.2
Copyright (c) 2006-2014 Roy Marples

Some hardware information:

# lspci
[...]
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
[...]

Last edited by rmmonster (2014-03-20 18:42:47)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,432

Re: device specific dhcpcd pid file missing?

Related bug report: https://bugs.archlinux.org/task/39544

rmmonster

Member

Registered: 2014-03-20

Posts: 2

Re: device specific dhcpcd pid file missing?

Thanks, that fixed it for me.

zg

Member

From: California, USA

Registered: 2013-07-28

Posts: 3

Website

Re: device specific dhcpcd pid file missing?

I was having this issue as well. Removing the line that contains "IP=dhcp" in my netctl profile fixed this issue.

Last edited by zg (2014-03-23 07:35:23)

Gnux

Member

Registered: 2006-09-27

Posts: 26

Re: device specific dhcpcd pid file missing?

Hi
I ran exactly into the same problem after the last upgrade of netctl to 1.6.
Here was my profile:

Description='Automatically generated profile by wifi-menu'
Interface=wlp3s3
Connection=wireless
Security=wpa
ESSID=xxx
IP=dhcp
Key=xxx
DHCPClient='dhclient'

And as the other guys 'round here, i keep getting:

# journalctl -xn
-- Logs begin at Mon 2013-09-09 19:40:01 CEST, end at Mon 2014-05-26 10:42:34 CEST. --
May 26 10:42:34 mnemosyne network[9700]: RTNETLINK answers: File exists
May 26 10:42:34 mnemosyne dhclient[9911]: bound to 192.168.1.78 -- renewal in 37910 seconds.
May 26 10:42:34 mnemosyne network[9700]: chmod: impossible d'accéder à « /run/dhclient4-wlp3s3.pid »: Aucun fichier ou dossier
May 26 10:42:34 mnemosyne dhclient[9943]: receive_packet failed on wlp3s3: Network is down
May 26 10:42:34 mnemosyne dhclient[13947]: receive_packet failed on wlp3s3: Network is down
May 26 10:42:34 mnemosyne dhclient[386]: receive_packet failed on wlp3s3: Network is down
May 26 10:42:34 mnemosyne network[9700]: Failed to bring the network up for profile 'wlp3s3'
May 26 10:42:34 mnemosyne systemd[1]: netctl@wlp3s3.service: main process exited, code=exited, status=1/FAILURE
May 26 10:42:34 mnemosyne systemd[1]: Failed to start Networking for netctl profile wlp3s3.
-- Subject: Unit netctl@wlp3s3.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp3s3.service has failed.
-- 
-- The result is failed.
May 26 10:42:34 mnemosyne systemd[1]: Unit netctl@wlp3s3.service entered failed state.

I tried the solution provided by zg and it gave me:

# journalctl -xn
-- Logs begin at Mon 2013-09-09 19:40:01 CEST, end at Mon 2014-05-26 10:46:49 CEST. --
May 26 10:46:48 mnemosyne network[2046]: ioctl[SIOCSIWENCODEEXT]: Invalid argument
May 26 10:46:49 mnemosyne kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s3: link becomes ready
May 26 10:46:49 mnemosyne network[2046]: Neither IP, nor IP6 was specified
May 26 10:46:49 mnemosyne dhclient[9943]: receive_packet failed on wlp3s3: Network is down
May 26 10:46:49 mnemosyne dhclient[13947]: receive_packet failed on wlp3s3: Network is down
May 26 10:46:49 mnemosyne dhclient[386]: receive_packet failed on wlp3s3: Network is down
May 26 10:46:49 mnemosyne network[2046]: Failed to bring the network up for profile 'wlp3s3'
May 26 10:46:49 mnemosyne systemd[1]: netctl@wlp3s3.service: main process exited, code=exited, status=1/FAILURE
May 26 10:46:49 mnemosyne systemd[1]: Failed to start Networking for netctl profile wlp3s3.
-- Subject: Unit netctl@wlp3s3.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp3s3.service has failed.
-- 
-- The result is failed.
May 26 10:46:49 mnemosyne systemd[1]: Unit netctl@wlp3s3.service entered failed state.

It gave me nevertheless a very precious hint: I tried to comment out just the last line:

Description='Automatically generated profile by wifi-menu'
Interface=wlp3s3
Connection=wireless
Security=wpa
ESSID=xxx
IP=dhcp
Key=xxx
#DHCPClient='dhclient'

And it works at the first try...