Update issue with NNA
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: Update issue with NNA
Tried that already, no dice. I also noticed the URLs in /etc/yum.repos.d/epel.repo were using http and on my XI server they were https so I changed that, still got the same error.
Re: Update issue with NNA
Can you post the following files?
Also, run this as root and post the output.
It kind of looks like an IPv6 issue.
Code: Select all
/etc/hosts
/etc/yum.conf
/etc/yum.repos.d/epel.repoCode: Select all
ip addrBe sure to check out our Knowledgebase for helpful articles and solutions!
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: Update issue with NNA
Code: Select all
[root@lisl-ngna-01-pv nagiosna]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
[root@lisl-ngna-01-pv nagiosna]# cat /etc/yum.conf
[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://bugs.centos.org/set_project.php?project_id=16&ref=http://bugs.centos.org/bug_report_page.php?category=yum
distroverpkg=centos-release
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
[root@lisl-ngna-01-pv nagiosna]# cat /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux 6 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
[epel-debuginfo]
name=Extra Packages for Enterprise Linux 6 - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch/debug
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-6&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
gpgcheck=1
[epel-source]
name=Extra Packages for Enterprise Linux 6 - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/6/SRPMS
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-source-6&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
gpgcheck=1
[root@lisl-ngna-01-pv nagiosna]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 00:50:56:8d:10:4f brd ff:ff:ff:ff:ff:ff
inet 10.245.128.169/24 brd 10.245.128.255 scope global eth0
inet6 fe80::250:56ff:fe8d:104f/64 scope link
valid_lft forever preferred_lft forever- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Update issue with NNA
Is stuff resolving correctly?
Code: Select all
nslookup mirrorlist.centos.org
nslookup www.google.comAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: Update issue with NNA
Yeah seems good. There's an IPv6 address, but there's also plenty of v4 addresses. I'm also not having this issue on my XI server which is on the same exact network as the NNA server.
Re: Update issue with NNA
The ipv6 DNS results may be the culprit, try this to disable ipv6 -
If it isn't the ipv6, it may be the proxy that yum is attempting to use. Can you also try configuring your proxy in yum by adding this line?
Code: Select all
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
Code: Select all
proxy=http://ip:port
Former Nagios Employee
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: Update issue with NNA
Code: Select all
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6Re: Update issue with NNA
Can you ping and traceroute to that host? Try running this on your NNA server and post the output here.
Code: Select all
ping mirrors.fedoraproject.org -c5
traceroute mirrors.fedoraproject.org
Be sure to check out our Knowledgebase for helpful articles and solutions!
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: Update issue with NNA
Cannot ping and don't have traceroute installed. Not sure how meaningful that is, however, as I also cannot ping that address on my XI server, but don't have this issue on that server.
Re: Update issue with NNA
Can you post this file?
Try running the yum update in verbose mode to see if there is any error information that could help out.
Code: Select all
/etc/yum.repos.d/CentOS-Base.repoCode: Select all
yum update -vBe sure to check out our Knowledgebase for helpful articles and solutions!