NagiosXI checks "an error occurred processing your request"

[Box293]

It looks like MK-Livestatus is failing, this is because of a bug they have regarding Core 4, you will need to use version "1.2.0p3" of livestatus in order to use it with Nagios XI.

Check this posting out:

http://support.nagios.com/forum/viewtop ... s.o#p99734

[QS1]

Thanks, all posts I've read explain what was done to correct but not details. Can you provide the steps needed to downgrade MK-Livestatus?

[Box293]

Thats where my knowledge ends

Perhaps check out the Check_MK forums and see if there is any help there.

[lmiltchev]

I installed ver. 1.2.4 on one of my test boxes and it seems it's working fine. I am not sure if you installed livestatus correctly. I installed it by running:

Code: Select all

cd /tmp
wget http://mathias-kettner.com/download/mk-livestatus-1.2.4.tar.gz
tar xzf mk-livestatus-1.2.4.tar.gz
cd mk-livestatus-1.2.4
./configure --with-nagios4
make
make install

[QS1]

Thank you. I ran the livestatus install based on your instruction and rebooted the VM. Im still receiving the error message

Also I am unable to see the nagios status after starting the service
[root@nagiosxi ~]# service nagios start
Starting nagios: done.
[root@nagiosxi ~]# service nagios status
nagios is not running
[root@nagiosxi ~]#

The nagios.cmd in /usr/local/nagios/var/rw continues to be removed when nagios service starts

[QS1]

At this point the production machine has been down for >24 Hrs. I am currently moving the latest backup data from our 32 bit production machine to an upgraded 64 bit Centos VM. The upgrade is much needed and our monitoring status has become critical.

Are there any other suggestions or input from the NagiosXi team before I begin the 32-to-64 bit upgrade?

[sreinhardt]

If you simply remove the livestatus module line from nagios.cfg, you should be able to start core just fine. Instead of going through the 32-64 transfer process, I would highly advice dropping livestatus until you can test the upgrade in a test vm.

[QS1]

After commenting out the livestatus module line from nagios.cfg the nagios service is now consistent. The Nagios alerts are now being generated. Thank you.

1) What functionality am I loosing with MK livestatus disabled?

I do see side effects:

2) When viewing Service Detail all hosts are greyed out with alert disabled icons on them.

3) When removing (81) hosts through the CCM and applying the config I am getting an error for "cannot find host". All associated services were deleted from the hosts first (config change applied successfully). when deleting the 81 hosts I am getting

"Error: Could not find any host matching 'WU_DOMINOAPP-A1' (config file '/usr/local/nagios/etc/services/DominoApp-A1.cfg', starting on line 169)
Error: Failed to expand host list 'WU_DOMINOAPP-A1' for service 'Windows Updates - AMallory' (/usr/local/nagios/etc/services/DominoApp-A1.cfg:169)"

I see the Hosts in /usr/local/nagios/etc/hosts and I deleted all 81. When I try the apply config the hosts are recreated

[Box293]

1) What functionality am I loosing with MK livestatus disabled?

I wish I could answer that.

As per your other questions, it sounds like the best step here is to delete the configs and then re-write them.

• Go into CCM
  Tools > Write Config Files
  Click the Delete button
  It will say "Successfully deleted all Host / Service Config Files"
  Click the Write Button
  It will show an output of all the files it creates
  Click the Verify button
  The output should end with "Total Errors: 0"
  Quick Tools > Apply Configuration
  Click the Apply Configuration button

[QS1]

Thank you the steps allows me to successfully apply the config for the deleted hosts and answers question #3

#2 When viewing Service Detail all hosts are greyed out with alert disabled icons on them. When viewing the Host Detail everything looks fine. I've rebooted the VM to see if that would correct the issue but it did not. I have attached screenshots of what is being displayed