Nagios Support Forum

vSphere 5.5 Host is hosting the Nagios 5.3.0 Appliance.
We use a proxy. We think it's working because prior to proxy install, update screen would not connect, now it does.
Attempting to upgrade to 5.4.0 via GUI.
On "Check for Updates" link, we see "Update in Progress" > 24 hrs and no activity in network.
System Profile info:
Nagios XI Installation Profile
System:
Nagios XI Version : 5.3.0
wscrnag01.ams.att.com 2.6.32-642.4.2.el6.x86_64 x86_64
CentOS release 6.8 (Final)
Gnome is not installed
Apache Information
PHP Version: 5.3.3
Agent: Mozilla/5.0 (Windows NT 6.1; rv:50.0) Gecko/20100101 Firefox/50.0
Server Name: 192.111.164.46
Server Address: 192.111.164.46
Server Port: 80
Date/Time
PHP Timezone: America/Los_Angeles
PHP Time: Wed, 18 Jan 2017 11:54:18 -0800
System Time: Wed, 18 Jan 2017 11:54:18 -0800
Nagios XI Data
License ends in:

Days left in Trial: 10

nagios (pid 22051) is running...
NPCD running (pid 1852).
ndo2db (pid 1866) is running...
CPU Load 15: 0.64
Total Hosts: 1
Total Services: 14
Function 'get_base_uri' returns: http://192.111.164.46/nagiosxi/
Function 'get_base_url' returns: http://192.111.164.46/nagiosxi/
Function 'get_backend_url(internal_call=false)' returns: http://192.111.164.46/nagiosxi/includes ... rofile.php
Function 'get_backend_url(internal_call=true)' returns: http://localhost/nagiosxi/backend/
Ping Test localhost
Running:

/bin/ping -c 3 localhost 2>&1

PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.052 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.047 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.044/0.047/0.052/0.008 ms
Test wget To localhost
WGET From URL: http://localhost/nagiosxi/includes/components/ccm/
Running:

/usr/bin/wget http://localhost/nagiosxi/includes/components/ccm/

--2017-01-18 11:54:20-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: "/usr/local/nagiosxi/tmp/ccm_index.tmp"

0K .......... ........ 1.66M=0.01s

2017-01-18 11:54:20 (1.66 MB/s) - "/usr/local/nagiosxi/tmp/ccm_index.tmp" saved [18628]

Network Settings

1: lo: mtu 65536 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: mtu 1500 qdisc pfifo_fast state UP qlen 1000

link/ether 00:50:56:a6:1f:e7 brd ff:ff:ff:ff:ff:ff

inet 192.111.164.46/24 brd 192.111.164.255 scope global eth0

inet6 fe80::250:56ff:fea6:1fe7/64 scope link

valid_lft forever preferred_lft forever


192.111.164.0/24 dev eth0 proto kernel scope link src 192.111.164.46

169.254.0.0/16 dev eth0 scope link metric 1002

default via 192.111.164.3 dev eth0

VMware-Tools installed

We have the image snapshotted so we can shutdown the system, revert to snapshot and try again until we resolve issue.

Thanks,
Joseph Settanni
[email protected]

I always suggest a manual update: https://assets.nagios.com/downloads/nag ... nstall.pdf

Can you give that a shot and let us know if you have problems?

Sounds like a good idea.
I'll try the manual method and get back to you
Thanks,.
Joe

Sounds good - let us know how it goes.

Does not seem like we are downloading the correct file.

That's weird, here's a direct link: https://assets.nagios.com/downloads/nag ... 4.0.tar.gz

Otherwise, the instructions should work.

We have figured out it's an issue of our proxy letting us get to the original URL in the instructions.
I can download the file locally via my browser onto my desktop, then ftp the file up to one of our Linux servers.
Then, we went back into the CentOS image for Nagios Xi and did an scp out to the Nagios machine to grab the file and pull it in.
Then we could run the update with a minor tweak.
tar xzf xi-latest.tar.gz threw off an error on the file, so instead, we did a gunzip xi-latest.tar.gz

Then tar -xvf xi-latest.tar

After that, we could run the ./update from the dir and it ran successfully.

We will probably take advantage of that quickstart offer later this week if time allows to show how we configured the network and proxy and get some feedback.

We are awaiting our license keys so we can move to full support. PO was already cut, just wanting from our internal teams for the updates...

THanks
Joe

Sounds good. Thanks for sharing your solution!

Let is know if you have any additional questions regarding this issue. If there's a delay in the license information, contacting our sales department is the best way to get information/resolution for that issue.

Hey guys,
Small step missing in manual update process. Need to gunzip the .gz file before attempting to untar the .tar file.
On page https://support.nagios.com/kb/article.php?id=134

At this step:
Installing the Updated Version to Nagios XI

Unpack the updated tarball you just downloaded. Note: You will need to change the name to match the file you downloaded if you did not download the latest version.
tar xzf xi-latest.tar.gz


Navigate to the new /tmp/nagiosxi/ subdirectory that was created when you unpacked the tarball:
cd /tmp/nagiosxi


Finally, run the upgrade script:
./upgrade



You should add a step prior to Unpacking as such:

Before you unpack the file, you need to gunzip the file xi-latest.tar.gz
gunzip xi-latest.tar.gz
This will give you the xi-latest.tar file.

Re-word as you deem appropriate.

Thanks,
Joe

Does the tar xzf xi-latest.tar.gz not produce the proper file structure? Usually that tackles the gunzip portion of the archive.