Server stalling on wget at start of update

[KiwiBloke]

Hi,

We are in the process of updating our NagiosXI servers to 2014R1.1.

Our 5th and last server to be upgraded however seems to choke kicking off wget to even pull the update file from assets.nagios.com.

I have checked /etc/yum.conf and /etc/wgetrc to see if a proxy is configured (nope) and have verified that we have a firewall rule to allow the server out to the internet (confirmed)

However wget seems to resolve the domain but then times out. I have checked the configuration of these files with its identical sister server (which updated aok)

Code: Select all

[root@psu4nagiosxi tmp]# wget http://assets.nagios.com/downloads/nagiosxi/xi-latest.tar.gz
--2014-06-24 13:04:01--  http://assets.nagios.com/downloads/nagiosxi/xi-latest.tar.gz
Resolving assets.nagios.com... 72.14.181.71
Connecting to assets.nagios.com|72.14.181.71|:80... failed: Connection timed out.
Retrying.

From there it just loops retrying every 30s

Attached is a screenshot from our firewall (the green circle indicates the traffic has been allowed)

NagiosFW.jpg

I will take this up with our network team, but if anyone has any other suggestions it would be great to hear them.

Cheers,

KB

[KiwiBloke]

Hi,

Our network team is going to check that the server is NAT'd correctly.

I'll update if there is a development.

Cheers,

KB

[slansing]

Sounds good, I'd also look into this here:

http://support.nagios.com/wiki/index.ph ... th_Proxies

[KiwiBloke]

Hi,

It seems the requests are making all to our internal firewall but not being seen on the external firewall.

Packet traces confirm this, but the vendors management tools show nothing.

There is a rule on the external firewall to allow this traffic out.

Thanks for the link, the NagiosXI server is not configured for a proxy and should have direct external access given everything we have checked so far.

We are going to escalate to the firewall vendor this evening.

Cheers,

KB.

[slansing]

Well, if you see packets originating from XI on the next hop over (internal firewall) but they are not making it to your external one, it sounds like you may have a networking issue on that end, which unfortunately we can't do much to help, that would be up to your networking team.

[KiwiBloke]

Hi,

Yes, that's understandable.

I think we are happy that its not the Nagios server at this point and we will escalate to our firewall vendor.

Cheers,

KB

[tmcdonald]

Sounds like a plan. I'll lock this up.