Solved

Problem monitoring VMware infrastructure


Badge +1

Hi there,

I’m trying to monitor VMWare Vshepre on premise infrastructure.

I just followed this topic : https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/

This just worked for a couple of days and suddenly with no explainable reason didnt !

I get an error when configuring the connector :

UNKNOWN: Container connection problem 

I had a look into /var/log/centreon/centreon_vmware.log and just got this error :


default' Login to VirtualCenter server failed: Server version '' at 'https://myvcenterserver:443/sdk/vimService.wsdl' unsupported.

My current Centreon Version is 22.04 (tried with 22.10 too and didnt worked)

My VSphere infrastructure runs 7.0.3 version (vcenter servers ans ESXi

Does anyone can help me ?

Thanks

icon

Best answer by omercier 31 August 2023, 13:13

View original

19 replies

Badge +2

Hi,

i have the same message because an admin change vcenter name. if your vcenter not change.

You can try:

re-enter password in your vcenter and check again

 

Badge +1

Hi @bannavong thanks for answer

Unfortunatly no change in vcenter name and i tried to re-enter password too

Connecting directly to esxi hosts using local credentials works

Userlevel 5
Badge +14

first thing first, does this url in you error message anwser and display the xml webservice in a browser

and can you curl/wget it from your poller?

in a browser, without needing a password

curl -k https://myvcenterserver/sdk/vimService.wsdl   (I removed :443)

this is the same output on vcenter 6 or 7 and contains no relevant information except “yes it a vcenter”

 

if this not that output, check you dns resolution, check your services on vcenter

try curl the same path but with the ip address instead of the dns name 

curl -k https://1.2.3.4/sdk/vimService.wsdl   

 

can you also paste your /etc/centreon/centreon_vmware.pm file (hide your password)

I mainly need to see which url you have setup for the ‘default’ vcenter you should have something like that :

{'url' => 'https://myvcenterser:443/sdk',

 

try without :443

{'url' => 'https://myvcenterserver/sdk',

or the ip

{'url' => 'https://1.2.3.4/sdk',

(note there is nothing after /sdk in the uri)

 

remember to restart your daemon/service “centreon_vmware” on the poller after each modification of the config file

(I also suggest you purge/move the log file each time, as there is no timestamp in the log, it’s hard to debug, or open 2 shell, one with tail -f of the log and one to restart the service)

 

there may also be issue with the login/password itself, account locked out or expired, or a change in role/attribution on the vcenter

 

Badge +1

first thing first, does this url in you error message anwser and display the xml webservice in a browser

and can you curl/wget it from your poller?

in a browser, without needing a password

curl -k https://myvcenterserver/sdk/vimService.wsdl   (I removed :443)

this is the same output on vcenter 6 or 7 and contains no relevant information except “yes it a vcenter”

 

if this not that output, check you dns resolution, check your services on vcenter

try curl the same path but with the ip address instead of the dns name 

curl -k https://1.2.3.4/sdk/vimService.wsdl   

 

can you also paste your /etc/centreon/centreon_vmware.pm file (hide your password)

I mainly need to see which url you have setup for the ‘default’ vcenter you should have something like that :

{'url' => 'https://myvcenterser:443/sdk',

 

try without :443

{'url' => 'https://myvcenterserver/sdk',

or the ip

{'url' => 'https://1.2.3.4/sdk',

(note there is nothing after /sdk in the uri)

 

remember to restart your daemon/service “centreon_vmware” on the poller after each modification of the config file

(I also suggest you purge/move the log file each time, as there is no timestamp in the log, it’s hard to debug, or open 2 shell, one with tail -f of the log and one to restart the service)

 

there may also be issue with the login/password itself, account locked out or expired, or a change in role/attribution on the vcenter

 

I also having problem with this plugin.

/var/log/centreon/centreon_vmware.log
2023-04-20 22:13:24 - 'xxxxxx' Login to VirtualCenter server failed: Server version unavailable at 'https://x.x.x.x:443/sdk/vimService.wsdl' at /usr/local/share/perl5/VMware/VICommon.pm line 734.

 

tried both using ip address and resolution.

 

also tried curl command and result same as yours.

 

What should we do to resolve this one?

Userlevel 5
Badge +14

mmh has there been a change in the centreon daemon? 

can you type rpm -qa | grep -i virt

 

my output is this : centreon-plugin-Virtualization-VMWare-daemon-3.2.5-20220816072422.el7.centos.noarch (I have not updated in a while)

can you check your version? (and if you have a version different 3.2.5  try installing this one, I know it works for me)

 

but frankly, if the daemon does not work and you did everything correctly i advise both of you to contact the support

 

could you also post what I asked : the config file .pm (masking just the password)

Badge +1

Hi,

 

I got centreon-plugin-Virtualization-VMWare-daemon-3.2.4-20220517103908.el7.centos.noarch

 

how can I update it? tried to update my plugin still same version installed.

 

Im kinda noob in this thing.

 

Thank you for response

 

Userlevel 5
Badge +14

have you tried what it says in the doc VMware vCenter v6 | Centreon Documentation

Install this daemon on each needed poller:

yum install centreon-plugin-Virtualization-VMWare-daemon
Badge +1

yes I tried that. Im thinking need to update my centreon-engine for both of my pollers and central server. Im running with 

Centreon Engine 21.10.2

 

might need to udpate this on first before I update it to 3.2.5 

 

Userlevel 5
Badge +14

possibly

I looked at the daemon https://github.com/centreon/centreon-vmware 

3.2.5 is the latest from august last year, I wouldn’t advise you to try and install it manually on your poller, but a few things seems to have been changed between 3.2.4 and 3.2.5 (like ssl connexion options) so maybe it’s that (there are also some perl vmware sdk modifications, for vmware7, i don’t talk git well enough to understand all, except to see that there were changes)

 

you could try to make a new poller from scratch (new alma 8 vm with the install script), no need to plug it to your existing setup, just install the vmware daemon and try to see if it run before upgrading your full setup

here are a few commands to install a 22.04 poller from scratch on alma8 (basic server install, no packages needed)

curl -L -s https://raw.githubusercontent.com/centreon/centreon/22.04.x/centreon/unattended.sh > install.sh

chmod +x install.sh

./install.sh install -t poller

then  yum install centreon-plugin-Virtualization-VMWare-daemon and try your config file

Userlevel 5
Badge +11

Hi @FDM31 did the solution you got from this conversation work for you? If yes, could you do us a solid and mark the answer that helped you as the "Best Answer"? That way, other folks who encounter the same issue can find the fix in a jiffy. Thanks 😉

Badge +5

Hello, Same for me the vmware daemon is not found on Centreon 23.04 OS: AlmaLinux 9 :

https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/

Userlevel 4
Badge +12

Hi @L3eO,

Sorry for that! We are going to fix it.

Userlevel 1
Badge +4

Hi @L3eO,

Sorry for that! We are going to fix it.

Hi @omercier

 

Do you have any idea when it will be fixed ?

 

Kélian

Badge +1
Same problem with Redhat 9 / Centreon 23.04.Still no date for a solution?
Userlevel 4
Badge +12

Hi, I can’t give you a release date, but the task is in progress.

Userlevel 1
Badge +4

Hi @omercier ,

 

Do you have any updates about this pls ? 

 

Kélian

Userlevel 4
Badge +12

Hi @Kélian 

Sorry, it has been fixed since then. Can you try again?

Userlevel 1
Badge +4

Hi @Kélian 

Sorry, it has been fixed since then. Can you try again?

Ok i’ll try, during my OS migration tests

Userlevel 1
Badge +4

Hi @Kélian 

Sorry, it has been fixed since then. Can you try again?

Hi @omercier,

 

Thanks, it works on Alma Linux 9 now :)  

Reply