Page 4 of 5
Re: Update issue with NNA
Posted: Mon Jan 25, 2016 12:05 pm
by snapon_admin
It really does, but it definitely isn't. Also, hilariously enough, this server now DOES go through our proxy. There was maintenance this weekend to re-route all the servers on this particular VLAN through the proxy so, I am now using the proxy. I updated my yum.conf and wgetrc files with the proxy info and still getting the same issue. Disclaimer: I also tried it again without the proxy to verify that wasn't the issue. With proxy off I get a "cannot reach host" error, with proxy off I get the "Error: Cannot retrieve metalink for repository: epel" error. So it's the same as before just with the proxy on/off situations reversed since this is now using the proxy.
Re: Update issue with NNA
Posted: Mon Jan 25, 2016 4:22 pm
by tgriep
Can you run the following 2 commands on the NA server and post the output?
Code: Select all
wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -4
wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -6
Thanks
Re: Update issue with NNA
Posted: Mon Feb 01, 2016 11:10 am
by snapon_admin
Sorry, was out all week last week.
With Proxy
Code: Select all
[root@lisl-ngna-01-pv nagiosna]# wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -4
Setting --inet4-only (inet4only) to 1
DEBUG output created by Wget 1.12 on linux-gnu.
--2016-02-01 10:08:02-- http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml
Resolving iproxyweb03.snapon.com... 208.65.151.192
Caching iproxyweb03.snapon.com => 208.65.151.192
Connecting to iproxyweb03.snapon.com|208.65.151.192|:8080... Closed fd 3
failed: Connection refused.
Releasing 0x0000000002182ad0 (new refcount 1).
[root@lisl-ngna-01-pv nagiosna]# wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -6
Setting --inet6-only (inet6only) to 1
DEBUG output created by Wget 1.12 on linux-gnu.
--2016-02-01 10:09:20-- http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml
Resolving iproxyweb03.snapon.com... failed: Name or service not known.
wget: unable to resolve host address â€iproxyweb03.snapon.comâ€
Without proxy:
Code: Select all
[root@lisl-ngna-01-pv nagiosna]# wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -4
Setting --inet4-only (inet4only) to 1
DEBUG output created by Wget 1.12 on linux-gnu.
--2016-02-01 10:07:40-- http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml
Resolving centos.host-engine.com... 204.45.61.34
Caching centos.host-engine.com => 204.45.61.34
Connecting to centos.host-engine.com|204.45.61.34|:80... Closed fd 3
failed: Connection refused.
Releasing 0x0000000001dbb8f0 (new refcount 1).
[root@lisl-ngna-01-pv nagiosna]# wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d -6
Setting --inet6-only (inet6only) to 1
DEBUG output created by Wget 1.12 on linux-gnu.
--2016-02-01 10:10:26-- http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml
Resolving centos.host-engine.com... 2001:49f0:a023:1::5
Caching centos.host-engine.com => 2001:49f0:a023:1::5
Connecting to centos.host-engine.com|2001:49f0:a023:1::5|:80... Closed fd 3
failed: Network is unreachable.
Releasing 0x0000000002145900 (new refcount 1).
Re: Update issue with NNA
Posted: Mon Feb 01, 2016 2:59 pm
by ssax
DNS isn't resolving?
Code: Select all
Resolving iproxyweb03.snapon.com... failed: Name or service not known.
Set the IP for your proxy manually in your /etc/hosts file or investigate why DNS isn't working.
I just dealt with this
exact issue 5 minutes ago and it was the proxy that was blocking HTTPS, the IPv6 was not the problem.
Re: Update issue with NNA
Posted: Fri Feb 05, 2016 2:05 pm
by snapon_admin
Nothing seems to have changed, maybe I did it wrong?
Code: Select all
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
XXX.XXX.XXX.XXX iproxyweb03.snapon.com
Re: Update issue with NNA
Posted: Fri Feb 05, 2016 2:35 pm
by tgriep
Can you login as root in one shell and run a tcpdump command like below
Code: Select all
tcpdump host centos.host-engine.com -w capture.cap
Then in another shell on the server, run the following
Code: Select all
wget http://centos.host-engine.com/6.7/os/x86_64/repodata/repomd.xml -d
After the wget command is done, stop the tcpdump and post the capture.cap so we can review it.
Re: Update issue with NNA
Posted: Fri Feb 05, 2016 2:49 pm
by snapon_admin
Don't have tcpdump installed on the NA server and can't get it because of this issue. Also, I checked my XI server and there is no proxy info in /etc/wgetrc, just in the yum.conf. Not sure if that means anything but figured I'd include that info here as well.
Re: Update issue with NNA
Posted: Fri Feb 05, 2016 3:10 pm
by tgriep
Can you take the proxy settings that are in the XI server's yum.conf file, add them to the NA's server yum.conf file and see if you can do an update?
Re: Update issue with NNA
Posted: Fri Feb 05, 2016 3:25 pm
by snapon_admin
Yeah I already did that, the 2 servers' yum.conf files are identical.
Re: Update issue with NNA
Posted: Mon Feb 08, 2016 10:12 am
by ssax
What do you have for your hosts entry in /etc/nsswitch.conf?