ESX monitoring login/logout

[snapon_admin]

Just wondering if this is expected behavior or not and, if not, how to fix it. We're monitoring our ESX servers using the VMware plugin wizard that cam preinstalled in XI and have noticed that the user we created on the server is logging in and out aver 5-10 seconds constantly. This is clogging the ESX logs and makes troubleshooting actual problems extremely difficult. Is this something that is supposed to happen with this check or am I missing something?

Edit: See attached screenshot of the log.

[tmcdonald]

Do you have just the one service check? Or do you have multiple? It looks like you have 6 logins in a 5-minute period, and 5 minutes is the default check interval for most things, so I would wager to guess that you have 6 ESX checks.

[sreinhardt]

Unfortunately, thats how vmware choose to make the sdk work, so yes it is fully expected. Box293 has a new agent and wizard out for vmware that you might want to take a look at instead: http://exchange.nagios.org/directory/Pl ... re/details

[snapon_admin]

Yeesh, ok yeah that's annoying. I'll take a look at that plugin, thanks. Looks like it uses vSphere? Is that using passive checks using NRDP? We also found this one while looking into this issue: http://exchange.nagios.org/directory/Pl ... er/details Is that one similar to the one you linked or would one be better than the other?

[slansing]

I've personally tested the new plugin and guide by Box, it works great! It actively queries a vMA system via ssh. You can use it for vCenter/vSphere, or ESX I believe. It's all in his documentation.

[snapon_admin]

K, sweet. We'll look into that, Thanks!

[slansing]

Great! Let us know if you need help.

[Box293]

Unfortunately, thats how vmware choose to make the sdk work, so yes it is fully expected. Box293 has a new agent and wizard out for vmware that you might want to take a look at instead: http://exchange.nagios.org/directory/Pl ... re/details

You will come across the same login/logout behaviour with box293_check_vmare, it's just how the VMware SDK works.

It will work with stand alone ESX(i) hosts, a vCenter server is not required. It's all there in the documentation