VMWare connector

hello

Which plugin are you using? the current with the daemon, or the new api one? (or an old one with the perlsdk?)

I’m asking because I planning an upgrade soon to 25.10 but I could not test the vcenter plugin yet.

also what is “crash” (symptom, error message)

Assuming  you use the vcenter plugin with the daemon, and your crash is that daemon stopping, there is a log and a config file

config is either here /etc/sysconfig/centreon_vmware

or /etc/default/centreon_vmware

it should contains something like that

# centreon_vmware command line options
OPTIONS="--config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=error"

as you can see there is a log and a severity, it should “information” by default if memory serves, but you should check the log file to see if there is an error logged when the daemon stop/crashes

nce I performed the update, none of my vCenter plugins are working anymore. I can no longer see the health status, snapshots, or anything that used to be reported.
I had set up the additional monitor with the proper credentials.
Now, whether I use the configuration file or the monitoring setup, it always returns a login error.

please give more information, we can’t help  you blindly.

• what plugin are you using (there are multiple version), you didn’t answer that.

• what version did you upgrade from? (if it was from 24.04 or below, there were some specific step to do for vmware plugin during the upgrade)

• please provide also output of the error and the command

(do it from the command line in the shell, you can get the full command line from the detail panel, and copy the command with the blue button

then paste that command in the ssh shell of the poller. you could also add “  --debug” in the command to have more output, and you can mask login/password if they are shown in clear)

Hello,

It happen to me today on 24.10.18 when I did an apt update.

Previous updates leave centreon_vmware.json file empty and use content from centreon_vmware.pm.deprecated file. Now, previous credential are not “converted” into the new file. I fill it and it works.

It looks to only happen on serveurs udpated from 24.04.x to 24.10.18. One on them was update to 24.10.5 before (or something like this...), files were all ok. I don’t remember if I did it manually or not for this one...

Nope. I just finished updating our servers. Most of them already had their valid configuration file.