Troubleshooting the Management Pack (MongoDB)

Once you have finished Installing the Management Pack (MongoDB) and Configuring the Management Pack (MongoDB), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

• Test Connection Errors
• Adapter and Collector Log Files

Test Connection Errors

When Creating an Adapter Instance (MongoDB), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Authentication Failed

Error Message: “Authentication failed. Please check your credentials and/or SSL certificate.”

Action: Ensure that your MongoDB user name and password is correct the SSL certificate is valid if ‘Validate Certificate Against Truststore’ Advanced Settings configuration field is set to True.

SSL Authentication Required

Error Message: “SSL Authentication Required.”

Action: Ensure that SSL is enabled (set to True) in the appropriate Advanced Settings configuration field.

PKIX Path Building Failed

Error Message: “PKIX path building failed. Unable to find valid certification path to requested target.”

Action: Ensure that the SSL certificate is in the correct truststore.

Change Authentication Type to ‘Default’

Error Message: Change Authentication Type to ‘Default’. Unsupported mechanism PLAIN.”

Action: Change Authentication Type to ‘Default’ when adding your credential.

MongoClient does not have any server addresses

Error Message: “MongoClient does not have any server addresses.”

Action: Ensure that connections can be made to the hostnames listed in the Host configuration field.

Not authorized on admin to execute command

Error Message: “Not authorized on admin to execute command <command> with username=”<username>” to on <host>/admin>.”

Action: Make sure the user being used for this host has permissions to run the specified command.

Unable to find databases with server address

Error Message: “Unable to find databases with server address list <hosts>.”

Action: Make sure the specified host has databases.

Could not create any MongoClients

Error Message: “Could not create any MongoClients connecting to mongods.”

Action: Make sure the mongods are up.

Adapter and Collector Log Files

You can review adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

• Adapter log files are located in the $VCOPS_BASE/user/log/adapters/mongodb_adapter3/ folder.
• Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

1. Navigate to Administration > Logs.
2. Expand the MASTER folder, then select the COLLECTOR folder.
3. Click the Edit Properties icon.

4. In the Root logger level drop-down menu, select the desired option:

   • The default logging level is warning.
   • To troubleshoot issues, set the logging level to info.

   • To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.

     Note: If you set the logging level to debug , log files can become large very quickly. Set the logging level to debug only for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.