Page 1 of 1

Something went wrong with commad submitted to Nagios Core

Posted: Tue Feb 09, 2016 11:41 am
by thur686
Host OS: CentOS6
Nagios XI version: 5.2.2

Hello,
When we try to use the scheduled downtime feature (downtime.php) we encounter the following error message:
Something went wrong with the commad submitted to Nagios Core
A quick internet search turned up this thread: https://support.nagios.com/forum/viewto ... 16&t=35033

Rather than use that work-around, I thought it would be better to just fix the certificate problem. It turns out that was a bad idea as I have no idea how to fix a certificate problem. These are the commands I tried:

Code: Select all

yum install ca-certificates
update-ca-trust force-enable
cd /etc/pki/tls/certs/
cp ca.crt /etc/pki/ca-trust/source/anchors/
update-ca-trust extract
service nagios restart
service httpd restart
I tried to import our CA certificate (ca.crt) into "/etc/pki/tls/certs/ca-bundle.crt" unsuccessfully. Curl validates the problem.

curl https://devnagios.mydomain.com/nagiosxi/
curl: (35) SSL connect error

curl https://devnagios.mydomain.com/nagiosxi/ -o /etc/pki/tls/certs/ca-bundle.crt
curl: (35) SSL connect error

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Tue Feb 09, 2016 11:48 am
by rkennedy
The work around that @ssax posted should work, but I also believe that this was fixed in 5.2.3.

Is using the patch, or upgrading an option?

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Tue Feb 09, 2016 1:06 pm
by thur686
Thanks rkennedy, I can use the work around. However the Network Status map (status.php) doesn't work either and I was thinking that the root cause could also be a local certificate problem.

We did not have plans to move to 5.2.3 yet.

I can try the downtime.zip work around and open another thread for the Network Status map if that is best.

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Tue Feb 09, 2016 2:02 pm
by lmiltchev
Yes, you can do that - start a new thread for the Network Status map issue. Show us a screenshot of the error that you see in the web UI, and a tail of the apache error log in code wraps.

Code: Select all

tail -100 /var/log/httpd/error_log

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Tue Feb 09, 2016 2:44 pm
by thur686

Code: Select all

[Tue Feb 09 14:38:42 2016] [error] [client 10.10.10.10] PHP Notice:  Trying to get property of non-object in /usr/local/nagiosxi/html/includes/components/xicore/downtime.php on line 501, referer: https://securenagios.com/nagiosxi/includes/components/xicore/downtime.php
[Tue Feb 09 14:38:42 2016] [error] [client 10.10.10.10] PHP Notice:  Trying to get property of non-object in /usr/local/nagiosxi/html/includes/components/xicore/downtime.php on line 501, referer: https://securenagios.com/nagiosxi/includes/components/xicore/downtime.php
[Tue Feb 09 14:38:42 2016] [error] [client 10.10.10.10] PHP Warning:  Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/xicore/downtime.php on line 501, referer: https://securenagios.com/nagiosxi/includes/components/xicore/downtime.php

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Wed Feb 10, 2016 1:07 pm
by tmcdonald
If the supplied zip did not work, then an upgrade will be necessary to resolve. We don't generally back-port fixes.

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Tue Mar 01, 2016 4:41 pm
by thur686
I performed an upgrade to 5.2.5 and it did not help. Although the error message has changed to 'Something went wrong with the command submitted to Nagios Core' and the color around the message is RED rather than green.

I will open a support ticket, thanks for the assistance.

Re: Something went wrong with commad submitted to Nagios Cor

Posted: Wed Mar 02, 2016 12:02 pm
by tmcdonald
Haven't seen a ticket come in yet, just checking in. Did you get a bounceback, or just haven't emailed in yet?

Update: We got the ticket, so I will be closing this thread now.