You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

StigBull Author

Level 1

20 points

My network connection completely died - "failed: 49 - Can't assign requested address"

The entire networking stack on my 2012 Retina MBP died just a few minutes ago, and I was only able to get it up and running by rebooting.

First no sites in Safari worked and then I noticed when using telnet that:

[stig@Hyperion:~]$ telnet www.allthingsd.com 80

Trying 192.0.65.213...

telnet: connect to address 192.0.65.213: Can't assign requested address

Trying 192.0.65.216...

telnet: connect to address 192.0.65.216: Can't assign requested address

telnet: Unable to connect to remote host

Strangely enough traceroute and ping worked.

In the system log there is no warning untill the network is down:

Nov 12 10:28:31 Hyperion.local mDNSResponder[62]: AppendDNSNameString: Illegal empty label in name ".weblamb.com"

Nov 12 10:28:31 Hyperion com.apple.launchd.peruser.501[164] (com.onible.iTunificationStartup[65065]): Exited with code: 1

Nov 12 10:28:31 Hyperion com.apple.launchd.peruser.501[164] (com.onible.iTunificationStartup): Throttling respawn: Will start in 10 seconds

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111635 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111635 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111634 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111634 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111637 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111637 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111636 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111636 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111639 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111639 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111638 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111638 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111642 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111642 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111640 connectx to 23.23.14.248#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111644 connectx to 192.237.224.183#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111644 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111646 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111646 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111645 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111645 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111647 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111647 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111648 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111648 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111640 connectx to 107.22.72.129#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111649 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111649 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111650 connectx to 184.86.224.214#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111650 failed to connect

I tried flushing the routes and using ifconfig to down/up the interfaces but nothing worked.

Has anybody seen anything like this?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Nov 12, 2013 2:15 AM

158 replies

Nate12

Level 1

0 points

Nov 25, 2013 11:13 AM in response to StigBull

Some updates. I can't seem to keep my system up continuously at the momement. It tends to throw a kernel panic when I wake the machine from sleep. The best uptime I have had since the problem last occurred was about 7 days. A periodic check of netstat showed nothing unusual during that time. This problem seems to only occur at longer uptimes ( > 21 days).

I am leaving my system up (without cpu sleep) running bittorrent to see if I can cause the bug to appear again.

Nov 25, 2013 11:48 AM in response to meople

I I forced keepalive to on and set all the expire times to 1. Naturally, it had no effect, maybe because these connections are orphans. That's why I asked about minimum values for which lower values might be ignored by the OS.

meople

Level 1

0 points

Nov 26, 2013 12:42 AM in response to stackman_dx

Still, someone should post output of sysctl for a pre-mavericks system.

otodic

Level 1

0 points

Nov 26, 2013 1:42 AM in response to StigBull

Same problem here on MBP 2010 with maverick.

Nov 26, 2013 7:42 AM in response to otodic

I'm curious to know if people that are having this issue have set their computer to sleep during its uptime.

I definitely agree that this issue doesn't show unless you've been up for a long time (3wk+) because there are a lot of sockets (65k+, but OSX only allocates a few thousand of them as dynamic connections) to exhaust before you run out.

I suspect it may have to do with sockets not being released on sleep, and not being reacquired on wake, so they leak.

Nov 26, 2013 7:52 AM in response to stackman_dx

stackman_dx wrote:

I'm curious to know if people that are having this issue have set their computer to sleep during its uptime.

I definitely agree that this issue doesn't show unless you've been up for a long time (3wk+) because there are a lot of sockets (65k+, but OSX only allocates a few thousand of them as dynamic connections) to exhaust before you run out.

I suspect it may have to do with sockets not being released on sleep, and not being reacquired on wake, so they leak.

Reasonable theory. Both of my computers are going to sleep.

meople

Level 1

0 points

Nov 26, 2013 8:39 AM in response to stackman_dx

I don't put my mini to sleep.

StigBull Author

Level 1

20 points

Nov 26, 2013 10:08 AM in response to jdavidbakr-wgm

