Page 2 of 5

Re: Update issue with NNA

Posted: Mon Jan 18, 2016 3:27 pm
by snapon_admin
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

Posted: Mon Jan 18, 2016 5:13 pm
by tgriep
Can you post the following files?

Code: Select all

/etc/hosts
/etc/yum.conf
/etc/yum.repos.d/epel.repo
Also, run this as root and post the output.

Code: Select all

ip addr
It kind of looks like an IPv6 issue.

Re: Update issue with NNA

Posted: Mon Jan 18, 2016 5:21 pm
by snapon_admin

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
I agree, feels like IPv6 issue, but not sure why it would be. I've updated this server before without this issue.

Re: Update issue with NNA

Posted: Mon Jan 18, 2016 6:48 pm
by Box293
Is stuff resolving correctly?

Code: Select all

nslookup mirrorlist.centos.org
nslookup www.google.com

Re: Update issue with NNA

Posted: Tue Jan 19, 2016 12:38 pm
by snapon_admin
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

Posted: Tue Jan 19, 2016 2:33 pm
by rkennedy
The ipv6 DNS results may be the culprit, try this to disable ipv6 -

Code: Select all

echo 1 > /proc/sys/net/ipv6/conf/all/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

proxy=http://ip:port

Re: Update issue with NNA

Posted: Tue Jan 19, 2016 3:09 pm
by snapon_admin

Code: Select all

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6
did not change anything. This particular VLAN does not go through our proxy but for good measure I added it into yum anyway and it also did not work.

Re: Update issue with NNA

Posted: Tue Jan 19, 2016 5:33 pm
by tgriep
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

Re: Update issue with NNA

Posted: Wed Jan 20, 2016 9:23 am
by snapon_admin
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

Posted: Wed Jan 20, 2016 12:59 pm
by tgriep
Can you post this file?

Code: Select all

/etc/yum.repos.d/CentOS-Base.repo
Try running the yum update in verbose mode to see if there is any error information that could help out.

Code: Select all

yum update -v