Nagios Support Forum

I have followed the instructions and the temp config file no longer exists. However the problem still exists. It appears that the information about the hosts is being saved somewhere else. Do you know the location of the vMA configuration file. I would like to verify that it or any other associated config file does not contain information that is making Nagios believe that the virtual center is already configured. Maybe even the messaging associated with that IP (10.1.11.201).

Here are the results of the verify:
Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Warning: Duplicate definition found for service 'Swap Usage' on host 'Web-LoadBal-v' (config file '/usr/local/nagios/etc/services/10.3.0.214.cfg', starting on line 79)
Warning: Duplicate definition found for service 'Ping' on host 'Web-LoadBal-v' (config file '/usr/local/nagios/etc/services/10.3.0.214.cfg', starting on line 64)
Warning: Duplicate definition found for service 'Memory Usage' on host 'Web-LoadBal-v' (config file '/usr/local/nagios/etc/services/10.3.0.214.cfg', starting on line 48)
Warning: Duplicate definition found for service '/ Disk Usage' on host 'Web-LoadBal-v' (config file '/usr/local/nagios/etc/services/10.3.0.214.cfg', starting on line 16)
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 490 services.
Warning: Host 'CSTM 2380 Printers and Cleaner Switch' has no default contacts or contactgroups defined!
Checked 136 hosts.
Checked 4 host groups.
Checked 0 service groups.
Checked 10 contacts.
Checked 11 contact groups.
Checked 166 commands.
Checked 17 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 136 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 17 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 1
Total Errors: 0

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

I'll send you a personal message with my email address, I'll do a remote with you to resolve the problem as it'll be easier and quicker.

Thank you

Please update this thread once you have performed the remote session, whether it resolved the issue or not. That way we can either continue or properly mark this thread as closed.

The issue was that on the vMA the credential repository had the username and password for the vCenter server stored against the IP address of the vCenter server.

In the vMA settings manager on Nagios XI, the vCenter server was being referenced by it's DNS record.

When the plugin was executed by the wizard, it was trying to connect to the vCenter server using the DNS record. The vMA credential repository did not have a record for that and hence failed.

Once we added the credentials using the DNS record of the vCenter server the wizard worked fine.

Alternatively the vMA settings manager could have changed from using a DNS record to the IP address and it also would have worked.