Update to 5.6.3 appears to have failed

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Update to 5.6.3 appears to have failed

Post by benningtonr »

can i get some assistance, i just ran the update script. It ran for a very long time. Usually it says update complete. this time it ended with this

granted this is just the last few lines, if there are logs i can submit please let me know, thank you

Done!
Installing 'dashlets/rss_dashlet.zip'
TMPNAME: C2nRK
Archive: /tmp/nagiosxi/subcomponents/xidashlets/dashlets/rss_dashlet.zip
9516d80a47aa2af87388f0f7c216c2e7380cd49b
creating: rss_dashlet/
creating: rss_dashlet/magpierss/
inflating: rss_dashlet/magpierss/AUTHORS
inflating: rss_dashlet/magpierss/CHANGES
inflating: rss_dashlet/magpierss/ChangeLog
inflating: rss_dashlet/magpierss/INSTALL
inflating: rss_dashlet/magpierss/NEWS
inflating: rss_dashlet/magpierss/README
inflating: rss_dashlet/magpierss/TROUBLESHOOTING
inflating: rss_dashlet/magpierss/cookbook
creating: rss_dashlet/magpierss/extlib/
inflating: rss_dashlet/magpierss/extlib/Snoopy.class.inc
inflating: rss_dashlet/magpierss/rss_cache.inc
inflating: rss_dashlet/magpierss/rss_fetch.inc
inflating: rss_dashlet/magpierss/rss_parse.inc
inflating: rss_dashlet/magpierss/rss_utils.inc
inflating: rss_dashlet/rss.jpg
inflating: rss_dashlet/rss_dashlet.css
inflating: rss_dashlet/rss_dashlet.inc.php
rss_dashlet
DASHLET NAME: rss_dashlet
CMD=grep register_dashlet /usr/local/nagiosxi/tmp/C2nRK/rss_dashlet/rss_dashlet.inc.php | wc -l
1
OUT=1
Dashlet looks ok...
CMD: cp -rf /usr/local/nagiosxi/tmp/C2nRK/rss_dashlet /usr/local/nagiosxi/html/includes/dashlets/
CMD: rm -rf /usr/local/nagiosxi/tmp/C2nRK
CMD: . /usr/local/nagiosxi/var/xi-sys.cfg && chown -R $nagiosuser /usr/local/nagiosxi/html/includes/dashlets/rss_dashlet


