Nagios Support Forum

Posted: **Mon Sep 16, 2019 3:08 pm**

We get that refused again. Alright, let's try this command.

curl -vvv "https://repo.nagios.com"

Maybe that will give us a better clue as to where the interruption is happening.

Posted: **Mon Sep 16, 2019 3:21 pm**

The output is:
[root@nagiosxi ~]# curl -vvv "https://repo.nagios.com"
* About to connect() to repo.nagios.com port 443 (#0)
* Trying 72.14.181.71...
* Connection refused
* Trying 2600

:f03c:91ff:fedf:b821...
* Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable
* Failed connect to repo.nagios.com:443; Network is unreachable
* Closing connection 0
curl: (7) Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable
[root@nagiosxi ~]#

Posted: **Mon Sep 16, 2019 3:35 pm**

Okay, still refused, with no additional information. About the best we can do is check on our side to see if your https requests are getting to us. If you can give us the public IP that your server would be coming from, we will search our access and error logs on our side to see if the request is making it to us. You may want to PM the public IP to me, rather than posting it here.

Code: Select all

curl http://api.ipify.org

That doesn't use https, so we shouldn't run into a problem of the connection being refused.

Posted: **Mon Sep 16, 2019 4:07 pm**

Okay, we checked on our side, we see some activity from that IP. Let's try changing up your yum repo.

Edit the file /etc/yum.repos.d/nagios-7.repo and find the baseurl= lines. If they aren't already, make sure those are set to https, rather than http. Then try the yum update again.

If that fails, we'll try disabling IPv6.

Edit /etc/sysctl.conf and add the following entries,

Code: Select all

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

Save the file, and then run

Code: Select all

sysctl -p

Then try the yum update once more.

Posted: **Mon Sep 16, 2019 4:27 pm**

Here is nagios output:
[root@nagiosxi etc]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 12 kB 00:00:00
* base: mirror.ash.fastserv.com
* epel: mirror.compevo.com
* extras: mirror.cs.pitt.edu
* updates: mirror.teklinks.com
base | 3.6 kB 00:00:00
extras | 3.4 kB 00:00:00
mcp | 2.5 kB 00:00:00
https://repo.nagios.com/nagiosxi-deps/7 ... repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable"
Trying other mirror.
https://repo.nagios.com/nagiosxi-deps/7 ... repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable"
Trying other mirror.

One of the configured repositories failed (Nagios),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=nagios-base ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable nagios-base
or
subscription-manager repos --disable=nagios-base

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=nagios-base.skip_if_unavailable=true

failure: repodata/repomd.xml from nagios-base: [Errno 256] No more mirrors to try.
https://repo.nagios.com/nagiosxi-deps/7 ... repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable"
https://repo.nagios.com/nagiosxi-deps/7 ... repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2600

:f03c:91ff:fedf:b821: Network is unreachable"
[root@nagiosxi etc]#

Posted: **Tue Sep 17, 2019 3:38 pm**

Alright, last thing I can think to try. Let's get a packet capture.

Code: Select all

tcpdump -w output.pcap host 72.14.181.71 &

That will give you a process ID, copy it now and hang on to it.

Code: Select all

curl -vvv "https://repo.nagios.com"

That will give you the output that you've been getting.

Code: Select all

kill <processID>

Kill the process ID you copied earlier.

You should now have a file called output.pcap. If you could PM that over to me, I will take a look and see what I can find.

Nagios Support Forum

Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try

Re: Nagios XI No More Mirrors to Try