So these three hosts have been upgraded from 6.0 to 6.5 to 6.7 and were initially loaded with a custom HPE ESXi 6.0 image.
I reloaded one host with a clean install to 6.7U3 (non-hpe) and it immediately started reporting to the esx health monitor once properly configured.
Something in the multiple ...
Search found 2 matches
- Thu Oct 15, 2020 10:04 pm
- Forum: VMWare ESX Host Health Monitor
- Topic: ImportError: No module named yaml (Error 10061, connection refused from GUI)
- Replies: 2
- Views: 7032
- Thu Oct 08, 2020 4:21 pm
- Forum: VMWare ESX Host Health Monitor
- Topic: ImportError: No module named yaml (Error 10061, connection refused from GUI)
- Replies: 2
- Views: 7032
ImportError: No module named yaml (Error 10061, connection refused from GUI)
Hello! First post but we've been using ESX Health Monitor plugin for years now. Have had a few hiccups here and there but we have been able to work through them all.
Last week, we updated three ESX hosts--all HPE Proliant Gen 9 ML350--to 6.7 U3 and the plugin stopped working for each of them.
CIM ...
Last week, we updated three ESX hosts--all HPE Proliant Gen 9 ML350--to 6.7 U3 and the plugin stopped working for each of them.
CIM ...