Get The Scoop On What's New
Want to know what Plugins4Automate is doing for ConnectWise Automate? Come check out our blog and find out about new products and updates that we are working on! https://www.plugins4labtech.com/blogs/blog

Probe not connecting to ESX

This forum supports the ESX Host Health Monitor plugin. When posting post screenshots of issues and any script and command logs listed in the probe consoles.
Post Reply
JvdMaat
Posts: 1
Joined: Wed Feb 21, 2018 1:31 am

Probe not connecting to ESX

Post by JvdMaat » Tue Sep 10, 2019 3:00 am

I'm having issues with a new customer, and a probe not connecting.
I tried the manual connect as detailed in another post and got this error. How do I get yaml? (Or how do I get past that error)
C:\Python27>python.exe -W ignore C:\Python27\check_esxi_hardware.py -v -H IP -U root -P "pwd"
Traceback (most recent call last):
File "C:\Python27\check_esxi_hardware.py", line 249, in <module>
import pywbem
File "C:\Python27\lib\site-packages\pywbem-0.10.0-py2.7.egg\pywbem\__init__.py", line 44, in <module>
from ._recorder import * # noqa: F403,F401
File "C:\Python27\lib\site-packages\pywbem-0.10.0-py2.7.egg\pywbem\_recorder.py", line 28, in <module>
import yaml
ImportError: No module named yaml


The ESX Health Monitor GUI has a different error (Error 10061, connection refused).
I have verified SSH is on. I can connect using PuTTY from the probe using the root credentials.
I switched the ESX probe from one server to another in the hopes that would fix it, but still the same issue.

The probe script log looks like this:
The Script(6047) was successful in the Then section.

