Something went wrong with commad submitted to Nagios Core

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
thur686
Posts: 66
Joined: Mon Jan 12, 2015 2:33 pm

Something went wrong with commad submitted to Nagios Core

Post 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
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Something went wrong with commad submitted to Nagios Cor

Post 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?
Former Nagios Employee
thur686
Posts: 66
Joined: Mon Jan 12, 2015 2:33 pm

Re: Something went wrong with commad submitted to Nagios Cor

Post 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.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Something went wrong with commad submitted to Nagios Cor

Post 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
Be sure to check out our Knowledgebase for helpful articles and solutions!
thur686
Posts: 66
Joined: Mon Jan 12, 2015 2:33 pm

Re: Something went wrong with commad submitted to Nagios Cor

Post 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
You do not have the required permissions to view the files attached to this post.
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Something went wrong with commad submitted to Nagios Cor

Post by tmcdonald »

If the supplied zip did not work, then an upgrade will be necessary to resolve. We don't generally back-port fixes.
Former Nagios employee
thur686
Posts: 66
Joined: Mon Jan 12, 2015 2:33 pm

Re: Something went wrong with commad submitted to Nagios Cor

Post 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.
You do not have the required permissions to view the files attached to this post.
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Something went wrong with commad submitted to Nagios Cor

Post 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.
Former Nagios employee
Locked