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

Mar 10, 2014 4:20 PM in response to Locomotivation

Get to 10.9.2!

Mar 11, 2014 5:10 AM in response to Wil Shipley

Is your reply on-topic?

Do you know with confidence that it resolves THIS ISSUE?

I fully realize the implications of being at 10.9.1, thank you.

Mar 11, 2014 2:23 PM in response to Locomotivation

Yes, and yes.

trisweb

Level 1

0 points

Mar 11, 2014 2:38 PM in response to Locomotivation

Just so ya know, Wil is a legit OSX developer. My guess is he probably got the assist on tracking this down. I'd trust him.

Thanks Wil!

刘昕

Level 1

0 points

Mar 14, 2014 1:22 PM in response to StigBull

No, I can confirm the problem is still occurring on 10.9.2, I took this screenshot an hour ago before I have to reboot my Mac mini server:

Larger version of this pic: http://i.v2ex.co/4Y3QVfdY.png

Mar 15, 2014 3:14 PM in response to trisweb

Still happens with 10.9.2, so Wil's post, whatever the intents, is useless right now.

Does anyone know if this issue has a bug id assigned already?

EDIT: filed as bug id 16336220.

Message was edited by: _-PeterP-_

Mar 15, 2014 6:00 PM in response to _-PeterP-_

My original RADAR for this is rdar://15798027, which was marked as a dup of rdar://16022720 (which is assumedly everyone's parent).

PeterP, to be clear, did you also see this crash under 10.9.2, or are you just talking about 刘昕's worrisome post?

I'm detecting a little hostility here. Let me try to explain myself: the correspondence with Apple inside of RADARs is considered under NDA. As such, it'd be a violation of an agreement I signed for me to say in a public forum if Apple has told me if a bug is fixed or not. It'd also be a violation if I had any external communication (like, if I spoke with the engineers) with Apple and I posted that I had done so here. (In this case I actually did NOT speak with the engineers themselves, to be clear, I'm just positing.)

ALL I can say is, "I think this is fixed in 10.9.2," if I have a reason, SOME reason, to believe it is. I'm not sure what other "intents" you think I have here. I don't post for my health, I'm trying to help people.

Obviously, I can't promise my information is accurate. ****, lots of times I think bugs are fixed in MY programs, and they're not, so I certainly can't vouch for Apple! I can just say, "I *THINK* it's fixed in 10.9.2."

-Wil

Mar 15, 2014 5:51 PM in response to 刘昕

刘昕, did you file a RADAR on this? I'd like to refer to it if you could post the number.

刘昕

Level 1

0 points

Mar 15, 2014 6:07 PM in response to Wil Shipley

Yes I do have.

ID: 16330153

Mar 17, 2014 2:53 PM in response to Wil Shipley

Wil,

while I appreciate your posts, without confirming that the issue is really fixed, the added value of your posts is exactly ZERO. Getting to 10.9.2 does not help and your post 'yes and yes' is actually false.

I did not yet have enough connections hung, but I am getting close (think the numbers for the third command were around 2200 last time):

user@host ~ $ netstat -an | egrep "^tcp|^udp" | wc -l

2030

user@host ~ $ netstat -an | egrep "^tcp|^udp" | egrep -vc "FIN_WAIT_1|LAST_ACK"

144

user@host ~ $ netstat -an | egrep "^tcp|^udp" | egrep -c "FIN_WAIT_1|LAST_ACK"

1887

user@host ~ $

Peter

Mar 17, 2014 3:21 PM in response to _-PeterP-_

I had reason to believe it was fixed. There was no way for me to confirm it myself because it hasn't even been 20 days since I upgraded to 10.9.2, and my machine only crashed every 20 days.

trisweb

Level 1

0 points

Mar 17, 2014 3:28 PM in response to Wil Shipley

For an contrary bit of anecdotal evidence, my netstat -an is extremely clean now after 14 days uptime on 10.9.2 (Early 2010 Mac Mini).

netstat -an | egrep "^tcp|^udp" | egrep -c "FIN_WAIT_1|LAST_ACK" for me gives 0.

So far so good. I'll continue monitoring.

Mar 20, 2014 1:31 PM in response to trisweb

Ok folks, it's been 21 days since the install on 10.9.2, and it' sharpened again on my Mac Mini server.

1900+ tcp connections, the vast majority of which are in FIN_WAIT_1. About a hundred in CLOSE_WAIT and 60 in FIN_WAIT_2. It has been a while since anything odd happened, so it took me a day to realize the initial symptom in my case was that mail rules processing had stopped working. (I have a POP account which forwards selected messages to my local Mavericks mail server, and the messages which should have been filtered out of this stream started showing up on my iOS devices.)

Again, the only way out has been a reboot. Not really so inconvenient every three weeks, but annoying. The three week interval (22 days and 27 minutes) is weird. You would think this would be tied to the number of connections or a specific IP or application, but it doesn't look like it.

Rebooted, all is again well.

Doug

Mar 20, 2014 1:37 PM in response to doug_blair

That should have been "it's happened again," not "it sharpened." Gotta love that auto-speller ...

Mar 20, 2014 3:10 PM in response to doug_blair

Interestingly enough I am at 18 days and my numbers look good.

$ netstat -an | egrep "^tcp|^udp" | egrep -c "FIN_WAIT_1|LAST_ACK"

$ netstat -an | egrep "^tcp|^udp" | egrep -vc "FIN_WAIT_1|LAST_ACK"

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