---- Starting Nagios XI Upgrade ----
Cleaning up temp directory...
No entry for terminal type "unknown";
using dumb terminal settings.
No entry for terminal type "unknown";
using dumb terminal settings.
Archive: sourceguardian/ixed4.lin.x86-32.zip
inflating: /usr/lib/php/modules/ixed.5.3.lin
Sourceguardian extension found for PHP version 5.3
Sourceguardian extension already in php.ini
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
No entry for terminal type "unknown";
using dumb terminal settings.
Checking required prereqs...
Please wait...
OLD VERSION: 5411
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=i386 error was
14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrors.fedoraproject.org'"
* base: mirror.vcu.edu
* epel: mirrors.mit.edu
* extras: mirror.cc.columbia.edu
* updates: mirrors.lga7.us.voxel.net
http://dl.google.com/linux/chrome/rpm/stable/x86_x64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: google-chrome. Please verify its path and try again
It looks like there could be a stale yum cache entry causing yum to not run. Lets clear it out and see if the upgrade finishes.
Run this as root on the server.
The new error suggests that you have to edit the /etc/yum.repos.d/epel.repo file on the server and adjust the path to EPEL's server list.
The following link has instructions for the changes that have to be done. https://stackoverflow.com/questions/267 ... y-its-path
If you still get the error after the change, post the file so we can view it.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: google-chrome.
@hillhealthcenter, You still have a google-chrome repository that fails to update. I recommend to just disable it for a while. On my system CentOS i'd go to the /etc/yum.repos.d/ folder, then open a google-chrome repository with a text editor and change enabled 1 to enabled 0. Then please run yum clean all and yum update one more time.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.