check_esx3.pl times out after applying ESXi 5.1 U3 patch
Posted: Fri Feb 13, 2015 1:28 pm
Hello,
We had a number of checks using the check_esx3.pl plugin successfully working for a number of months until we recently applied a ESXi 5.1 Update 3 which includes the following patches:
ESXi510-201412201-UG: Updates ESXi 5.1 esx-base vib
ESXi510-201412202-UG: Updates ESXi 5.1 tools-light vib
ESXi510-201412203-UG: Updates ESXi 5.1 scsi-megaraid-sas vib
ESXi510-201412101-SG: Updates ESXi 5.1 esx-base vib
Now the plugin times out. On further inspection, the plugin returns results but these take between 85 and 200+ seconds. The ESXi servers are not under any significant load, network issues have been ruled out (as RTT is < 1ms) and a https get (via wget) on the ESXi management pages is < 1 sec.
From reading similar threads I tried:
-- updating perl-libwww
-- update check_esx3.pl to 3.0.5
Neither of these tasks helped, and still plugin response time is very slow.
I know this must be related to the latest patch applied to ESXi as it was working fine before, but are you aware of any fixes or workarounds?
Thanks,
Michael
We had a number of checks using the check_esx3.pl plugin successfully working for a number of months until we recently applied a ESXi 5.1 Update 3 which includes the following patches:
ESXi510-201412201-UG: Updates ESXi 5.1 esx-base vib
ESXi510-201412202-UG: Updates ESXi 5.1 tools-light vib
ESXi510-201412203-UG: Updates ESXi 5.1 scsi-megaraid-sas vib
ESXi510-201412101-SG: Updates ESXi 5.1 esx-base vib
Now the plugin times out. On further inspection, the plugin returns results but these take between 85 and 200+ seconds. The ESXi servers are not under any significant load, network issues have been ruled out (as RTT is < 1ms) and a https get (via wget) on the ESXi management pages is < 1 sec.
From reading similar threads I tried:
-- updating perl-libwww
-- update check_esx3.pl to 3.0.5
Neither of these tasks helped, and still plugin response time is very slow.
I know this must be related to the latest patch applied to ESXi as it was working fine before, but are you aware of any fixes or workarounds?
Thanks,
Michael