Nagios Support Forum

Hi Team,

On ESX host monitoring using box293 we are frequenly getting alert with message Error: Cannot complete login due to an incorrect user name or password.
Which is recovering automatically. Can you please help us on this to resolve the issue.

2017-07-18 09:26:16 dfweXXXX CPU Usage UNKNOWN SOFT 1 of 3 UNKNOWN: Error: Cannot complete login due to an incorrect user name or password.
2017-07-17 23:27:32 dfweXXXX CPU Usage OK SOFT 2 of 3 OK: Host CPU {Free: 58.4 GHz} {Used: 1.5 GHz} {Total: 59.9 GHz}
2017-07-17 23:22:41 dfweXXXX CPU Usage UNKNOWN SOFT 1 of 3 UNKNOWN: Error: Cannot complete login due to an incorrect user name or password.
2017-07-17 22:37:40 dfweXXXX CPU Usage OK HARD 3 of 3 OK: Host CPU {Free: 58.1 GHz} {Used: 1.8 GHz} {Total: 59.9 GHz}
2017-07-17 21:07:57 dfweXXXX CPU Usage UNKNOWN HARD 3 of 3 UNKNOWN: Error: Cannot complete login due to an incorrect user name or password.
2017-07-17 21:03:14 dfweXXXX CPU Usage UNKNOWN SOFT 2 of 3 UNKNOWN: Error connecting to server at 'https://172.X.X.X/sdk/webService': Connection refused
2017-07-17 20:57:55 dfweXXXX CPU Usage UNKNOWN SOFT 1 of 3 UNKNOWN: Error connecting to server at 'https://172.X.X.X./sdk/webService': Connection refused
2017-07-17 19:43:05 dfweXXXX CPU Usage OK HARD 3 of 3 OK: Host CPU {Free: 58.3 GHz} {Used: 1.6 GHz} {Total: 59.9 GHz}

are you using a local vmware account or a domain account to login? it looks like there may be an intermittent issue with the plugin connecting, especially with the connection refused errors.

One thing to check when you see intermittent issues like this is if you have any filters, host or network data loss prevention, or IPS/IDS devices that may be flagging the communication for some reason thinking it's an exploit and dropping it. Please have your network admins validate the logs on the devices in the path to see what they are seeing.

Is it only for this host or are all ESX hosts having this issue?


Thank you

For a particular vCenter esx host. We are using domain account to connect to vCenter.

One thing to try is to increase the resources (Memory and CPU's) that the vMA appliance has allocated to it.
If the vMA appliance is not sized correctly, that could cause the intermittent login issue.

Hi tgriep,

We didn't add any new KPI before the problem arise.

Previously we are not facing same problem. Suddenly after upgrading vCenter from version 5 to 6.5.0. We are start facing the problem.

For more info current use is below. Still we are facing same issue.

top - 13:06:20 up 384 days, 15:45, 1 user, load average: 1.31, 1.31, 1.23
Tasks: 147 total, 2 running, 145 sleeping, 0 stopped, 0 zombie
Cpu(s): 13.6%us, 2.7%sy, 0.0%ni, 83.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 10021M total, 8186M used, 1834M free, 254M buffers
Swap: 133M total, 15M used, 118M free, 7543M cached


free -m
total used free shared buffers cached
Mem: 10021 8145 1876 0 254 7543
-/+ buffers/cache: 346 9674
Swap: 133 15 118

First. make sure you are running the latest version of the plugin, you can find the latest version on the plugin here.
https://exchange.nagios.org/directory/P ... re/details

If that doesn't help, enable debugging and check the log file to see what could be causing the issue.
--debug
• Generates a LOT of verbose information about what the plugin is doing
• Creates the file /home/vi-admin/box293_check_vmware_debug_log.txt
• If the debug file exists it will be overwritten