Wicd fails to connect/inconsistently connects, manual connect works.
Hi all, wicd is failing to connect after an update today. I've tried both my wired and wireless networks; it fails to connect to both for the majority of the time. I've been able to connect 1 or twice to both without failure, however. Manually running "sudo dhcpcd eth0" connects without issue. The issue seems to be with dhcpcd 5.5.4-1, as a downgrade to the [core] version (5.2.12-4) fixes the issue. Any ideas?
/var/log/errors.log:
Feb 8 23:37:53 localhost dhcpcd[5808]: dhcpcd not running
Feb 8 23:37:54 localhost dhcpcd[5814]: dhcpcd not running
Feb 8 23:37:54 localhost dhcpcd[5820]: dhcpcd not running
Feb 8 23:37:57 localhost dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
Feb 8 23:38:00 localhost dhcpcd[5856]: dhcpcd not running
Feb 8 23:39:50 localhost dhcpcd[6067]: dhcpcd not running
Feb 8 23:39:50 localhost dhcpcd[6074]: dhcpcd not running
Feb 8 23:39:51 localhost dhcpcd[6082]: dhcpcd not running
Feb 8 23:40:08 localhost dhcpcd[6216]: dhcpcd not running
Feb 8 23:40:09 localhost dhcpcd[6238]: dhcpcd not running
/var/log/wicd/wicd.log:
2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: checking for 192.168.1.7
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: dhcpcd[3603]: forked to background, child pid 3626
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: DHCP connection successful
2012/02/08 23:26:04 :: Connecting thread exiting.
2012/02/08 23:26:05 :: Sending connection attempt result success
2012/02/08 23:27:23 :: Connecting to wireless network s_wifi
2012/02/08 23:27:24 :: Putting interface down
2012/02/08 23:27:24 :: Releasing DHCP leases...
2012/02/08 23:27:24 :: Setting false IP...
2012/02/08 23:27:24 :: Stopping wpa_supplicant
2012/02/08 23:27:24 :: Flushing the routing table...
2012/02/08 23:27:24 :: Putting interface up...
2012/02/08 23:27:26 :: Running DHCP with hostname carbon
2012/02/08 23:27:26 :: dhcpcd[3760]: version 5.5.4 starting
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: waiting for carrier
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: carrier acquired
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sending IPv6 Router Solicitation
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sendmsg: Cannot assign requested address
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: broadcasting for a lease
2012/02/08 23:27:26 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: received RA for unexpected interface from fe80::222:75ff:fed5:73d4
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: forked to background, child pid 3784
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: DHCP connection successful
2012/02/08 23:27:27 :: not verifying
2012/02/08 23:27:27 :: Connecting thread exiting.
2012/02/08 23:27:30 :: Sending connection attempt result success
2012/02/08 23:28:04 :: Putting interface down
2012/02/08 23:28:04 :: Error checking link using /sys/class/net/eth0/carrier
2012/02/08 23:28:04 :: Releasing DHCP leases...
2012/02/08 23:28:04 :: Setting false IP...
2012/02/08 23:28:04 :: Stopping wpa_supplicant
2012/02/08 23:28:04 :: Flushing the routing table...
2012/02/08 23:28:04 :: Putting interface up...
2012/02/08 23:28:06 :: Running DHCP with hostname carbon
2012/02/08 23:28:06 :: dhcpcd[3899]: version 5.5.4 starting
2012/02/08 23:28:06 ::
2012/02/08 23:28:06 :: dhcpcd[3899]: eth0: waiting for carrier
2012/02/08 23:28:06 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: carrier acquired
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sending IPv6 Router Solicitation
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sendmsg: Cannot assign requested address
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: broadcasting for a lease
2012/02/08 23:28:07 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: checking for 192.168.1.7
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: forked to background, child pid 3922
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: DHCP connection successful
2012/02/08 23:28:08 :: Connecting thread exiting.
2012/02/08 23:28:09 :: Sending connection attempt result success
2012/02/08 23:35:31 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:35:31 :: Removing PID file...
2012/02/08 23:35:31 :: Shutting down...
2012/02/08 23:35:31 :: Exception KeyError: KeyError(139867792365312,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:35:33 :: ---------------------------
2012/02/08 23:35:33 :: wicd initializing...
2012/02/08 23:35:33 :: ---------------------------
2012/02/08 23:35:33 :: wicd is version 1.7.1 717
2012/02/08 23:35:33 :: setting backend to external
2012/02/08 23:35:33 :: trying to load backend external
2012/02/08 23:35:33 :: successfully loaded backend external
2012/02/08 23:35:33 :: trying to load backend external
2012/02/08 23:35:33 :: successfully loaded backend external
2012/02/08 23:35:33 :: Automatically detected wireless interface wlan0
2012/02/08 23:35:33 :: setting wireless interface wlan0
2012/02/08 23:35:33 :: automatically detected wired interface eth0
2012/02/08 23:35:33 :: setting wired interface eth0
2012/02/08 23:35:33 :: setting wpa driver wext
2012/02/08 23:35:33 :: setting use global dns to False
2012/02/08 23:35:33 :: setting global dns
2012/02/08 23:35:33 :: global dns servers are None None None
2012/02/08 23:35:33 :: domain is None
2012/02/08 23:35:33 :: search domain is None
2012/02/08 23:35:33 :: setting automatically reconnect when connection drops True
2012/02/08 23:35:33 :: Setting dhcp client to 0
2012/02/08 23:35:33 :: Wireless configuration file found...
2012/02/08 23:35:33 :: Wired configuration file found...
2012/02/08 23:35:33 :: chmoding configuration files 0600...
2012/02/08 23:35:33 :: chowning configuration files root:root...
2012/02/08 23:35:33 :: Using wireless interface...wlan0
2012/02/08 23:35:33 :: Using wired interface...eth0
2012/02/08 23:35:47 :: Connecting to wireless network s_wifi
2012/02/08 23:35:47 :: Putting interface down
2012/02/08 23:35:48 :: Releasing DHCP leases...
2012/02/08 23:35:48 :: Setting false IP...
2012/02/08 23:35:48 :: Stopping wpa_supplicant
2012/02/08 23:35:48 :: Flushing the routing table...
2012/02/08 23:35:48 :: Putting interface up...
2012/02/08 23:35:50 :: Running DHCP with hostname carbon
2012/02/08 23:35:50 :: dhcpcd[5483]: version 5.2.12 starting
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: waiting for carrier
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: carrier acquired
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: broadcasting for a lease
2012/02/08 23:35:50 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: offered 192.168.1.3 from 192.168.1.1
2012/02/08 23:35:51 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
2012/02/08 23:35:51 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: checking for 192.168.1.3
2012/02/08 23:35:51 ::
2012/02/08 23:35:55 :: dhcpcd[5483]: wlan0: leased 192.168.1.3 for 283824000 seconds
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 :: dhcpcd[5483]: forked to background, child pid 5514
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 :: DHCP connection successful
2012/02/08 23:35:55 :: not verifying
2012/02/08 23:35:55 :: Connecting thread exiting.
2012/02/08 23:35:58 :: Sending connection attempt result success
2012/02/08 23:37:39 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:37:39 :: Removing PID file...
2012/02/08 23:37:39 :: Shutting down...
2012/02/08 23:37:39 :: Exception KeyError: KeyError(139889612089088,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:37:40 :: ---------------------------
2012/02/08 23:37:40 :: wicd initializing...
2012/02/08 23:37:40 :: ---------------------------
2012/02/08 23:37:40 :: wicd is version 1.7.1 717
2012/02/08 23:37:40 :: setting backend to external
2012/02/08 23:37:40 :: trying to load backend external
2012/02/08 23:37:40 :: successfully loaded backend external
2012/02/08 23:37:40 :: trying to load backend external
2012/02/08 23:37:40 :: successfully loaded backend external
2012/02/08 23:37:40 :: Automatically detected wireless interface wlan0
2012/02/08 23:37:40 :: setting wireless interface wlan0
2012/02/08 23:37:40 :: automatically detected wired interface eth0
2012/02/08 23:37:40 :: setting wired interface eth0
2012/02/08 23:37:40 :: setting wpa driver wext
2012/02/08 23:37:40 :: setting use global dns to False
2012/02/08 23:37:40 :: setting global dns
2012/02/08 23:37:40 :: global dns servers are None None None
2012/02/08 23:37:40 :: domain is None
2012/02/08 23:37:40 :: search domain is None
2012/02/08 23:37:40 :: setting automatically reconnect when connection drops True
2012/02/08 23:37:40 :: Setting dhcp client to 0
2012/02/08 23:37:41 :: Wireless configuration file found...
2012/02/08 23:37:41 :: Wired configuration file found...
2012/02/08 23:37:41 :: chmoding configuration files 0600...
2012/02/08 23:37:41 :: chowning configuration files root:root...
2012/02/08 23:37:41 :: Using wireless interface...wlan0
2012/02/08 23:37:41 :: Using wired interface...eth0
2012/02/08 23:37:46 :: Connecting to wireless network s_wifi
2012/02/08 23:37:46 :: Putting interface down
2012/02/08 23:37:46 :: Releasing DHCP leases...
2012/02/08 23:37:46 :: Setting false IP...
2012/02/08 23:37:47 :: Stopping wpa_supplicant
2012/02/08 23:37:47 :: Flushing the routing table...
2012/02/08 23:37:47 :: Putting interface up...
2012/02/08 23:37:49 :: Running DHCP with hostname carbon
2012/02/08 23:37:49 :: dhcpcd[5759]: version 5.5.4 starting
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sending IPv6 Router Solicitation
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sendmsg: Cannot assign requested address
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: broadcasting for a lease
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: forked to background, child pid 5777
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: DHCP connection successful
2012/02/08 23:37:49 :: not verifying
2012/02/08 23:37:49 :: Connecting thread exiting.
2012/02/08 23:37:52 :: Sending connection attempt result success
2012/02/08 23:37:52 :: Autoconnecting...
2012/02/08 23:37:53 :: Putting interface downAttempting to autoconnect with wired interface...
2012/02/08 23:37:53 ::
2012/02/08 23:37:53 :: Releasing DHCP leases...
2012/02/08 23:37:53 :: Setting false IP...
2012/02/08 23:37:53 :: Stopping wpa_supplicant
2012/02/08 23:37:53 :: Flushing the routing table...
2012/02/08 23:37:53 :: Putting interface up...
2012/02/08 23:37:55 :: Running DHCP with hostname carbon
2012/02/08 23:37:55 :: dhcpcd[5828]: version 5.5.4 starting
2012/02/08 23:37:55 ::
2012/02/08 23:37:55 :: dhcpcd[5828]: eth0: waiting for carrier
2012/02/08 23:37:55 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: carrier acquired
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sending IPv6 Router Solicitation
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: broadcasting for a lease
2012/02/08 23:37:57 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: checking for 192.168.1.7
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: forked to background, child pid 5851
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: DHCP connection successful
2012/02/08 23:37:58 :: Connecting thread exiting.
2012/02/08 23:38:00 :: Sending connection attempt result success
2012/02/08 23:38:01 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/08 23:38:04 :: Unable to autoconnect, you'll have to manually connect
2012/02/08 23:39:43 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:39:43 :: Removing PID file...
2012/02/08 23:39:43 :: Shutting down...
2012/02/08 23:39:43 :: Exception KeyError: KeyError(140388630619904,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:39:45 :: ---------------------------
2012/02/08 23:39:45 :: wicd initializing...
2012/02/08 23:39:45 :: ---------------------------
2012/02/08 23:39:45 :: wicd is version 1.7.1 717
2012/02/08 23:39:45 :: setting backend to external
2012/02/08 23:39:45 :: trying to load backend external
2012/02/08 23:39:45 :: successfully loaded backend external
2012/02/08 23:39:45 :: trying to load backend external
2012/02/08 23:39:45 :: successfully loaded backend external
2012/02/08 23:39:45 :: Automatically detected wireless interface wlan0
2012/02/08 23:39:45 :: setting wireless interface wlan0
2012/02/08 23:39:45 :: automatically detected wired interface eth0
2012/02/08 23:39:45 :: setting wired interface eth0
2012/02/08 23:39:45 :: setting wpa driver wext
2012/02/08 23:39:45 :: setting use global dns to False
2012/02/08 23:39:45 :: setting global dns
2012/02/08 23:39:45 :: global dns servers are None None None
2012/02/08 23:39:45 :: domain is None
2012/02/08 23:39:45 :: search domain is None
2012/02/08 23:39:45 :: setting automatically reconnect when connection drops True
2012/02/08 23:39:45 :: Setting dhcp client to 0
2012/02/08 23:39:45 :: Wireless configuration file found...
2012/02/08 23:39:45 :: Wired configuration file found...
2012/02/08 23:39:45 :: chmoding configuration files 0600...
2012/02/08 23:39:45 :: chowning configuration files root:root...
2012/02/08 23:39:45 :: Using wireless interface...wlan0
2012/02/08 23:39:45 :: Using wired interface...eth0
2012/02/08 23:39:50 :: Autoconnecting...
2012/02/08 23:39:50 :: Attempting to autoconnect with wired interface...
2012/02/08 23:39:50 :: Putting interface down
2012/02/08 23:39:51 :: Releasing DHCP leases...
2012/02/08 23:39:51 :: Setting false IP...
2012/02/08 23:39:51 :: Stopping wpa_supplicant
2012/02/08 23:39:51 :: Flushing the routing table...
2012/02/08 23:39:51 :: Putting interface up...
2012/02/08 23:39:53 :: Running DHCP with hostname carbon
2012/02/08 23:39:53 :: dhcpcd[6087]: version 5.2.12 starting
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: waiting for carrier
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: carrier acquired
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: broadcasting for a lease
2012/02/08 23:39:53 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:39:54 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:39:54 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: checking for 192.168.1.7
2012/02/08 23:39:54 ::
2012/02/08 23:39:58 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:39:58 :: Removing PID file...
2012/02/08 23:39:58 :: Shutting down...
2012/02/08 23:39:58 :: Exception KeyError: KeyError(140583090784000,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:40:00 :: ---------------------------
2012/02/08 23:40:00 :: wicd initializing...
2012/02/08 23:40:00 :: ---------------------------
2012/02/08 23:40:00 :: wicd is version 1.7.1 717
2012/02/08 23:40:00 :: setting backend to external
2012/02/08 23:40:00 :: trying to load backend external
2012/02/08 23:40:00 :: successfully loaded backend external
2012/02/08 23:40:00 :: trying to load backend external
2012/02/08 23:40:00 :: successfully loaded backend external
2012/02/08 23:40:00 :: Automatically detected wireless interface wlan0
2012/02/08 23:40:00 :: setting wireless interface wlan0
2012/02/08 23:40:00 :: automatically detected wired interface eth0
2012/02/08 23:40:00 :: setting wired interface eth0
2012/02/08 23:40:00 :: setting wpa driver wext
2012/02/08 23:40:00 :: setting use global dns to False
2012/02/08 23:40:00 :: setting global dns
2012/02/08 23:40:00 :: global dns servers are None None None
2012/02/08 23:40:00 :: domain is None
2012/02/08 23:40:00 :: search domain is None
2012/02/08 23:40:00 :: setting automatically reconnect when connection drops True
2012/02/08 23:40:00 :: Setting dhcp client to 0
2012/02/08 23:40:00 :: Wireless configuration file found...
2012/02/08 23:40:00 :: Wired configuration file found...
2012/02/08 23:40:00 :: chmoding configuration files 0600...
2012/02/08 23:40:00 :: chowning configuration files root:root...
2012/02/08 23:40:00 :: Using wireless interface...wlan0
2012/02/08 23:40:00 :: Using wired interface...eth0
2012/02/08 23:40:09 :: Putting interface down
2012/02/08 23:40:09 :: Releasing DHCP leases...
2012/02/08 23:40:09 :: Setting false IP...
2012/02/08 23:40:09 :: Stopping wpa_supplicant
2012/02/08 23:40:09 :: Flushing the routing table...
2012/02/08 23:40:09 :: Putting interface up...
2012/02/08 23:40:11 :: Running DHCP with hostname carbon
2012/02/08 23:40:11 :: dhcpcd[6245]: version 5.2.12 starting
2012/02/08 23:40:11 ::
2012/02/08 23:40:11 :: dhcpcd[6245]: eth0: waiting for carrier
2012/02/08 23:40:11 ::
2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: carrier acquired
2012/02/08 23:40:12 ::
2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: broadcasting for a lease
2012/02/08 23:40:12 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:40:13 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:40:13 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: checking for 192.168.1.7
2012/02/08 23:40:13 ::
2012/02/08 23:40:18 :: dhcpcd[6245]: eth0: leased 192.168.1.7 for 283824000 seconds
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 :: dhcpcd[6245]: forked to background, child pid 6272
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 :: DHCP connection successful
2012/02/08 23:40:18 :: Connecting thread exiting.
2012/02/08 23:40:19 :: Sending connection attempt result success
excerpt from dmesg:
[ 220.232167] iwlwifi 0000:03:00.0: PCI INT A disabled
[ 235.617077] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 235.617084] Copyright(c) 2003-2011 Intel Corporation
[ 235.617227] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 235.617297] iwlwifi 0000:03:00.0: setting latency timer to 64
[ 235.617467] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[ 235.617472] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900117e4000
[ 235.617477] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[ 235.618087] iwlwifi 0000:03:00.0: irq 56 for MSI/MSI-X
[ 235.618299] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[ 235.618699] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 235.647477] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[ 235.647483] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
[ 235.647488] iwlwifi 0000:03:00.0: Valid Tx ant: 0X7, Valid Rx ant: 0X7
[ 235.647519] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 235.650620] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[ 235.650965] Registered led device: phy1-led
[ 235.651159] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
[ 246.254967] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 246.261863] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 246.530405] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 246.537210] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 246.685081] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 251.545715] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 251.552573] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 251.752912] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 252.006076] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.058081] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.060295] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 252.305685] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.357970] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.359622] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 253.667466] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 253.674333] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 253.880956] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 254.137065] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 254.189437] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 254.191042] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 254.282074] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 254.288879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 254.493939] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 256.572737] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.627057] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 256.634142] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.636012] wlan0: authenticated
[ 256.737360] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 256.786082] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 256.826726] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 256.828337] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 256.881172] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.884801] wlan0: authenticated
[ 256.986051] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 256.991611] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 256.991618] wlan0: associated
[ 257.006311] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 541.311145] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 541.368832] cfg80211: Calling CRDA to update world regulatory domain
[ 541.453885] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 541.460755] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 541.683356] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 542.134773] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 542.187993] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 542.189715] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 545.110702] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 545.111269] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 546.693999] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 546.700730] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 546.936168] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 547.190401] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 547.243068] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 547.244623] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 547.340217] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 547.347099] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 547.560981] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 549.644554] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 549.647565] wlan0: authenticated
[ 549.647945] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 549.651558] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 549.651564] wlan0: associated
[ 549.664372] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 551.461505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 551.463148] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 552.308069] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 552.361536] cfg80211: Calling CRDA to update world regulatory domain
[ 552.462798] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 552.469740] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 552.690035] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 552.942343] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 552.994174] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 552.995790] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 555.897119] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 555.898730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 579.349813] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 579.356589] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 579.591802] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 579.846307] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 579.898914] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 579.900576] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 580.152275] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 580.205302] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 580.206916] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 582.895184] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 582.896930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 585.270436] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 585.277198] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 585.499201] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 585.854505] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 585.906564] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 585.908183] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 588.995907] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 588.997528] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 663.872912] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 663.879693] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 664.081192] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 664.334184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 664.385981] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 664.387425] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 664.487889] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 664.494654] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 664.717618] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 666.791284] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 666.793798] wlan0: authenticated
[ 666.794109] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 666.797735] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 666.797743] wlan0: associated
[ 666.813158] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 667.322243] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 667.323899] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 670.192203] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 670.263747] cfg80211: Calling CRDA to update world regulatory domain
[ 670.358193] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 670.365031] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 670.589231] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 670.840405] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 670.893001] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 670.894626] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 675.344581] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 675.346128] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 703.509218] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 703.515992] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 703.736371] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 703.985977] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.038426] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.040078] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 704.292262] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.344831] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.346446] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 706.924844] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 706.926454] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 709.146741] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 709.153635] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 709.380526] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 709.727666] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 709.779778] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 709.781421] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 712.682663] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 712.683237] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1163.099577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1163.106361] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1163.334124] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1163.785622] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1163.838170] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1163.839786] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1164.088913] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1164.141284] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1164.142888] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1166.755012] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1166.761833] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1166.791221] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1167.001157] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1167.002730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1167.256207] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1167.308293] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1167.309927] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1167.433323] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1167.440189] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1167.683916] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1169.766437] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 1169.769518] wlan0: authenticated
[ 1169.769895] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 1169.773508] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 1169.773514] wlan0: associated
[ 1169.788727] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1170.264529] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1170.266191] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1250.157515] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 1250.213474] cfg80211: Calling CRDA to update world regulatory domain
[ 1250.304748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1250.311548] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1250.531278] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1250.786838] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1250.839522] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1250.841153] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1253.742306] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1253.743948] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1285.564500] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1285.571291] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1285.799384] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1286.050860] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1286.102984] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1286.104632] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1286.225143] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1286.231901] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1286.434212] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1288.467235] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 1288.469740] wlan0: authenticated
[ 1288.470052] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 1288.473730] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 1288.473738] wlan0: associated
[ 1288.485867] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1289.075695] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1289.077339] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1291.610215] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 1291.654374] cfg80211: Calling CRDA to update world regulatory domain
[ 1291.749248] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1291.755994] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1291.979161] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1292.230432] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.283644] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.285268] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1292.534611] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.586642] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.588281] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1293.916374] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1293.923205] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1294.158126] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1294.410095] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1294.461555] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1294.463149] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1296.861675] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1296.863283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1299.572965] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1299.579879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1299.802442] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1300.160999] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1300.212812] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1300.214548] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1303.095815] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1303.097470] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1409.502302] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1409.509094] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1409.732008] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1409.987074] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.039305] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.040915] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1410.289187] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.342358] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.344038] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1413.025445] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1413.027081] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1427.879453] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1427.886240] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1428.101077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1428.452191] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.505126] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.506718] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1428.756124] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.808184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.809809] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1431.511433] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1431.513072] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
roobie wrote:
I had a similar problem yesterday (especially reffering to the error "Exception KeyError: KeyError(-1219500352,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored"
And after reading https://bbs.archlinux.org/viewtopic.php?id=121589 i synced my system time with my hwclock and it worked after that. The command I used:
hwclock -u -systohc
It may be the cause of your problem as well...
My hardware clock and system time are in sync and there's no change of time in my logs like is mentioned in the thread. I don't think this is the issue.
EDIT: This seems to be limited to my home network, possibly an IPv6 problem. Maybe the IPv6 address is not being assigned properly somewhere?
Last edited by soupcan (2012-02-10 00:23:03)
Similar Messages
-
Wicd fails to connect with a WEP key
I'm trying to connect to my wireless network after the recent update to net-tools. I sorted through most of my issues with the hostname command (I think) by installing inetutils and the recent update to wicd. Now, after trying to reconnect, my /var/log/wicd/wicd.log looks like the following:
2011/10/04 09:23:48 :: trying to automatically connect to...UVEE2
2011/10/04 09:23:48 :: Connecting to wireless network UVEE2
dhcpcd[12869]: dhcpcd not running
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
dhcpcd[12912]: dhcpcd not running
2011/10/04 09:23:48 :: Putting interface down
2011/10/04 09:23:48 :: Releasing DHCP leases...
dhcpcd[12967]: dhcpcd not running
2011/10/04 09:23:48 :: Setting false IP...
2011/10/04 09:23:49 :: Stopping wpa_supplicant
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2011/10/04 09:23:49 :: Flushing the routing table...
2011/10/04 09:23:49 :: Putting interface up...
2011/10/04 09:23:51 :: Attempting to authenticate...
unlink[ctrl_iface]: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2011/10/04 09:23:51 :: connect result is Failed
2011/10/04 09:23:51 :: exiting connection thread
2011/10/04 09:23:51 :: Sending connection attempt result bad_pass
dhcpcd[13034]: dhcpcd not running
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
dhcpcd[13078]: dhcpcd not running
This looks strange to me because I am connecting to a wireless network that has a WEP hex key, and nothing in my configuration suggests any WPA key. I even tried rm-ing all of the *.conf files in /etc/wicd/ to no avail. Thank heavens for netcfg, or I think Arch Linux would have just blown my network stack again, the way the net-tools "upgrade" did
Does anyone have any tips on how to solve this?
P.S. Maybe it would be good to have some testing process for future updates affecting network connectivity? If this were my only computer I would totally have been dead in the water with the net-tools update. It took a sizable amount of time and effort to find out I needed to bootstrap the hostname command. For a while, before I figured to check the wicd logs, I was considering just dropping Arch Linux. Breaking the internet is just about the worst because you leave people with broken systems and no way to look up how to fix them.Sorry, but I don't think that thread applies here. That thread is dealing with the net-tools upgrade, and the missing hostname utility. I fixed that, dhcpcd works just fine. My problem is that after the wicd update, it tries to use WPA to connect to a network that I have specified as using WEP, so it fails to authenticate.
-
Automatic startup/shutdown failed. Running the script manual..works...
Hi,
DB: Oracle9i
Os: solaris 9
/etc/rc0.d K05oracle -> /etc/init.d/oracledb
/etc/rc3.d SS85oracle -> /etc/init.d/oracledb
Oratab: i have put yes.
Please help to resolve this issue...where can i check the startup log?
what else i need to check?
Thanks,
Siva.Thanks for your reply....
Script:
#!/bin/sh
case "$1" in
'start')
# Sets ORACLE_HOME to latest version on machine
# ORACLE_HOME="`cut -d ":" -f 2 /var/opt/oracle/oratab | sort | tail -1`"
ORACLE_HOME=`grep -v "^#" /var/opt/oracle/oratab|grep -v "^$"|cut -d ":" -f 2 | sort | tail -1`
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME:$ORACLE_HOME/bin
# If you are running Oracle's Multi-Threaded Server, the SQL*Net
# listener service must be started before the database is started.
# If it is not, your dispatcher(s) will not start.
if [ -f $ORACLE_HOME/bin/dbstart ]
then
echo "Starting up Oracle databases."
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/lsnrctl start"
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/dbstart"
else
echo "Can't find Oracle startup file."
fi
'stop')
# Sets ORACLE_HOME to latest version on machine
ORACLE_HOME="`cut -d ":" -f 2 /var/opt/oracle/oratab | sort | tail -1`"
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME:$ORACLE_HOME/bin
if [ -f $ORACLE_HOME/bin/dbshut ]
then
echo "Shutting down Oracle databases."
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/dbshut"
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/lsnrctl stop"
else
echo "Can't find Oracle shutdown file."
fi
echo "Usage: /etc/init.d/database { start | stop }"
esac -
[SOLVED] wicd fails to automatically connect to a network
I have just upgrade to kernel 3.6.5-1 and after that wicd fails to autoconnect to my wireless network which I have set "Automatically connect to this network" from wicd-curse.
Is anyone experiencing the same issue? Any idea on what causing the issue?
Last edited by pingpong (2012-11-03 05:07:58)Do you think some more information might help?
Start with telling us your chipset. Check with lspci -nn (That would be two n's, not m)
Also, is it your router? Is it encrypted? WPA? WEP?
Can you see it with iwlist scan
Can you associate with the access point by hand?
Is there anything interesting in the journal (or logs)?
What DE are you using?
Is the WAN blocked? (Check with rfkill list)
Last edited by ewaller (2012-11-03 03:50:27) -
On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013
I have a new install of Windows 2012. I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server. (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support -
Airport fails to connect at login (only)
Using a MacBook with OSX 10.5, I am trying to connect to a WPA2 Enterprise network. All of the settings are correct, and the certificate is set on 'always trust'.. but on startup/login, Airport fails to connect (no error message, but IP address is self-assigned). If I turn airport off and back on, it properly connects instantly, with no prompts at all.
Does anyone know a reason why the machine would be unable to automatically connect to the network at login, but able to just fine if I manually turn the airport off and back on?Hmm.. in retrospect this probably isn't the right sub-forum for this question.. it should maybe go in a sub-forum for OS X 10.5 instead (it's not related to the airport basestation). Please feel free to move this, if so.
-
Mail Fails To Connect In My Office Network, Works on Reboot
This is baffling me and my network admin:
Mail fails to connect to any of my accounts at work. But it recovers if I reboot my machine.
Here is what happens:
- Mail works just fine at home. Connects to gmail, iCloud, and a 3rd party email account no problems.
- I get to the office
- I log in to the office WiFi with my password - for this I have to open a browser window, and enter my credentials.
(I kind of assume that this is the problem ^^)
- All my internet connections work fine, I can use the browser to access Gmail etc
- Mail refuses to connect to any of my email servers, and all accounts go offline
- Connection Doctor says "Mail can connect to the internet" but all individual connections are red, not reachable. I checked "detail" too - its empty.
Then I reboot my Mac, and after that everything's happy. Mail connects to my accounts normally, and Connection Doctor marks all as green.
Since it works on reboot, we can rule out network problems like closed ports etc. So the only thing I can think of is that Mail initially tries to connect as soon as I am on WiFi, then hangs (because I am not logged in yet), and somehow this hang is of a kind that does not recover (I've left it on for hours at a time, no difference, it never recovers).
Anyone have any ideas about this? Is there some way I can restart networking daemons to kill the hung connections. Or any other way I can diagnose this?A captive portal, which is what you have, can work in any of at least three ways: by HTTP redirection, IP redirection, or DNS poisoning. I'm guessing that yours is the last type. In that case, a TTL of zero should be used. If the TTL is non-zero, then Internet applications may not work until the DNS cache is flushed. That happens when you reboot.
You should discuss the possibility with your network admin. If the network configuration isn't going to be changed, you may be able to avoid the need to reboot by flushing the DNS cache manually, as described in the article linked below:
OS X: How to reset the DNS cache -
Ipad2 'fails to connect' to my Wifi.
My Ipad2 'fails to connect' to my Wifi whereas my Iphone 3GS successfully connects and works without issue on the same router. Wifi is WEP encrypted with 26 character code. The Ipad 2 sees the network, yet will not connect. I have tried the 'reset network settings' option and I'm looking for any further suggestions?
The process of checking your router settings depends on the router you have. You will need the manual that came with your router. If you don't have one, you probably can download a manual from the router manufacturer's website.
Basically the process is starting your web browser on a computer that is connected to your network. Entering the IP address of the router in the web address line. Usually the IP address of the router is the same as the IP address of the computer connected to your network except the last number is 1. For example if the IP address of the computer is 192.168.0.132, then the IP address of the router would be 192.168.0.1.
The next question you may have is how do you find the IP address of the computer. If you have a Windows computer, go to Start/Run or Start/Programs/Accessories/Run. Type in "CMD" (no quote marks) and press the Enter key. A DOS window will appear. At the command prompt type "ipconfig" and press the Enter key. The resulting listing should show you the IP address of the computer and the IP address of your router (listed as Default Gateway.) If you have a Mac I can't help you, because I don't have a Mac, but I'm sure someone on this forum would be able to help.
Once you enter th IP Address of your router, you should get a login screen. You will need to log into the router. Note that the login password is not the network passcode. If you do not know the Admin login name and password and you are sure no one has changed the password from the default, the router manual will have this information.
When you are logged into the router you need to consult the router manual to find out how to check the settings. If purchance you have a D-link DIR-625 I can help. -
SQL Server Agent fails to connect to DB after enabling mirror on failover cluster
Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joeSQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M. -
Fails to connect, forgets password
I have a 2G Touch with 3.1.1 software. This problem was happening before the 3.1.1 upgrade, but does seem to be happening a bit more frequently since.
There are several Wi-Fi networks I connect to regularly, but have a problem with only one. That is the one at my office, which uses an older D-Link router. It's not unusual to have to try a couple of times before connecting, and I blame the router for that. However, sometimes when it fails to connect, the iPod then seems to forget the password. That is, the connection fails and when I try again, it asks for the password. That works, and it continues to work on subsequent tries until a day or two later when it fails and demands the password again.
Not much I can do about the router, but it seems to me that the iPod should remember the password, even after a failed connection. I've tried resetting the network settings, restarting the iPod, forgetting the network and re-entering it. Nothing improves the problem.
Any suggestions?Similar issue has hsppen to my 2 gen itouch after 3.1.1 update. If the ssid is not broadcasted, itouch wont remember the network name.
Network at work, the ssid is not broadcasted and there is no password for the network. Every time after I put itouch to sleep, I will need to enter the network name again when I turn on the itouch. The 1st gen itouch without 3.1.1 update doesn't require me input the network name over and over.
Just tested the home network. Everything works fine if I have ssid broadcasted. Once I hide the ssid, itouch wont pick up the network at all until I manually type in the network name. It also forgets the password as well just like what posthocergopropterhoc had mentioned.
I am very positive that firmware 2.2.2 does pick up hidden ssid once it has been entered once. However, I will double check again with my friend's itouch again tomorrow and post the confirmation.
I am not sure if Apple purposely design 3.1.1 upgrade to act this way, but its for sure very inconvenient. Especially when it says on itouch network interface that "Known networks will be joined automatically". I do consider I know my own network even if the ssid is hidden for privacy reason.
Message was edited by: WonderingPisces -
MDBs failed to connect to remote JMS server
Hi,
We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
<weblogic-enterprise-bean>
<ejb-name>MyBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyTopic</destination-jndi-name>
<provider-url>t3://myhost:19009,myhost:19011</provider-url>
<connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
di-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
(t3://myhost:19009) but got the same result.
When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
Any help would be greatly appreciated.
Thanks,
ThaoI'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?). I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
>>> Could you elaborate on the known problem?
9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
>>> What else I can try?
Beyond contacting customer support, I'm not sure.
Tom -
Windows 7- Adobe Reader X 10.1.4- "An Internal Error Occurred"-"Fatal Error, Adobe Failed to connect
I downloaded Adobe Reader X 10.1.4 lately and I could not open any pdf file I have and gave a message, "An Internal Error Occurred. I tried to change it under the Program Features for updates and fixes and re-started my computer. Then I tried to open again a pdf file and a message " Fatal Error", Adobe failed to connect to DDE Server. What do I need to do to fix this up? Is Adobe even aware of this?
If all things fail and you are not getting a resolution to this. Delete the Windows 7 User profile. C:\Windows\Users\<user name>
Reboot, then recreate the user profile by logging on as the User. You are not done yet.
Logoff and log back as Administrator and go to Regedit and manually delete the user profile from the Registry.
Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\[SID] look for the User name.bak
Delete it. Then reboot and go back and log on as the user. That should fix it.
If you get lost with those instructions on how to delete user profile. Go to this link:
The best way to delete the user profile from a domain joined Windows PC - fixedByVonnie -
Hi,
wicd doesn't connect my wired interface on boot. In it's log it complaints:
2008/10/11 13:22:10 :: No wired connection present, attempting to autoconnectto wireless network
I've tried to add
ifconfig -a > /tmp/ifconfig_output
at the beginning of /etc/rc.d/wicd and eth0 is present in the output.
I've tried to stop wicd, bring eth0 down, then start it again and it connected, so the problem is specific to boot time.
Following the wiki, the network daemon, dhcdbd, networkmonitor, eth0 and eth0 routes are banged out.
I am out of ideas, can you help?kremso wrote:
Ok, for everyone else facing the problem, here is the wicd patch:
should go to: /usr/lib/python2.5/site-packages/wicd/wnettools.py
http://wicd.pastebin.com/m6991fd19
kremso,
My Installation did work before the update, then I had the same problem, but the patch does not work. I Pasted it to wnettools.py and cut the old def, still the same problem. If I connect manually after booting all is fine. Well, exept that my wireless connection has gone to nirvana after the kernel update, but that seems to be another story... Rolling distros are are a real thrill, but that's what were here for, ain't we?
Harvey -
Deploying Business Definition error: RPE-02150: Failed to connect
During deploying a business definition module, I encountered an error message like this: "RPE-02150: Failed to connect with user EUL_FROM_OWB, password ***, connection null. Disco export file 2230.eex written to directory owb/deployed_files."
I have 10.2 as the database, OWB R2, and OracleBI Discoverer 10g (10.1.2.2).
In fact, I did not have problem previously when I was using database 10.1.
Any hints? Thanks.
JohnI hope this will find you in good faith...
I have tried a workaround on this issue and it worked fantastically.
The error message in Control Centre will generate an .eex file.
Before you deploy your objects make sure you've selected the Business Area and the Items you want to deploy, and then deploy.
Once done, locate your eex file and manually import this file via Oracle Discoverer Administrator.
hope this will help
Ots -
Hamachi not launching, failed to connect to engine, error 1053, tried EVERYTHING
Please read before suggesting doing things I've already tried. So here's what's happening with my Hamachi, When I try to get it booted up, I get an error that says, "failed to connect to engine".So I went into services, made sure the "Allow services to interact with Desktop" option under the Logon tab in the Properties was unchecked.After that I tried to start the tunneling engine manually from there.I recieved an error 1053 message, "the service did respond to the start or control request in a timely fashion" After reading this I checked the registry, under HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/LogMeIn Hamachi and made sure the EngineConfigDir folder was there, and had to add it in as it was missing. After having done all of this I tried to start Hamachi once again, and kept getting the same errors all over again. What do I do??? I'm seriously desperate to get this up and running, but I cannot for the life of me figure out what is wrong.
The run solution was the only one that worked for me! :) If it does this again I might just try to un-install and install again. Catasstrophy wrote:
you can fix this problem easily:1.hold the windows button and press the "r" key or go to start menu and type "run" and launch "Run"2.type in the run window "services.msc" and press enter3.scroll to "LogMeIn Hamatchi Tunneling Engine" and click it4.press "start the service"5.launch LogMeIn
Maybe you are looking for
-
How can I see previously stored tunes no longer on my computer? Where are iCloud audio files?
Maybe my question has an answer too "obvious" for me to see it. But lately I've become aware of tunes that, for one reason or another, are not showing in my iMac's iTunes program. I went to System Preferences and clicked on "iCloud." Immediately, I
-
10.5.7 update broke sharing on my G5 PowerPC
So, silly me, I ran the 10.5.7 update on all my machines and now my G5 PowerPC has gone AWOL from the rest of my network and now file sharing and printer sharing are broken. I have an intel MacBook Pro and intel MacMini which I can connect to with no
-
My daughter downloaded the new safari update on her iMac and now it won't open without new os update
We downloaded the new safari update on my daughter's iMac and one it won't open without the new os. How do we go back to the previous safari? Thanks!
-
Hi All, We have a repository that is built on top of a SQL server database and the front end application works fine. We have now created another repository against another SQL Server database and wanted to have this as a separate subject area in the
-
I want to stop the scheduling of the process chains for two days in a week. Presently the chains are running daily and i need to stop the loading for two days in a week.