Upgrade failing for 2011 Upgrade

[[email protected]]

What version of Nagios XI are you using? Nagios XI 2009R1.1H
Linux Distribution and version? CentOS release 5.4
32 or 64bit? 32 bit
VMware Image or Manual Install of XI? vmware image

I am in the middle of upgrading from the version you see above to the 2011 version as recommended in a previous thread. The install has exited with the following error:

skipping: http://download.fedora.redhat.com/pub/e ... noarch.rpm - transfer failed - unknown or unexpeted error

I suspect that the rpm is no longer there, but I am not sure where to access the necessary rpms if they are not there. Any help would be appreciated.

[abrist]

What is in the directory:

Code: Select all

ls -la /tmp/nagiosxi/packages

[[email protected]]

[root@incentive packages]# ls -tla
total 228
drwxrwxrwx 9 root root 4096 Nov 8 12:57 ..
drwxrwxrwx 2 root root 4096 Aug 22 2012 .
-rwxrwxrwx 1 root root 90613 Aug 20 2012 Ajaxterm-0.10-8.el5.noarch.rpm
-rwxrwxrwx 1 root root 12232 Aug 20 2012 epel-release-5-4.noarch.rpm
-rwxrwxrwx 1 root root 14064 Aug 20 2012 epel-release-6-5.noarch.rpm
-rwxrwxrwx 1 root root 31031 Aug 20 2012 php-pear-HTML-Template-IT-1.3.0-2.el5.noarch.rpm
-rwxrwxrwx 1 root root 12680 Aug 20 2012 rpmforge-release-0.5.2-2.el5.rf.i386.rpm
-rwxrwxrwx 1 root root 12649 Aug 20 2012 rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
-rwxrwxrwx 1 root root 12732 Aug 20 2012 rpmforge-release-0.5.2-2.el6.rf.i686.rpm
-rwxrwxrwx 1 root root 12700 Aug 20 2012 rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
[root@incentive packages]#

[yancy]

Can you post what version of Python you're running on this machine.

Code: Select all

python -V

-Yancy

[[email protected]]

[root@incentive packages]# python -V
Python 2.4.3
[root@incentive packages]#

[scottwilkerson]

Actually, you should go straight to 2012.

It is highly likely that the old upgrade script in the 2011 tarball doesn't function any longer as it relied on external resources that have since been moved...

[[email protected]]

Actually, you should go straight to 2012.

It is highly likely that the old upgrade script in the 2011 tarball doesn't function any longer as it relied on external resources that have since been moved...

upgrade completed to 2012. Please lock thread.