Issue with updating NNA...again

This support forum board is for support questions relating to Nagios Network Analyzer, our network traffic and bandwidth analysis solution.
User avatar
eloyd
Cool Title Here
Posts: 2190
Joined: Thu Sep 27, 2012 9:14 am
Location: Rochester, NY
Contact:

Re: Issue with updating NNA...again

Post by eloyd »

This is the first post you've mentioned IPv6. Could that be an issue?
Image
Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoyd
I'm a Nagios Fanatic! • Join our public Nagios Discord Server!
User avatar
snapon_admin
Posts: 952
Joined: Mon Jun 10, 2013 10:39 am
Location: Kenosha, WI
Contact:

Re: Issue with updating NNA...again

Post by snapon_admin »

The only reason I mention IPv6 is because the address in the error I get when running this without a proxy looks like an IPv6 address (2001:4178:5:200::10). This is the first post in this thread that I mentioned IPv6, but it was a pretty main topic in the previous thread where I had this issue. No, I do not believe that IPv6 is the issue, or at least if it is the issue then it makes zero sense. We are not using IPv6 and, near as I can tell, IPv6 is 100% disabled on my NNA server. And believe me, I've tried every method of disabling IPv6 that I've come across so if it is still enabled then there is something seriously wrong with CentOS and its network settings.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Issue with updating NNA...again

Post by tgriep »

From what I have been reading, if yum cannot connect to the servers using IPv4, it then tries to use IPv6 and if it cannot connect using IPv6, it prints the IPv6 address in the error.
All I can add is that something is blocking access to Centos's server using IPv4.
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
snapon_admin
Posts: 952
Joined: Mon Jun 10, 2013 10:39 am
Location: Kenosha, WI
Contact:

Re: Issue with updating NNA...again

Post by snapon_admin »

So I went to that URL in my browser on my PC (both from behind the proxy and not) and was able to get to it fine. I also noticed the list of URLs it presents all refer to CentOS 6.9.

Code: Select all

http://mirrors.cat.pdx.edu/centos/6.9/os/x86_64/
http://dist1.800hosting.com/centos/6.9/os/x86_64/
http://ftp.osuosl.org/pub/centos/6.9/os/x86_64/
http://mirror.web-ster.com/centos/6.9/os/x86_64/
http://mirrors.syringanetworks.net/centos/6.9/os/x86_64/
http://centos.vwtonline.net/centos/6.9/os/x86_64/
http://mirrors.usc.edu/pub/linux/distributions/centos/6.9/os/x86_64/
http://mirror.mojohost.com/centos/6.9/os/x86_64/
http://mirror.nodesdirect.com/centos/6.9/os/x86_64/
http://mirror.net.cen.ct.gov/centos/6.9/os/x86_64/
I'm not sure if it's related, but could this issue be because my server is on CentOS 6.7?
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Issue with updating NNA...again

Post by tgriep »

It should not matter that you are running Centos 6.7, your other system is probably running a newer release of Centos.
Try running this as root on the NNA server and post the output.

Code: Select all

curl -4 http://mirrorlist.centos.org -v
If it works, it should print the following on the last line.

Code: Select all

Invalid release
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
snapon_admin
Posts: 952
Joined: Mon Jun 10, 2013 10:39 am
Location: Kenosha, WI
Contact:

Re: Issue with updating NNA...again

Post by snapon_admin »

Nah, just getting connection refused errors.

Code: Select all

[root@lisl-ngna-01-pv nagiosna]# curl -4 http://mirrorlist.centos.org -v
* About to connect() to mirrorlist.centos.org port 80 (#0)
*   Trying 212.69.166.138... Connection refused
*   Trying 216.176.179.218... Connection refused
*   Trying 67.219.148.138... Connection refused
*   Trying 85.236.43.108... Connection refused
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Issue with updating NNA...again

Post by tgriep »

Well, it looks like something is blocking the connection and you will have to investigate further.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked