Nagios Support Forum

Hi there,

We've just updated NXI to R1.6 and:
a) on Advanced tab for hosts we get:
Notice: Undefined property: stdClass::$hoststatus in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1172
Notice: Trying to get property of non-object in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1172

b) on Performance graphs tab for hosts we get:
Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1008

Additionally in Apache's error_log:

PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1008, referer: http://x.x.x.x/nagiosxi/includes/compon ... st=y.y.y.y
PHP Notice: Undefined property: stdClass::$hoststatus in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1172, referer: http://x.x.x.x/nagiosxi/includes/compon ... st=y.y.y.y
PHP Notice: Trying to get property of non-object in /usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1172, referer: http://x.x.x.x/nagiosxi/includes/compon ... st=y.y.y.y

Apart from that NXI GUI is veeeery slow (much slower than R1.2) while old nagios GUI work just fine.
This is very strange since the server is not overloaded. Every action we try to perform in NXI GUI take ages to complete. This makes it really unusable.

Any ideas ?

Michalux

What distro is this running on?

Can you run php -v from the command-line and show us the output?

Distro: Oracle Linux Server release 5.6 (RedHat Clone actually)
Kernel: 2.6.32-100.26.2.el5 (x86_64)
php -v:
PHP 5.1.6 (cli) (built: Feb 11 2010 19:06:40)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

Just to verify, I've installed NXI GUI from R1.2 in parallel to R1.6 (in different location on the same server). Opening host tabs using R1.2 doesn't show those errors, so there must be something in R1.6 that causes that.

Michalux

Distro: Oracle Linux Server release 5.6 (RedHat Clone actually)

This is not a supported installation distribution. We only support RHEL and CentOS at this time.

Just to verify, I've installed NXI GUI from R1.2 in parallel to R1.6 (in different location on the same server). Opening host tabs using R1.2 doesn't show those errors, so there must be something in R1.6 that causes that.

How did you set this up?

This would have been relevant information to know up front. I'm amazed the system is working as well as it is. This will most DEFINITELY break things. I understand the need to test release updates before implementing them in production, which is why our licenses cover a Production server, a Test environment, and a Disaster Recovery server. We maintain a controlled environment on which the installation is on so that we can document, test, and fully support our installations.

Ok - I understand that You do not support Oralce Linux, but running R1.2 we had no problems of such a kind (and Orlacle Linux i actually just like RHEL !)
As I've mentioned we have parallel R1.2 NXI installed (only the copy of /usr/local/nagiosxi directory available as separate URL) - and using R1.2 code this errors does not appear.

So I'd appreciate some info about how to fix this.

Michalux

I've found something new - our environment is placed behind the NAT.
Accessing it from within the same network produces no errors whatsoever.
So the problem seems to be somehow connected to the NAT translation. But R1.2 didn't behave that way, so the changes made after R1.2 have introduced this problem.

So, I'd appreciate some solution.
We cannot remove the NAT, so from the network's perspective it has to work this way.

Michalux

I need so know exactly what you did in your upgrade process, and also any difference in directory structure on your XI install.

Even with that information, I don't have an expectation of the side-by-side install of XI working correctly. There are too many internal calls and include references to know where something is going wrong.

I'll put together a script to display what URL's and addresses are being called by XI on your system to address the NAT situation.

(and Orlacle Linux is actually just like RHEL !)

There are differences between RHEL and CentOS 5/6 32/64 bit, all of which require us to make adjustments in our install scripts. It is still and different distribution, and would require adjustments to our install scripts to verify that it works correctly. This does matter in terms of support.

We will try and point you in the right direction, but understand that you've strayed from a supported installation in multiple ways, so we don't guarantee everything working correctly with the set up that you have.

Ok, lets leave the parallel installation problem, since it's not the point of this topic.

I think I've figured it out what is going on (regarding the errors mentioned above).
This problem seems to be closely connected to the second one I've opened the topic for - slowness of NXI R1.6 GUI.
As You've mentioned in that second topic, now NXI makes some local calls due to the SSL support to work correctly.
So opening NXI GUI with URL pointing to the NATed IP address makes NXI server perform local http calls back to this NATed IP - and since it doesn't get the response, some things in the GUI apparently breake up. This manifests itself with slow opening of GUI pages and with such errors mentioned above (additionally I've noticed that only three of six system status indicators show up on the top of the page).

So from my perspective the problem has nothing to do with the NXI installation/upgrade process. It's only about the NAT and the way NXI GUI work in NATed environment.
The question is if there is a way to fix NAT support without breaking up the SSL support.

Michalux

Michalux,

I'm gonna close this topic, not because your questions aren't valid, but because the two running threads seem to have merged, so any further conversation on this topic should be directed to the other thread.