Nagios 4.0.2 and pnp4nagios wproc issue?

[JohnO]

Greetings,

I've just updated a small test environment from Nagios 3.5.1 to Nagios 4.0.2. I've also got pnp4Nagios 0.6.21 running with this installation.

The Nagios upgrade went fine. Old pnp4Nagios data is still available, but it appears the perfdata checks are not happening.

The Nagios event log shows the following:

Informational Message[12-26-2013 12:25:37] wproc: Unknown job type: 10
Informational Message[12-26-2013 12:25:37] Worker 50318: Unknown jobtype: 10
Informational Message[12-26-2013 12:25:37] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
Informational Message[12-26-2013 12:25:37] wproc: command: /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl
Informational Message[12-26-2013 12:25:37] wproc: SERVICE PERFDATA job 211 from worker Core Worker 50318 is a non-check helper but exited with return code 2

I've seen similar notes here on the forum, but some seem to point to tracker issues that may have been resolved in 4.0.2, but since that is what I'm running, I wanted to confirm what I'm seeing is still a core issue vs. a problem in my configuration.

Thanks,

John

[slansing]

It appears as though this is because the workers are not correctly set up to handle performance data, you could try this patch here, though we have not heard back from others with this issue after the 4.0.2 release, so it was presumed fixed.

http://tracker.nagios.org/view.php?id=534

[JohnO]

Welp -- the patch eliminated the unknown job type error. Unfortunately, it still appears that the perfdata files are not being written/updated:

Informational Message[12-26-2013 14:22:47] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
Informational Message[12-26-2013 14:22:47] wproc: command: /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl
Informational Message[12-26-2013 14:22:47] wproc: SERVICE PERFDATA job 26 from worker Core Worker 61313 is a non-check helper but exited with return code 2

Looking at the Performance Data line on the Service State information display for Nagios shows that the data is there. It just isn't getting written out the way it should. The pnp4nagios verify script completes with no critical errors. The data that was in the directory/log files is still displayed correctly - just nothing new is being generated.

Thanks,

John

[slansing]

Well we tracked down your error code, which is being output as a part of the processperfdata script. The issue is that it is trying to parse environment variables which are currently broken in core 4, we are working on a fix for this but that is what is going on here. Unfortunately there is not currently a work around for this.

[JohnO]

I really appreciate the prompt and detailed feedback.

This is just in a test environment, so no big deal to wait and try again some time in the future!

Thanks again,

John

[sreinhardt]

Your welcome, just an fyi myself and another core developer are currently working to resolve this as soon as possible. Hopefully in 4.0.3, as per our last discussion, which should be out soon. I'm going to lock this up for now.