Done!
INSTALL: Dashlets installed/updated OK.
CREATE TYPE
CREATE SEQUENCE
psql:nagiosxi/nagiosxi-db/mods/pgsql/schema_05.sql:23: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "xi_mibs_pkey" for table "xi_mibs"
psql:nagiosxi/nagiosxi-db/mods/pgsql/schema_05.sql:23: NOTICE: CREATE TABLE / UNIQUE will create implicit index "xi_mibs_mib_name_key" for table "xi_mibs"
CREATE TABLE
ALTER TABLE
chown: invalid user: `snmptt:nagios'
swolf

Re: Update to 5.6.3 appears to have failed

Post by swolf »

Hi @benningtonr,

What version did you upgrade from? What distribution are you running? Could you either upload your system profile here or PM it to me?
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Re: Update to 5.6.3 appears to have failed

Post by benningtonr »

Upgrading from 5.4.13, not sure where to get distribution version.
Can you send me instruction on how to get system config and I will PM it to you.

Thank you
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Re: Update to 5.6.3 appears to have failed

Post by benningtonr »

I got the profile:

Nagios XI - System Info
System:
Nagios XI Version : 5.4.13
nagios.whro.local 2.6.32-431.17.1.el6.i686 i686
CentOS release 6.5 (Final)
Gnome is not installed
Apache Information
PHP Version: 5.3.3
Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36
Server Name: nagios.whro.local
Server Address: 192.168.99.69
Server Port: 80
Date/Time
PHP Timezone: America/New_York
PHP Time: Mon, 08 Jul 2019 13:33:36 -0400
System Time: Mon, 08 Jul 2019 13:33:36 -0400
Nagios XI Data
License ends in: NSQSMM

nagios (pid 25978) is running...
NPCD running (pid 1941).
ndo2db (pid 21224) is running...
CPU Load 15: 0.06
Total Hosts: 101
Total Services: 744
Function 'get_base_uri' returns: http://nagios.whro.local/nagiosxi/
Function 'get_base_url' returns: http://nagios.whro.local/nagiosxi/
Function 'get_backend_url(internal_call=false)' returns: http://nagios.whro.local/nagiosxi/inclu ... 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.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.031 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.026 ms

--- localhost.localdomain ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.026/0.027/0.031/0.006 ms
Test wget To localhost
WGET From URL: http://localhost/nagiosxi/includes/components/ccm/
Running:
/usr/bin/wget http://localhost/nagiosxi/includes/components/ccm/
--2019-07-08 13:33:38-- http://localhost/nagiosxi/includes/components/ccm/
Resolving localhost... ::1, 127.0.0.1
Connecting to localhost|::1|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://localhost/nagiosxi/login.php?red ... f&noauth=1 [following]
--2019-07-08 13:33:38-- http://localhost/nagiosxi/login.php?red ... f&noauth=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.15M=0.02s

2019-07-08 13:33:39 (1.15 MB/s) - "/usr/local/nagiosxi/tmp/ccm_index.tmp" saved [25968]

Network Settings
1: lo: mtu 16436 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 UNKNOWN qlen 1000

link/ether 00:50:56:b8:70:2b brd ff:ff:ff:ff:ff:ff

inet 192.168.99.69/22 brd 192.168.99.255 scope global eth0

inet6 fd2b:5d0f:da65:0:250:56ff:feb8:702b/64 scope global dynamic

valid_lft forever preferred_lft forever

inet6 fe80::250:56ff:feb8:702b/64 scope link

valid_lft forever preferred_lft forever

3: eth1: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000

link/ether 00:50:56:b8:32:79 brd ff:ff:ff:ff:ff:ff

inet 172.16.16.42/24 brd 172.16.16.255 scope global eth1

inet6 fe80::250:56ff:feb8:3279/64 scope link

valid_lft forever preferred_lft forever


172.16.16.0/24 dev eth1 proto kernel scope link src 172.16.16.42

192.168.96.0/22 dev eth0 proto kernel scope link src 192.168.99.69

169.254.0.0/16 dev eth0 scope link metric 1002

169.254.0.0/16 dev eth1 scope link metric 1003

default via 192.168.99.1 dev eth0
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Re: Update to 5.6.3 appears to have failed

Post by benningtonr »

I get this when i click download profile

PROFILE BUILD FAILED
Array
(
)
CODE: 1
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Update to 5.6.3 appears to have failed

Post by benjaminsmith »

Hello,
I get this when i click download profile
PROFILE BUILD FAILED
Array
(
)
CODE: 1
This error is usually caused by an incorrect sudoers file. Please follow the directions in the knowledge-base article below to correct this. Let us know if you have any questions.

Nagios XI - Profile Build Failed
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Re: Update to 5.6.3 appears to have failed

Post by benningtonr »

Okay, so reading the document, i get why i cannot download the profile. Which is the reason for the help request. The upgrade to 5.6.3 failed to complete correctly. I did not get the installation completed successfully when it was done. so it is in a state of flux. I show that i am still running 5.4.13, but the sudoer file is probably 5.6.3.

So i still need assistance on getting my system either back to 5.4.13 so i can try the upgrade again, or i need help fixing the reason it did not complete successfully.

Thank you
danniiffxi
Posts: 121
Joined: Tue Jan 30, 2018 3:29 am
Location: UK

Re: Update to 5.6.3 appears to have failed

Post by danniiffxi »

I am having what appears to be the same error, note that my sudoers file is fine and it is not related to the fault you reported.

https://support.nagios.com/forum/viewto ... 16&t=54647

I am convinced it is a permissions issues as the line we are both getting " chown: invalid user: `snmptt:nagios' " is shown.

I too would like i know how to fix this is possible.. I am updating from 5.6.1 to 5.6.3
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Update to 5.6.3 appears to have failed

Post by tgriep »

Run the following to create the snmptt user and re-run the upgrade.

Code: Select all

adduser snmptt
usermod -a -G nagcmd snmptt
usermod -a -G nagios snmptt
Be sure to check out our Knowledgebase for helpful articles and solutions!
benningtonr
Posts: 524
Joined: Tue May 22, 2012 2:16 pm

Re: Update to 5.6.3 appears to have failed

Post by benningtonr »

is this for Danni to run or me?
Locked