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.

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

Reply
158 replies

Nov 12, 2013 5:10 PM in response to StigBull

Same issue here on the same machine (Mid 2012 15" Retina MBP). I tried various methods to

restore the system before giving up and rebooting.


Whats interesting is netstat took forever to print out active connections and was filled with

LAST_ACK and FIN_WAIT_1 entries. Ping worked, nslookups worked, but no new tcp/udp

sockets could be created. From the looks of it Mavericks is failing to cleanup sockets when

they are closed. I will periodically check netstat and see if this is a chronic issue or just

a transient error. If it keeps showing up I will open a bug report with Apple and see if they

can figure out what is going wrong.

Nov 12, 2013 11:25 PM in response to Nate12

I noticed the same too and I also suspected it ran out of sockets.


I think I had ~4K sockets in netstat. However I forgot to take a copy of the netstat status before I rebooted.


I did also notice that a ton of open sockets were to localhost, however this could be normal for all I know.


If it happens again, I'll try lsof on the ports that won't close and see which application is keeping them in a hung state.


Do you know of any util that one can force close them with?

Nov 14, 2013 6:26 PM in response to StigBull

It appears I have the same issue, it has happened twice now. Once on my Work Mac Mini, and once on my personal Mac Mini.


So far I haven't been able to figure out what is going on. Interestingly enough IPv6 continues to function without issues, so I was able to browse Facebook/Google and various other sites, but as soon as I landed on a IPv4 only website (Apple get with the program!) it wouldn't load.


Eventually I just gave in and restarted, downside is that now I get to rebuild all of my open programs and terminals to get back to developing!

Nov 18, 2013 9:34 AM in response to StigBull

Same issue here, happened twice on the same Mac Mini.


2013-10-05: upgraded to 10.9

2013-10-30: first time happened

2013-11-18: second time


So it looks, that it takes about 20-25 days of uptime for the problem to appear on my system (it probably highly depends on the network usage, i.e. torrents, websurfing and whatnot).

Nov 18, 2013 11:23 AM in response to StigBull

I get this issue, too. Spent some time trying to see if there was a way I could manually drop connections, but seems there isn't a built-in way to do it on OSX (BSD has one; tcpdrop).

Netstat shows a lot of FIN_WAIT1, and LAST_ACK.

Interestingly, lsof doesn't show these connections, and as mentioned, ping, nslookup, and traceroute still work.


Also worth mentioning that a lot of these connections originate from a LAN IP that I no longer have. It may be related to sleeping with active connections and then changing wifi locations (This is on a retina macbook pro). Probably not applicable to Mac minis, but it might be important.

Nov 20, 2013 10:23 AM in response to StigBull

Running a Mac Pro 2010 here on 10.9 and I believe this just happened to me as well.


Could't load any sites in Safari or Chrome. Most mail connections dead. But like the OP, I could ping sites and DNS was resolving.


What's weird was my Adium connection was still up.


A logout/login didn't fix. A reboot of Airport didn't fix. Only a system reboot fixed the issue.


Honestly I can't remember when I last rebooted the system.


Anyone know a way to find out when the last reboot was? System logs only go back a week. Maybe some obscure log file that would have an entry?


EDIT:

Looking in the daily.out log, today's entry listed:

6:40 up 20 days, 12 hrs, 1 user, load averages: 0.41 0.52 0.50


So it seems to correspond with the issues starting after 20 days of uptime.


-Kevin


Message was edited by: netnothing

Nov 20, 2013 3:20 PM in response to mmarionsd1

Knew about uptime, but since I rebooted before finding this thread that wasn't going to help.


I did not know about "last reboot". That's cool....thanks!


It does confirm my uptime line I found in daily.out:


$ last reboot

reboot ~ Wed Nov 20 13:06

reboot ~ Wed Oct 30 19:40

reboot ~ Sun Oct 27 18:31

reboot ~ Sun Oct 27 18:26

reboot ~ Sun Oct 27 16:33

reboot ~ Sun Oct 27 15:51

reboot ~ Sun Oct 27 15:50

reboot ~ Tue Oct 22 22:21

reboot ~ Tue Oct 22 20:25

reboot ~ Tue Oct 22 19:59

reboot ~ Tue Oct 22 19:15



So clearly something with having a system up for ~20 days. I wonder if it's solid uptime or system uptime? My Mac Pro is on 24x7.....but my MacBook Air is usually asleep. I currently have an uptime on the Air of 15 days....so I guess in a week we'll see!


But based on previous posts, I also wonder if it has to do with overall traffic over that time as well.


-Kevin

Nov 20, 2013 3:22 PM in response to Nate12

Hmm.. I just found this thread looking for why I was seeing the same thing. This is on an iMac that's powered on 24/7.


The first signs I've been noticing are that my AppleTV has been acting odd when talking to it. Nevery every other time I'd start playback on a new movie or TV show, it would do the little pinwheel until I backed out, then restarted. Then I just saw today that the end of a file would sometimes fall back 2 or 3 levels instead of just back to the TV episode list. Then the Artwork wasn't loading in the listing. Even rebooting the aTV didn't help.


Looked at the iMac found the same situation you're all describing.


I got counts with % and saw less then the 4k counts some are seeing but counts like:

migimac(OSX) ~ {708}$ netstat -n | egrep '^(tcp|udp)' | awk '{print $NF}' | psort

0.2710% 1 SYN_SENT

0.5420% 2 CLOSING

1.3550% 5 ESTABLISHED

2.1680% 8 SYN_RCVD

10.5691% 39 FIN_WAIT_1

11.3821% 42 *.*

73.7127% 272 LAST_ACK

Total: 369


The connections to this ipv6 addr I don't recognize are odd too...

migimac(OSX) ~ {711}$ netstat -l

Active Internet connections

Proto Recv-Q Send-Q Local Address Foreign Address (state)

tcp4 0 0 migimac.miguelit.rfb 192.168.1.101.49437 ESTABLISHED

tcp6 0 820 migimac.local.daap fe80::18ec:dc40:c836:4511%en0.50694 FIN_WAIT_1

tcp6 0 220 migimac.local.daap fe80::18ec:dc40:c836:4511%en0.50691 FIN_WAIT_1


Odd that it's daap too.. It's possible my aTV is getting an IPv6 addr from my new router that's taking precedence for some reason.

Nov 21, 2013 8:35 AM in response to StigBull

Make sure to thumbs the first post if you have the issue so we can get more eyes on this. It's a pretty serious issue if the OS doesn't release sockets.


FWIW, I also tried forcing TCP keepalive timeouts, but it didn't seem to have any affect. Does anyone know if you have to restart for those settings to take? Or if there are global minimums that are enforced for related values?

Nov 25, 2013 3:51 AM in response to stackman_dx

> Or if there are global minimums that are enforced for related values?


I'd look at "sysctl" settings.

It'd be great if someone would make diff of mavericks and pre-mavericks settings and post it here.


For example, keepidle is 2 hours, isn't it too much?

net.inet.tcp.keepidle: 7200000

Probably not, if it's the same as linux's net.ipv4.tcp.keepalive_time, which is also 2 hours by default on my debian system.

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

I had this same issue happen, on my computer at home about a week ago and on my work computer today. My uptime here at work was 31 days, but if it's that Mavericks is not releasing sockets when it should I would suspect that the length of time would be related to how much network activity is occurring that opens sockets.


Like the OP, I had no trouble pinging during this time being down. Hope this issue gets noticed and fixed soon as it's a pretty big deal since if you don't know to look in the console to troubleshoot it just looks like your internet (or network in general) has died.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.