Nagios Support Forum

Posted: **Sun Feb 07, 2021 12:08 pm**

Hello.

I have recently migrated my network monitoring machine from armbian (Debian on the arm architecture) to OpenBSD 6.8 (armv7). Unfortunately, upon installing and configuring nagios for this new environment, I've run into a few stumbling blocks. Most of them I've been able to figure out myself, but I've not yet been able to get to the bottom of why check_ping doesn't seem to be executing properly when handled by nagios, despite the fact that it runs without a problem manually.

When navigating to the Current Status->Problems->Services display, status is unknown or down, depending on how long nagios has been running, last check is 30-40+ years in the past, the duration is running into the tens or hundreds of thousands of days, and the status information states "(No output on stdout) stderr: "

(see screenshot)

: Screenshot of the Current Status:Problems:Services display

When running nagios from the console, the following error messages are displayed:

wproc: CHECK job 19 from worker Core Worker 33684 died by signal 11 (core dumped) after -451591648.00 seconds
wproc: host=d-resources; service=PING;
wproc: early_timeout=0; exited_ok=1; wait_status=139; error_code=0;
wproc: CHECK job 19 from worker Core Worker 3931 died by signal 11 (core dumped) after -68996576.00 seconds
wproc: host=diaspora; service=(null);
wproc: early_timeout=0; exited_ok=1; wait_status=139; error_code=0;
wproc: CHECK job 20 from worker Core Worker 40023 died by signal 11 (core dumped) after -299544416.00 seconds
wproc: host=localhost; service=(null);
wproc: early_timeout=0; exited_ok=1; wait_status=139; error_code=0;

in /usr/local/nagios/libexec/, check_ping seems to be executing just fine, though:

borgi$ libexec/check_ping
check_ping: Could not parse arguments
Usage:
check_ping -H <host_address> -w <wrta>,<wpl>% -c <crta>,<cpl>%
[-p packets] [-t timeout] [-4|-6]

/usr/local/nagios/etc/resource.cfg only contains the following uncommented line:
$USER1$=/usr/local/nagios/libexec

and in /usr/local/nagios/etc/servers/ I have the following 2 files, for each of the hosts I am starting to configure:

Code: Select all

borgi$ ls
d-resources_host.cfg  diaspora_host.cfg
borgi$ cat d-resources_host.cfg                                                                                                      
define host {
   use linux-server
   host_name d-resources
   alias Primary Desktop Host
   address 192.168.0.2
   register 1
}

define service {
   host_name d-resources
   service_description PING
   check_command check_ping!100.0,20%!500.0,60%
   max_check_attempts 2
   check_interval 2
   retry_interval 2
   check_period 24x7
   check_freshness 1
   contact_groups admins
   notification_interval 2
   notification_period 24x7
   notifications_enabled 1
   register 1
}
borgi$ cat diaspora_host.cfg                                                                                                         
define host {
   use linux-server
   host_name diaspora
   alias Diaspora/SBBS Host
   address 192.168.0.14
   register 1
}

define service {
   host_name diaspora
   service_description PING
   check_command check_ping!100.0,20%!500.0,60%
   max_check_attempts 2
   check_interval 2
   retry_interval 2
   check_period 24x7
   check_freshness 1
   contact_groups admins
   notification_interval 2
   notification_period 24x7
   notifications_enabled 1
   register 1
}

I have been googling and trying to find any information that might help me with this issue and I'm not finding anything except for issues with people having $USER1$ set incorrectly, incorrect permissions on the libexec directory, or no plugins installed... None of which seem to apply to me in this particular scenario. If anybody has any pointers or ideas that might help lead me to a resolution on this problem I would be very much appreciative for whatever you can offer. Please let me know if there is any more information that I can provide in order to assist in troubleshooting.

Thank you for your time and assistance on this matter!

Posted: **Mon Feb 08, 2021 10:38 am**

With a little bit more investigation, this seems to be an issue with the plugin executables themselves. It seems that check_ping, although running fine to print usage information without arguments, segfaults when given appropriate arguments. I'm guessing that this may be an issue when compiled for the arm architecture, as I've stumbled across a few reports of things working just fine under OpenBSD in general.

Does anybody know what I might be able to do about this issue?

Nagios Support Forum

problem with check_ping reporting hosts as down (signal 11?)

problem with check_ping reporting hosts as down (signal 11?)

Re: problem with check_ping reporting hosts as down (signal