972393 - OSX 10.9.1 fails to make any additonal network connections: "Can't assign requested address"

Status: RESOLVED WORKSFORME

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[Andrei Eftimie]

We can't access https://ftp.mozilla.org/ on mm-osx-109-1.

We're failing to retrieve any Firefox build:
> 04:51:15   INFO | Retrieving list of builds from https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/02
> 04:51:15   WARNING | Build not found: 'HTTPConnectionPool(host='proxy.dmz.scl3.mozilla.com', port=3128): Max retries exceeded with url: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/02 (Caused by <class 'socket.error'>: [Errno 49] Can't assign requested address)'


I've tried reaching ftp.mozilla.org over http, https and ftp.
The server does respond to ping.

I'll check if the proxy settings are correct.

Comment 1

[Andrei Eftimie]

I've updated the proxy settings, restarted the machine and all appears to work fine now.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andrei, you should at least tell, what was wrong with the proxy settings. Just saying I have updated them is not enough. Thanks.

Comment 3

[Andrei Eftimie]

I have actually no idea what was wrong.

I've only done a couple of things:
(used the mana docs)
1) check /etc/profile that it has the correct entries (it did)
2) used the `networksetup` commands as they are laid out (I didn't find a quick/easy way to checking their output, so I just run the commands the set them up)

At this time the proxy setting still weren't working as expected.
3) I rebooted the machine. After which all was working correctly.

It could very well be that the machine only needed rebooting.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

In such a case you should:

* check the current environment variables
* go into the network preferences and check the networking setup

It's not good when we do NOT check what's wrong. It could cause further problems in the future, given that we might not know the underlying issue and the situation which caused this misbehavior. If a fix takes longer, take the node offline for deeper investigation. But please no hasty fixes.

For this time and reading your statement, I think the environment variables were simply broken.

Comment 5

[Andrei Eftimie]

This hit all 10.9 boxes

We are keeoing mm-osx-109-3 offline to investigate further.
Restarted both mm-osx-109-2 and mm-osx-109-4 should fix the issue.

This might be a bug in OSX.
See some discussions about it:
https://discussions.apple.com/thread/5551686?start=45&tstart=0

People are suggesting this might get fixed in 10.9.3

We don't know yet the underlying cause.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

The last reboot of this machine was:

$ last reboot
reboot    ~                         Tue Jan  7 23:22

So it's 5 weeks ago. 

Regarding a fix, as listed in the thread it will be 10.9.2 and not 10.9.3.

I finally killed the network connections. :/ Now I have to request IT to restart it.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Apple released the 6th beta about 4 days ago. So hopefully the RC and the final release shouldn't take that long. I will take this bug and upgrade the OS X machines, once the update is available.

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Andrei Eftimie from comment #5)
> See some discussions about it:
> https://discussions.apple.com/thread/5551686?start=45&tstart=0

No-one in this thread has been reported yet if that has been fixed for 10.9.2. Given that I upgraded to that version yesterday we should keep an eye on those boxes, and re-check this bug in about a month. If it still happens we will have to wait for the next update.

Comment 9

[Livid]

I can confirm this problem is still occurring on OS X 10.9.2, I have to reboot my Mac mini server today. Last reboot was for installing 10.9.2 (in hope it contains fix for the problem), so uptime is from Feb 25 to Mar 14 (PST).

Here is a pic I took:

http://i.v2ex.co/4Y3QVfdY.png

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+1]]

This is really sad to hear. Looks like we have to wait for another round of updates. Lets hope it will be included in 10.9.3 then.

Comment 11

[Livid]

Since we have been suffering this for months, I just submitted it as a serious bug on Apple's bug reporting website. Bug ID: 16330153

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We haven't seen this problem anymore in the last 2 months. Maybe it has been silently fixed? Lets close as WFM for now, and lets reopen if it comes back.