Nagios Support Forum

aptmis wrote:< HTTP/1.1 302 Found
< Server: squid/4.0.14-BZR
< Date: Mon, 26 Mar 2018 12:58:39 GMT
< Content-Length: 0
< Location: http://APTiPrism.AF.Local:80/auth-bin/n ... 2s%3d&PM=1
< X-Cache: MISS from 10.100.0.2
< X-Cache-Lookup: MISS from 10.100.0.2:3128
< Connection: keep-alive

This is a squid proxy... Please attach your /etc/yum.conf

And make sure you have followed the following as previously suggested
https://support.nagios.com/kb/article.php?id=147

here is the response of /etc/yum.conf

[root@nagios ~]# /etc/yum.conf
-bash: /etc/yum.conf: Permission denied
[root@nagios ~]#

I didn't want you to execute it, I wanted you to send the contents of the file.

Here is the content of the file, hope we can come to some solution soon. This is now truly getting frustrating!!!
************************************************************************
[root@nagios ~]# vi /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? ... tegory=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
~
"/etc/yum.conf" 25L, 969C

This is only the first 25 lines of the file
please run the following and post the whole content

I tried, but this is the only results I got:

[root@nagios ~]# 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? ... tegory=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@nagios ~]#

how about run these instead

[root@nagios ~]# cat /etc/yum.conf|grep proxy
[root@nagios ~]# echo $https_proxy

[root@nagios ~]# echo $http_proxy

[root@nagios ~]#

Do you have a system or network admin that can help answer the question why your network traffic is being re-directed through this?

aptmis wrote:

Code: Select all

< HTTP/1.1 302 Found
< Server: squid/4.0.14-BZR
< Date: Mon, 26 Mar 2018 12:58:39 GMT
< Content-Length: 0
< Location: http://APTiPrism.AF.Local:80/auth-bin/n ... 2s%3d&PM=1
< X-Cache: MISS from 10.100.0.2
< X-Cache-Lookup: MISS from 10.100.0.2:3128
< Connection: keep-alive

Without that stopping, there isn't anything else I can help with.

This is our Content filtering security appliance and while no changes have been made, this setup was working since the first day of Nagios Installation. I have done many updates since then. Can you please provide me a list of URLS I need to be concerned about.