Once you have finished Installing the Management Pack (Kubernetes) and Configuring the Management Pack (Kubernetes), 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 (Kubernetes), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.
The following errors are possible:
Incorrect Bearer Token
Error Message: "Request GET https://host:port/version is unauthorized: Check that credentials are correct."
Recommended Solution: Verify that the Bearer Token you specified when Creating a Credential (Kubernetes) is correct.
Error Message: "Unknown host. Check that host is correct."
Recommended Solution: Verify that the hostname you specified when Creating an Adapter Instance (Kubernetes) is correct.
Error Message: "Resource https://host:port/version was not found. Check that the host and/or API version are correct."
"Connection refused: host:port. Check that host is correct, and required port(s) are open."
Recommended Solution: Verify that the hostname and port(s) you specified when Creating an Adapter Instance (Kubernetes) are correct, that the specified port(s) are open, and that you are using a supported API version. See: System Requirements (Kubernetes).
Failed Kubelet Collection
Error Message: "Kubelet collection failed on # of # Nodes." -or- "Kubelet collection failed on all Nodes."
- If the kubelets require authentication, ensure that the specified Bearer Token when Creating a Credential (Kubernetes) is valid for them.
- Ensure that the SSL settings are correct when Creating an Adapter Instance (Kubernetes): No SSL for HTTP, No Verify/Verifyfor HTTPS.
- curl -k -XGET -H "Authorization: Bearer <token>" https://<kubelet-host>:<kubelet-port>/stats/summary/
- Default kubelet ports: HTTPS: 10250, HTTP: 10255
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/KubernetesAdapter/ 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.Caution: 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.