Support Forum

We have had a lot of changes happen to our automate system. The main is that we have moved to a cloud hosted system. And I just noticed today that the esx health monitor has not scanned the probes in like 2 months. I have tried to adjust and readd the agents and such, but still they are not running the scans on the schedule.

If you click the squid logo it should bring up an About page with your license date on it.

Licenses are handed by Automate Hostnames. The name you provide when signing up for the subscriptions process. This is manageable in the www.plugins4automate.com portal for your account, under "LabTech Host Name" field.

When you edit this the next billing cycle will use the new hostname for license and will automatically update for you. You can also send a email to support if you need us to trigger an change sooner.

I'll try to do some digging here based on your support account to see if I can find you in the portal. If I can match you up I will see what your checking in now as and update your information.

Otherwise send me your account and new hostname to support and I'll fix that for you.

Ok I found you and checked your licenses. They look valid and you are checking in to them.

So if it is not "working" it most likely not a license issue.

So next thing is to look at the "probe" agents to see if you are getting script schedules taking place on these agents to probe the ESX host?

If the scripts are not scheduling then we need to capture the Automate host logs for the plugins automation.

Now that your hosted you will need to ask support for this log.

C:\Program Files\LabTech\Logs\Plugin_VMWareESXHealthMonitor.txt

In the logs you will find: "Send probe command to agent ID#"

Is the probes listed here? if so then look at agents script logs to see if script is scheduled?

If that is then see what it returned when it ran last?

There will be execute commands during the same time as script logs time frame. These would be the commands the script is trying to execute. If you follow the commands log for that time frame you will see what the script was doing and where it may have failed.


Please post the data you find so we can help further.

Cubert wrote: ↑Thu Mar 31, 2022 12:55 pm If you click the squid logo it should bring up an About page with your license date on it.

Licenses are handed by Automate Hostnames. The name you provide when signing up for the subscriptions process. This is manageable in the www.plugins4automate.com portal for your account, under "LabTech Host Name" field.

When you edit this the next billing cycle will use the new hostname for license and will automatically update for you. You can also send a email to support if you need us to trigger an change sooner.

I'll try to do some digging here based on your support account to see if I can find you in the portal. If I can match you up I will see what your checking in now as and update your information.

Otherwise send me your account and new hostname to support and I'll fix that for you.

Our host name is correct there. Has been since migration.

Cubert wrote: ↑Thu Mar 31, 2022 1:26 pm Ok I found you and checked your licenses. They look valid and you are checking in to them.

So if it is not "working" it most likely not a license issue.

So next thing is to look at the "probe" agents to see if you are getting script schedules taking place on these agents to probe the ESX host?

If the scripts are not scheduling then we need to capture the Automate host logs for the plugins automation.

Now that your hosted you will need to ask support for this log.

C:\Program Files\LabTech\Logs\Plugin_VMWareESXHealthMonitor.txt

In the logs you will find: "Send probe command to agent ID#"

Code: Select all

LTAgent  v220.57	 - 3/31/2022 8:04:15 AM	 - Plugin VMWareESXHealthMonitor, Version=5.0.0.3, Culture=neutral, PublicKeyToken=null: Send probe command to agentID 33:::
LTAgent  v220.57	 - 3/31/2022 8:04:15 AM	 - Plugin VMWareESXHealthMonitor, Version=5.0.0.3, Culture=neutral, PublicKeyToken=null: P4A ESX HealthMonitor Maintenance Script Starting:::
LTAgent  v220.57	 - 3/31/2022 8:04:15 AM	 - Plugin VMWareESXHealthMonitor, Version=5.0.0.3, Culture=neutral, PublicKeyToken=null: P4A ESX HealthMonitor Maintenance cleaning up stail records:::
LTAgent  v220.57	 - 3/31/2022 9:04:36 AM	 - Plugin VMWareESXHealthMonitor, Version=5.0.0.3, Culture=neutral, PublicKeyToken=null: P4A ESX HealthMonitor Scanner thread starting:::
LTAgent  v220.57	 - 3/31/2022 9:04:36 AM	 - Plugin VMWareESXHealthMonitor, Version=5.0.0.3, Culture=neutral, PublicKeyToken=null: P4A ESX HealthMonitor info HOUR = 9 Interval = 4:::

Is the probes listed here? if so then look at agents script logs to see if script is scheduled?

If that is then see what it returned when it ran last?

There will be execute commands during the same time as script logs time frame. These would be the commands the script is trying to execute. If you follow the commands log for that time frame you will see what the script was doing and where it may have failed.


Please post the data you find so we can help further.

Ok, so I need to get this from the server itself. Correct. I am on a cloud hosted one so I will have to get with connectwise.

LTAgent v220.77 - 3/25/2022 11:26:01 PM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/25/2022 11:36:04 PM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/25/2022 11:46:08 PM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/25/2022 11:56:10 PM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 12:10:14 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 12:20:40 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 12:30:44 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 12:40:46 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 12:51:40 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 1:01:47 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor Scanner thread starting:::
LTAgent v220.77 - 3/26/2022 1:01:47 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor info HOUR = 1 Interval = 2:::
LTAgent v220.77 - 3/26/2022 1:12:04 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 1:22:11 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 1:32:55 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 1:42:58 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 1:53:01 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor service is post TOTH (Top Of The Hour)- Skipping probe executions:::
LTAgent v220.77 - 3/26/2022 2:03:10 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor Scanner thread starting:::
LTAgent v220.77 - 3/26/2022 2:03:10 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor info HOUR = 2 Interval = 2:::
LTAgent v220.77 - 3/26/2022 2:03:10 AM - Plugin VMWareESXHealthMonitor, Version=4.0.0.62, Culture=neutral, PublicKeyToken=null: P4L ESX HealthMonitor License expired:::


This is what my logs say.

It says my license is good till april. but I just don't get it.

If you open the the main ESX Monitor link from the tools menu, Does it show valid?

can you PM me the IP address of your automate host? I will go capture the request coming in to see what its sending us and what we respond with..

Also, just so we are on the same playing field.


What does your version say if you click the small squid icon in to of main window?