Troubleshooting

This topic describes how to troubleshoot issues for PATROL for Elasticsearch.

Tip

For more information about known issues, see Known-and-corrected-issues.

If you encounter any problems using this KM, BMC Support might request you to enable KM debug.

Enable the following debug variables:

Variable	Value	Log file location
*/ESK/CONT/<label>/pslDebug*	0 = Disable 1 = Enable	The log file is located at the %patrol_home%\esk\log directory
*/ESK/CONT/<label>/javaDebugLevel*	0 = Disable 1 = Enable	The log file is located at $PATROL_HOME/log/trace/<hostname>/<port>/issow.log

Annotation message for MonitoringStatus (ESK_CLUSTER) attribute	Details
Elasticsearch service on <hostname> ,port <port> is down.	Elasticsearch service is not running on the connection node.
Host unreachable OR Unknown host : <hostname> / unknown host	Indicates network issue, as REST connection cannot be established between PATROL Agent host and Elasticsearch connection host.
Authentication failed! No data will be collected.	Invalid authentication credentials for Elasticsearch connection host.
Access Denied! No data will be collected.	Collector received http error 403, data collection is not possible. Verify roles/permissions assigned to Elasticsearch user.
Collection Error : Connection node <hostname>,port <port> Possible causes : Master not discovered exception OR HTTP Error 503 - Service Unavailable.	Collector received http error 503, data collection is not possible.
Unable to connect to Elasticsearch service on <hostname> ,port <port>. Possible causes : Invalid port or host unreachable.	Invalid port or host unreachable. Please make sure configured hostname is correct.

On this page