upgrading from Nagios XI 2009R1.3E to 2009R1.4B problems

[microdata.dk]

help

[microdata.dk]

After a reboot, the error came back... What to do????

[microdata.dk]

Feb 28 21:17:41 ASPMON01 xinetd[1626]: FAIL: nsca service_limit from=xxx.xxx.xxx.xxx

[rdedon]

Code: Select all

cps              Limit the guesses OF incoming connections.  Takes two argument.  The roofridge argument is the
                        NUMBER  OF  connections  by  second  tons  acts.  If the guesses OF incoming connections is
                        more higher than this, the service wants fuel element temporarily disabled.  The second argument  is  the
                        NUMBERs OF seconds tons of WAIT before RH-enabling the service after it has been disabled.  The
                        default for this setting is 50 incoming connections and the interval is 10 seconds.

It looks as cps needs to be adjusted for xinetd for nsca.

[tonyyarusso]

As for the Event Data issue, I don't know the cause myself, but I'm told this is a now-known bug, and a patch will be coming shortly.

[microdata.dk]

Where do i change this??

[rdedon]

Where do i change this??

The fix should be coming out very shortly so I would advise waiting before we start changing things (as then the bug fix may not work properly).

[mguthrie]

This seems to be an issue showing up for users who utilize a lot of passive checks, we're working on resolving it as we speak. Here are some notes from our lead developer to another user experiencing some of these issues, if you could try them and let us know the results we would appreciate it.

Try these changes:

1. Edit /usr/local/nagios/etc/nagios.cfg and change the
"log_passive_checks" option from 1 to zero (0).

2. Truncate(empty) the following tables in the "nagios" MySQL database:

nagios_logentries
nagios_eventhandlers

Let us know if MySQL indicates the tables are damaged.

3. Restart Nagios core: /etc/init.d/nagios restart

4. Kill any hung dbmaint.php cron jobs:

Code: Select all

	ps axuw | grep dbmaint.php
	kill -9 [processid]

5. Optionally change the db maintenance schedule. This is configured in
the following file:

/usr/local/nagiosxi/html/config.inc.php

The maintenance/repair schedules are located in an array. You'll see
values for these in the following array (abbreviated for clarity):

Code: Select all

	$cfg['db_info']=array(
		"ndoutils" => array(
			"dbmaint" => array(
				"optimize_interval" > 60,
				"repair_interval" => 120,
				),
			),
		);