Multiple Service check time out alert.

[preethu.d]

Hi,

We are getting Multiple Service check time out alert where time out is 60 sec for hosts which are added via vmware wizard. how do we fix the issue?

Regards,
Preethu

[ssax]

What OS/version is your XI server running?

Code: Select all

uname -a
cat /etc/*release

Do they intermittently work?

If your VMWare checks experience timeouts or are unusually slow you may be running out of available entropy (available random numbers) on the XI server that the VMWare Perl SDK needs to function properly/quickly. (random number generation is expensive in terms of CPU cost so you can see delays until there are enough random numbers to fulfill the random number request)

You can validate if you are running out of entropy by running this command when you are experiencing slowness with the check_vmware_api.pl plugin or any other plugin that uses the VMWare Perl SDK:
- NOTE: You may need to run it multiple times to catch the issue but it should not be close to zero

Code: Select all

cat /proc/sys/kernel/random/entropy_avail

If it is close to zero you are likely running out of entropy and you'll need to install a service to fix the system:

NOTE: If you get any errors related to not having a hadware RNG device, you'll need to look at adding a hardware random number generator to the system before rng-tools will work properly:

Feb 10 17:15:04 xxxxx rng-tools[22520]: Starting Hardware RNG entropy gatherer daemon: (Hardware RNG device inode not found)
Feb 10 17:15:04 xxxxx rng-tools[22520]: /etc/init.d/rng-tools: Cannot find a hardware RNG device to use.

If your system is running CentOS/Redhat/Oracle/Amazon Linux/etc:

Code: Select all

sudo yum install rng-tools
sudo systemctl enable rngd
sudo systemctl start rngd

If it's running Debian/Ubuntu:

Code: Select all

sudo apt install rng-tools
sudo systemctl enable rng-tools
sudo systemctl start rng-tools

Then test it again and see if the issue is resolved.

[preethu.d]

Hi,

Thanks for the update.
This issue resolved automatically, looks like it was a network fluctuation.
You can lock the thread.

Regards,
Preethu

[ssax]

Thank you for the update, locking and marking as resolved.