I have two Mini's at home which I do put to sleep. So far it has not happen with any of these. The one I'm typing this on right now has an uptime of 34 days and 13 hours.

The 2012 Retina MBP I use at work is never put to sleep, and it was with this one I experienced it.

otodic

Level 1

0 points

Nov 26, 2013 10:15 AM in response to stackman_dx

Yes, it goes to sleep.

The problem started on Nov 25th, and the laptop was rebooted on Nov 4th (after Maverick update). So, about 21 days.

Nov 26, 2013 11:24 AM in response to otodic

Just making sure, you guys have specifically set the Mac to not sleep in power settings? By default, OSX is configured to sleep after 10min (or 15? i forget) of inactivity, and hibernate after some longer amount of time. Waking from sleep is fast enough to be imperceivable from just having the display turn off.

Nov 26, 2013 11:35 AM in response to stackman_dx

stackman_dx wrote:

Just making sure, you guys have specifically set the Mac to not sleep in power settings? By default, OSX is configured to sleep after 10min (or 15? i forget) of inactivity, and hibernate after some longer amount of time. Waking from sleep is fast enough to be imperceivable from just having the display turn off.

You know what, after you said this I went back and checked. I said that my computer is going to sleep, but I misspoke - I do have my energy saver settings set to "Never" sleep, I'm just turning the display off. So mine are not going to sleep.

One more point that may or may not be relevant, on my home computer I stay logged in all the time, at work I log out every night.

Nov 26, 2013 4:17 PM in response to StigBull

iMac 2011 on Mavericks, same situation, 35 days of uptime

sinm

Level 1

4 points

Dec 10, 2013 12:48 AM in response to StigBull

Same here. Mac mini mid 2010. Sleep disabled. 11 days uptime. Updated from 10.8. Closing Chrome, Skype and Fusion helped for several minutes...

StigBull Author

Level 1

20 points

Dec 10, 2013 5:51 AM in response to sinm

Is anyone else here using Dropbox?

I noticed right now with netstat and lsof that Dropbox<->Finder has a heck of a lot of established connections.

Take a look at this (PID 26164 is dropbox)

[stig@Hyperion:~]$ sudo lsof|grep 26164

Finder 211 stig 5u IPv4 0xaae910ea13b48ced 0t0 TCP localhost:57054->localhost:26164 (ESTABLISHED)

Finder 211 stig 7u IPv4 0xaae910ea067284d5 0t0 TCP localhost:57056->localhost:26164 (ESTABLISHED)

Finder 211 stig 16u IPv4 0xaae910ea13b48ced 0t0 TCP localhost:57054->localhost:26164 (ESTABLISHED)

Finder 211 stig 17u IPv4 0xaae910ea064b24d5 0t0 TCP localhost:57057->localhost:26164 (ESTABLISHED)

[...]

Finder 211 stig 202u IPv4 0xaae910ea064b54d5 0t0 TCP localhost:57175->localhost:26164 (ESTABLISHED)

Finder 211 stig 203u IPv4 0xaae910e9f87964d5 0t0 TCP localhost:57410->localhost:26164 (ESTABLISHED)

Finder 211 stig 204u IPv4 0xaae910ea06738ced 0t0 TCP localhost:57408->localhost:26164 (ESTABLISHED)

Finder 211 stig 209u IPv4 0xaae910e9f87964d5 0t0 TCP localhost:57410->localhost:26164 (ESTABLISHED)

I don't know but I don't think Dropbox should use so many TCP connections - unfortunately I rebooted my Mac at home today so I can't compare.

But all of a sudden Spotify and the Cisco VPN adapter started to act up, and it all returned to normal once I relaunched Dropbox and restarted (killall) Finder...

Dec 10, 2013 6:42 AM in response to StigBull

interisting, StigBull - yes, I am using DropBox on both of my machines. But, I've been up for 14 days and only have 4 TCP connections attributed to my DropBox proc id.

My network connection completely died - "failed: 49 - Can't assign requested address"