Issue configuring VMware vCenter with box293_check_vmware

[mejokj]

Hi Team,

We are tried to configure the VMware center using the box293_check_vmware/ plugin but we got the below attached error.

We have followed all the steps mentioned in the document fro the box293 plugin the below link

https://exchange.nagios.org/components/ ... 0&cf_id=29

Tested the below command and it works fine and provides an output.

/usr/local/nagios/libexec/check_by_ssh -E 1 -t 30 -l vi-admin -H 10.3*.*.* -C "~/box293_check_vmware.pl --timeout 30 --server example.com --check Guest_Snapshot --host example1.com --warning snapshot_age:10 --critical snapshot_age:14"


Thanks

[mejokj]

Hi Team,

Please check and update on this

Thanks

[ssax]

What error are you referring to, there is no error in that screenshot, if you're referring to that output from the screenshot, if you read the output carefully it says those have ALREADY been done, it will always show that message, it does on mine as well.

What OS/version/php version are you running?

Code: Select all

cat /etc/*release
uname -a
php -v

Continue on through the steps.

[mejokj]

Hi,

Please find below the OS release output.

root@ittestnagiosxi toolsadmin]# cat /etc/redhat-release

Red Hat Enterprise Linux Server release 7.5 (Maipo)

Thanks

[ssax]

Ok, so is it working? What was listed is not an error.

[mejokj]

Hi ssax,

The plugin works fine. But by using the same plugin create another problem.

We are getting the attached error. This issue happened when we try to do force check any service/host in nagiosxi after the VMware plugin adds with box293.

Observations
==========

1) We don't see any high load in the server during the time.

2) Cluster status looks green, sent attachment as PM to you

3) Monitoring Engine status Looks Green
==========
I have attached the service config added screenshot as well.

This issue occurs multiple times now after we try to add multiple vcenter services. Sometimes we can fix the issue by doing "apply configuration" for the second time after adding the plugin.

Now we have disabled the service to avoid this issue.

We did not find any particular in the logs and not sure what is the root cause of this issue.

Could you please help us on this issue to find out the root cause.

Config check Output
=================

Checked 1644 hosts.
Checked 263 host groups.
Checked 9 service groups.
Checked 303 contacts.
Checked 25 contact groups.
Checked 326 commands.
Checked 302 time periods.
Checked 1609 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1644 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 302 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 563
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check

===============================================================

Thanks

[ssax]

Locking thread, ticket received, we will continue support through the ticket.

Thank you!