Open grosbedos opened 6 months ago
Hello :)
I'm not sure to understand if your plugin was working at a moment or if it never worked?
I tried to trace the call of functions that could lead to the output Vsan is not enabled in vmware connector
and assuming you moved the files as indicated, ensuring that they had opening rights. I think I see where the class call did not work (here) but I need to do further research and consult with the development team to understand better this part.
Hi,
The vmware connector is working, but not for vsan. (for example, i can monitor the cpu-cluster)
If i add the option: vsan_sdk_path => '/usr/share/perl5/VMware/' in /etc/centreon/centreon_vmware.pm, the vmware connector doesn't work anymore, nor for cpu, nor vsan.
Best regards.
Hello :)
Thank you for this feedback, we have taken note of this information and opened the associated procedure, we will inspect the problem and come back to you when we know more about it.
Hi,
I'm not able to monitor vsan with a debian 11. The plugin says : Vsan is not enabled in vmware connector
I have of course tried the issue 1785:
So I added the option: vsan_sdk_path => '/usr/share/perl5/VMware/' in /etc/centreon/centreon_vmware.pm
After that, when i restart the centreon_vmware daemon, they are error in the log file :
And the vmware connector doesn't work anymore.
Environment:
Can you help me ?
Best regard