Once you have finished Installing the Management Pack (MEDITECH) and Configuring the Management Pack (MEDITECH), 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
- Collection Errors
- Adapter and Collector Log Files
Test Connection Errors
When Creating an Adapter Instance (MEDITECH), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host server.
The following errors are possible:
Failed to connect
Error Message: "Failed to connect."
Action: Ensure your server is running.
Failed to connect to server
Error Message: "Failed to connect to server."
Action: Verify your SMB path/host is correct when Creating an Adapter Instance (MEDITECH).
Error Message: "No protocol."
Action: Ensure you prepend your SMB share with smb:// before the path when Creating an Adapter Instance (MEDITECH).
Logon failure: unknown user name or bad password
Error Message: "Logon failure: unknown user name or bad password."
Action: Check your SMB login credentials when Creating a Credential (MEDITECH).
Problem: No metrics (or old data).
Solution: Verify MEDITECH is populating the SMB share path with .sirt files.
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/MeditechAdapter/ folder.
- Collector log files are located in the $VCOPS_BASE/user/log/ folder.
To set the base log level for the collector in vROps:
- Navigate to Administration > Logs.
- Expand the MASTER folder, then select the COLLECTOR folder.
- Click the Edit Properties icon.
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.