Skip to main content

Hello,

I'm trying to set up monitoring for an ESX server and I've encountered some difficulties that I'd like to share here to get some help.

I've installed the Vmware ESX plugin and configured the container as follows:
 


When executing the command: /usr/lib/centreon/plugins/centreon_vmware_connector_client.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=tools-vm -- display-description --vm-hostname='vxr1-witness' --filter

 

I get the following error message: UNKNOWN: Container connection problem.

I also checked the Centreon interface, where I receive the same error message :

 

Additionally, it's worth mentioning that the ping to the ESX server is functioning properly :
 


The user configured in the container is an administrator, so it doesn't seem to be a permissions issue.

Checking the logs in /var/log/centreon/centreon_vmware.log, I found the following lines:



Use of uninitialized value $server_from_url in transliteration (tr///) at /usr/local/lib64/perl5/VMware/VICommon.pm line 465.
2024-04-11 12:14:14 - 'default' Login to VirtualCenter server failed: Can't call method "getChildrenByTagName" on an undefined value at /usr/local/lib64/perl5/VMware/VICommon.pm line 2383.

I also tried recreating a new user on our ESX, but the problem persists. I'm at a loss as to how to resolve this issue. Has anyone here encountered this problem before or have any ideas on what might be wrong with my configuration?

Thanks in advance for your help and have a great day!

​​​​​​​

Hello,

Does you ESX url on the conf file has “/sdk” at the end?

 

Hello Vcoum,

No, the configuration link did not contain /sdk at the end. I just tried it, but it didn't work.
Additionally, when I test my ESX URL on the web with /sdk at the end, it is not reachable.


 


 


However, if I don't put /sdk at the end, the web page is reachable.
 

So @regis_shr you put /sdk at the end and restart centreon_vmware process without success?

Hello,
Can you please try with ESX IP instead of URL.
Example:- url =>’https://10.#.#.#/sdk’, 
and i think config file is case sensitive, make sure your url is in small later.

also try with same host name and container name.
 

Hello @Cm123,

I tested by adding the URL: ==> https://10.XX.XX.XX/sdk and https://10.XX.XX.XX/ (without /sdk). The issue remains the same. I modified the configuration using the same hostname, but it's still the same thing.



I still wonder about the configuration of my ESX because when I connect to it with /sdk, it doesn't lead me anywhere. However, just with the IP, I land on my ESX correctly.
What is the purpose of /sdk?

 


@Laurent  I added /sdk at the end but it didn't work, and my ESX is also not reachable with /sdk from the web. Could I have a configuration issue with my ESX perhaps?

you certificat look like not valid, may be it could be the root cause

Hi @regis_shr! Have you managed to solve your problem? If so, don't forget to click on BEST ANSWER. Or simply tell us how you personally managed to solve the problem. This will help other people with the same problem to easily find the solution. Thank you 

Hi @Fabrix,

Unfortunately, I haven't had the time to delve deeper into the certificate issue yet, but I think @Laurent is right, it most likely stems from the certificate problem. I've encountered a similar issue with SSL on my WSUS server monitoring.

Reply


Terms & ConditionsCookie settings