Nagios Support Forum

I will review the configuration with the support team and get back.

Thanks for the example / feedback.

############################################################################### # # Services configuration file # # Created by: Nagios CCM 2.7.0 # Date: 2018-10-10 11:45:38 # Version: Nagios Core 4.x # # --- DO NOT EDIT THIS FILE BY HAND --- # Nagios CCM will overwrite all manual settings during the...

I can see the authfiles are accessible by Nagios, please see below [nagios@sl79nag01 vmware]$ ls sa79esx1001_corp_shire_com_auth.txt sa79esx1003_corp_shire_com_auth.txt sa79esx1021_auth.txt sy21esx20a_corp_shire_com_auth.txt usbbvc1001_corp_inbaxalta_com_auth.txt sa79esx1002_corp_shire_com_auth.txt ...

[root@sl79nag01 var]# su - nagios Last login: Tue Oct 9 22:00:07 EDT 2018 [nagios@sl79nag01 ~]$ /usr/local/nagios/libexec/check_esx3.pl -V check_esx3.pl 0.7.1 [nagios@sl79nag01 ~]$ define command { command_name check_esx3_guest command_line $USER1$/check_esx3.pl -H "$HOSTADDRESS$" -f "...

what does this mean? we disabled all Vcenter alerts and still see this error below. I also confirmed the file does exist in Nagios. Confirmation: [root@sl79nag01 libexec]# ls -la check_esx check_esx3.pl check_esx3.pl_backup check_esxi_hardware.py [root@sl79nag01 libexec]# ls -la check_esx3.pl -rwxrw...

# ./check_esx3.pl -V
check_esx3.pl 0.7.1
[root@sl79nag01 libexec]#

I had to disable the notification to most of them.
I used ps -ef |grep check_esx3.pl |wc -l and when the server was about to crash, it had 1001 running.

Nagiosxi 5.5.4
Redhat Linux 7.4
load average: 294.89, 242.34, 165.81
check_esx3 plugin spawns 1000s
Linux server crashes and reboots . Disabling the plugin for now. Any fix to this issue?

269472 ticket open and profile uploaded for review.

More LOGs PHP Warning: pg_set_client_encoding() expects parameter 1 to be resource, boolean given in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-postgres7.inc.php on line 255 tail cmdsubsys.log PROCESSED 0 COMMANDS ........................................................... PROCESSED 0 COMMANDS ...

The upgrade to Nagios 5.5.0 also negatively affected the reporting feature.