Nagios Support Forum

I installed Nagios 4.1.1 on Ubuntu 14.04.4 LTS

All checks are working fine.

But i get lots of informational messages like

[1461234388] wproc: HOST PERFDATA job 86 from worker Core Worker 28047 is a non-check helper but exited with return code 2
[1461234388] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461234388] wproc: HOST PERFDATA job 86 from worker Core Worker 28050 is a non-check helper but exited with return code 2
[1461234388] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461234388] wproc: HOST PERFDATA job 86 from worker Core Worker 28048 is a non-check helper but exited with return code 2
[1461234388] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461234390] wproc: HOST PERFDATA job 87 from worker Core Worker 28049 is a non-check helper but exited with return code 2
[1461234390] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461234390] wproc: HOST PERFDATA job 88 from worker Core Worker 28050 is a non-check helper but exited with return code 2
[1461234390] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461234390] wproc: HOST PERFDATA job 87 from worker Core Worker 28048 is a non-check helper but exited with return code 2
[1461234390] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;

How I can drill down to the origin of these messages?

Best regards
Andi

In the nagios.cfg file, you can enable debugging and check the /usr/local/nagios/var/nagios.debug file to see what is causing the error.
Can you post your nagios.cfg file so we can review it?

here is the nagios.cfg

in the nagios.log I find this

[1461310175] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;
[1461310175] wproc: SERVICE PERFDATA job 876 from worker Core Worker 25806 is a non-check helper but exited with return code 2
[1461310175] wproc: early_timeout=0; exited_ok=1; wait_status=512; error_code=0;

in the nagios.debug (debug_level=-1 and debug_verbosity=2) I see this

[1461310175.100910] [016.2] [pid=25804] Processing check result for service 'Baramundi-Agent' on host 'OBB-PC-HASTA23'
[1461310175.100912] [001.0] [pid=25804] handle_async_service_check_result()
[1461310175.100914] [016.0] [pid=25804] ** Handling check result for service 'Baramundi-Agent' on host 'OBB-PC-HASTA23' from 'Core Worker 25806'...
[1461310175.100916] [016.1] [pid=25804] HOST: OBB-PC-HASTA23, SERVICE: Baramundi-Agent, CHECK TYPE: Active, OPTIONS: 0, SCHEDULED: Yes, RESCHEDULE: Yes, EXITED OK: Yes, RETURN CODE: 0, OUTPUT: 1 process matching bma.exe (> 0)

[1461310175.100920] [001.0] [pid=25804] get_service_check_return_code()
[1461310175.100922] [016.2] [pid=25804] Parsing check output...
[1461310175.100924] [016.2] [pid=25804] Short Output: 1 process matching bma.exe (> 0)
[1461310175.100925] [016.2] [pid=25804] Long Output: NULL
[1461310175.100927] [016.2] [pid=25804] Perf Data: NULL
[1461310175.100929] [016.2] [pid=25804] ST: HARD CA: 1 MA: 3 CS: 0 LS: 0 LHS: 0
[1461310175.100931] [016.1] [pid=25804] Service is OK.
[1461310175.100933] [016.1] [pid=25804] Service did not change state.
[1461310175.100938] [016.1] [pid=25804] Rescheduling next check of service at Fri Apr 22 09:39:33 2016
[1461310175.100940] [001.0] [pid=25804] get_next_valid_time()
[1461310175.100943] [001.0] [pid=25804] _get_matching_timerange()
[1461310175.100945] [001.0] [pid=25804] schedule_service_check()
[1461310175.100948] [016.0] [pid=25804] Scheduling a non-forced, active check of service 'Baramundi-Agent' on host 'OBB-PC-HASTA23' @ Fri Apr 22 09:39:33 2016
[1461310175.100950] [016.2] [pid=25804] Scheduling new service check event.
[1461310175.100952] [001.0] [pid=25804] add_event()

One causeof that message means a script/executable in the command_line of the eventhandler command definition can't be found (Edit: or the command isn't a valid shell command, check for typos, missing quotes, unescaped special characters). It's a good idea to use the full path to scripts, you can use the $USER1$ macro for executables in /usr/local/nagios/libexec.
If you have an event handler defined for the Baramundi-Agent, you may want to check it.

Thank you for your hint. I could fix it. It was a wrong pnp4nagios configuration.

Best regards
Andi

Great to hear! Are we good to mark this thread as resolved?