Script: S6047 - Starting at Server Time: Monday, September 9, 2019 10:53:13 PM
Script step logging has been disabled. Please set @ScriptEngineEnableLogger@ = True in your script to enable function logging.
Script logging has been enabled.
L3 F20 SetType(P1):10 Parameter(P2):'C:\Python27\check_esxi_hardwar...' VariableName(P3):PROBEREADY T: 1.2970925
L4 F29 Message (P1): PROBE Ready -> [ 35579 ] T: 27.3027536
L5 F114 File (P1): c:\python25\python.exe Check (P2): 1 Jump (P3): 1 T: 27.3037532
L7 F154 Folder (P1): %windir%\LTSvc\ESXHealthMonitor T: 33.3091399
L8 F70 Value (P1): PROBEREADY Comparer (P2): 9 To (P3): Does Not Exist Jump (P4): :RUNPROBE T: 39.3115247
L45 F139 Note (P1): :RUNPROBE T: 39.3115247
L46 F20 SetType(P1):1 Parameter(P2):1 VariableName(P3):LOOPCOUNT T: 39.3115247
L47 F196 SQL (P1): 'SELECT ESXHost,Username,Password,Vender FROM plugin_p4l_vmware_healthmon_hosts WHERE Probe...' T: 39.3115247
L48 F139 Note (P1): :LOOPSTART T: 39.3125231
L49 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXHOSTIP T: 39.3125231
L50 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXUSERNAME T: 39.3125231
L51 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXPASSWORD T: 39.3125231
L52 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXVENDER T: 39.3125231
L53 F197 Variable (P1): sqldataset RowIndex (P2): 1 T: 39.3125231
L54 F20 SetType(P1):1 Parameter(P2):172.20.103.9 VariableName(P3):ESXHOSTIP T: 39.3125231
L55 F20 SetType(P1):1 Parameter(P2):root VariableName(P3):ESXUSERNAME T: 39.3135254
L56 F235 T: 39.3135254
L57 F20 SetType(P1):1 Parameter(P2):password redacted
VariableName(P3):ESXPASSWORD T: 43.317805
L58 F20 SetType(P1):1 Parameter(P2):auto VariableName(P3):ESXVENDER T: 43.317805
L59 F70 Value (P1): ESXPASSWORD Comparer (P2): 2 To (P3): Jump (P4): :NOPASSWORD T: 43.317805
L60 F70 Value (P1): ESXPASSWORD Comparer (P2): 8 To (P3): Exception calling Jump (P4): :NOPASSWORD T: 43.317805
L61 F109 Delimiter (P2): Variable (P3): PROBEDATA T: 43.317805
L62 F29 Message (P1): 'PROBE -> [ Traceback (most recent call last):
File "C:\Python27\check_esxi_hardware.py"...' T: 51.3552998
L63 F20 SetType(P1):1 Parameter(P2):'UPDATE plugin_p4l_vmware_healt...' VariableName(P3):SCANSQL T: 51.360295
L65 F67 Sql (P1): 'UPDATE plugin_p4l_vmware_healthmon_hosts SET LastScan = NOW(), Status = 'Traceback (most ...' T: 51.360295
L66 F109 Delimiter (P2): Variable (P3): CREATECIMDATA T: 51.3612949
L67 F70 Value (P1): CREATECIMDATA Comparer (P2): 9 To (P3): Element Name Jump (P4): :NOVALIDCIMDATA T: 55.3635608
L86 F139 Note (P1): :NOVALIDCIMDATA T: 55.3635608
L87 F29 Message (P1): No Verbose CIM Data was returned for the ESX Host [172.20.103.9] T: 55.3635608
L88 F101 ValueOne (P1): 1 Operator (P2): 0 ValueTwo (P3): 1 Variable (P4): LOOPCOUNT T: 55.3645529
L89 F70 Value (P1): LOOPCOUNT Comparer (P2): 5 To (P3): 2 Jump (P4): :LOOPSTART T: 55.3645529
L48 F139 Note (P1): :LOOPSTART T: 55.3645529
L49 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXHOSTIP T: 55.3645529
L50 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXUSERNAME T: 55.3655544
L51 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXPASSWORD T: 55.3655544
L52 F20 SetType(P1):1 Parameter(P2): VariableName(P3):ESXVENDER T: 55.3655544
L53 F197 Variable (P1): sqldataset RowIndex (P2): 2 T: 55.3655544
L54 F20 SetType(P1):1 Parameter(P2):172.20.103.10 VariableName(P3):ESXHOSTIP T: 55.3655544
L55 F20 SetType(P1):1 Parameter(P2):root VariableName(P3):ESXUSERNAME T: 55.3655544
L56 F235 T: 55.3655544
L57 F20 SetType(P1):1 Parameter(P2):pw_redacted
VariableName(P3):ESXPASSWORD T: 61.3689419
L58 F20 SetType(P1):1 Parameter(P2):auto VariableName(P3):ESXVENDER T: 61.3689419
L59 F70 Value (P1): ESXPASSWORD Comparer (P2): 2 To (P3): Jump (P4): :NOPASSWORD T: 61.3689419
L60 F70 Value (P1): ESXPASSWORD Comparer (P2): 8 To (P3): Exception calling Jump (P4): :NOPASSWORD T: 61.3699399
L61 F109 Delimiter (P2): Variable (P3): PROBEDATA T: 61.3699399
L62 F29 Message (P1): 'PROBE -> [ Traceback (most recent call last):
File "C:\Python27\check_esxi_hardware.py"...' T: 65.3731947
L63 F20 SetType(P1):1 Parameter(P2):'UPDATE plugin_p4l_vmware_healt...' VariableName(P3):SCANSQL T: 65.3751954
L65 F67 Sql (P1): 'UPDATE plugin_p4l_vmware_healthmon_hosts SET LastScan = NOW(), Status = 'Traceback (most ...' T: 65.3751954
L66 F109 Delimiter (P2): Variable (P3): CREATECIMDATA T: 65.3791962
L67 F70 Value (P1): CREATECIMDATA Comparer (P2): 9 To (P3): Element Name Jump (P4): :NOVALIDCIMDATA T: 69.3814557
L86 F139 Note (P1): :NOVALIDCIMDATA T: 69.3814557
L87 F29 Message (P1): No Verbose CIM Data was returned for the ESX Host [172.20.103.10] T: 69.3814557
L88 F101 ValueOne (P1): 2 Operator (P2): 0 ValueTwo (P3): 1 Variable (P4): LOOPCOUNT T: 69.3824537
L89 F70 Value (P1): LOOPCOUNT Comparer (P2): 5 To (P3): 2 Jump (P4): :LOOPSTART T: 69.3824537
L90 F129 Jump (P1): T: 69.3824537

Any help on where to look?
I am assuming it's the yaml issue. But why is that missing from a clean install? (Other ESX probes at other customers are working fine)

User avatar
Cubert
Posts: 1251
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: Probe not connecting to ESX

Post by Cubert » Wed Sep 11, 2019 1:44 pm

If this is a problem with the agent (Probe) installing Python,

The first thing to try is deleting c:\python27 on probe and allowing it to rescan. This will force a reinstall of python on probe. If probe has some AV on it or some other software you might see issues with installing python and updating the PATH of the service name the agent service runs under.

2nd Option is to select a different agent as the probe and let it scan. See if it has the same issues with installing python.



No modules errors are Python install issues typically due to some AV or permissions set by GPs.

Errors the reference a bad connection or no connections available / failed would say that CIM services on ESXhost are not running or have stalled.

Errors for username or pass is just that…


These are the most typical seen. Keep in mind ESX >= 6.5 had CIM service administratively disabled by default from Install. You have to administratively enable then start the services before your probes can read data.

Also see our forums at http://support.plugins4automate.com for help with VMWare plugin

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests