Nagios Core 4.0.3rc1

[estanley]

A tarball with a release candidate for Nagios Core 4.0.3 has been uploaded to Sourceforge. This tarball contains fixes for a significant number of issues. You are requested to test this release. Please report problems (or successes) related to fixes in this release to the forum under this topic. Please report any new issues to Tracker (http://tracker.nagios.org).

The change log for this release is as follows:

ENHANCEMENTS
* Added notifications on flexible downtime expiration (Dan Wittenberg)

FIXES
* Macros now exported to environment when enable_environment_macros=1 (Eric Stanley)
* No longer checks whether logs can be written when verifying configuration (Eric Stanley)
* Fixed CGI bug where the CGI could read past the end of the list of CGI variables, potentially crashing the CGI (Scott Wilkerson)
* Fixed inheritance of hourly_value from host and service templates (Scott Wilkerson)
* Fixed bug #502: 4.0.0: Configuration -> Service Escalations = incomplete list (Eric Stanley)
* Fixed bug #523: quotes and double quostes in plugin message are converted to HTML escapes in Nagios 4.0 (duplicate of bug #524)
* Fixed bug #524: URLs returned in plugin check results are not correctly displayed (Eric Stanley)

Thanks,

Eric

[abrist]

I will test it this weekend. Cheers good sir.

[marcobto58]

Hi
I tried Nagios core 4.0.3.rc1
it seems working but simply setting process_performance_data=1 in nagios.cfg the wprocs hangs. see log:

[1391526594] Nagios 4.0.3rc1 starting... (PID=6061)
[1391526594] Local time is Tue Feb 04 16:09:54 CET 2014
[1391526594] LOG VERSION: 2.0
[1391526594] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1391526594] qh: core query handler registered
[1391526594] nerd: Channel hostchecks registered successfully
[1391526594] nerd: Channel servicechecks registered successfully
[1391526594] nerd: Channel opathchecks registered successfully
[1391526594] nerd: Fully initialized and ready to rock!
[1391526594] wproc: Successfully registered manager as @wproc with query handler
[1391526594] wproc: Registry request: name=Core Worker 6066;pid=6066
[1391526594] wproc: Registry request: name=Core Worker 6065;pid=6065
[1391526594] wproc: Registry request: name=Core Worker 6064;pid=6064
[1391526594] wproc: Registry request: name=Core Worker 6063;pid=6063
[1391526594] SERVICE FLAPPING ALERT: GalaxyS3;PING;STARTED; Service appears to have started flapping (23.8% change >= 20.0% threshold)
[1391526594] SERVICE FLAPPING ALERT: GalaxyS4;PING;STARTED; Service appears to have started flapping (27.8% change >= 20.0% threshold)
[1391526594] SERVICE FLAPPING ALERT: GalaxyTab;PING;STARTED; Service appears to have started flapping (21.6% change >= 20.0% threshold)
[1391526594] Successfully launched command file worker with pid 6067
[1391526599] wproc: Socket to worker Core Worker 6064 broken, removing
[1391526599] wproc: Socket to worker Core Worker 6066 broken, removing
[1391526602] wproc: Socket to worker Core Worker 6065 broken, removing
[1391526602] wproc: Socket to worker Core Worker 6063 broken, removing
[1391526602] Caught SIGSEGV, shutting down...

the problem is perfectly reproducible also in sample configurations:

1. set process_performance_data=1 in nagios.cfg.
2. set process_perf_data 1 in any service or host definition
3. define a dummy command in command.cfg (follow an example that simply echo env)
define command {
command_name process-service-perfdata
command_line /etc/nagios/libexec/printenv.sh
}

So it is impossible to use the performance counters ....

Regard

[slansing]

@marcobto58

Please report any new issues to Tracker (http://tracker.nagios.org)