Troubleshoot the "[Errno 111] Connection refused" error when installing the Elasticsearch plugins
When installing the Elasticsearch monitoring plugins, you may encounter the following error:
URL Error [Errno 111] Connection refused: This error usually indicates that the Elasticsearch client is unable to establish a connection to the Elasticsearch server.Here are some steps to troubleshoot the issue.
- Validate if Elasticsearch is running: You can use the following command to check if Elasticsearch is running:
curl -X GET "localhost:9200/"
If Elasticsearch is running, you should see a JSON response with details about the cluster. - Examine the bind address: Elasticsearch typically binds to localhost (127.0.0.1) by default. If you've changed the bind address, ensure you're using the correct address to connect. Also, check the elasticsearch.yml configuration file for the network.host setting.
- Check the port: Confirm that you are connecting to the correct port. Elasticsearch usually uses port 9200 by default, though this can be modified in the elasticsearch.yml configuration file.
- Check if Elasticsearch is bound to a specific IP: If Elasticsearch is bound to an IP address other than localhost, you'll need to include the server's IP address where you've installed the agent to connect with Elasticsearch and obtain metrics.
- Verify the Elasticsearch Cluster Health URL: Ensure the Elasticsearch Cluster Health URL is functioning as intended, as this is the URL utilized by our plugin to retrieve Elasticsearch metrics. Use the following command to check this:
curl -X GET "localhost:9200/_cluster/health"
Once you've made changes based on the checks above, restart the Site24x7 server monitoring agent or re-register the plugin. Within five minutes, you should be able to view performance metrics in Site24x7.
If the issue persists, reach out to support@site24x7.com with the plugin details.
Related Articles
Troubleshoot "[Errno 111] Connection refused" error when installing Tomcat plugins
When installing Tomcat plugins, you may encounter the following error: We failed to reach a server. Reason: [Errno 111] Connection refused: This error indicates that your client is unable to establish a connection to the Tomcat Manager URL, but the ...Troubleshoot "[Errno 111] Connection refused" error for RabbitMQ plugins
When installing the RabbitMQ plugin, you may encounter the following error: urlopen error [Errno 111] Connection refused: This error usually occurs when the plugin tries to connect with the RabbitMQ server but is unable to establish a connection. ...Troubleshoot the [Errno 111] Connection refused error for Oracle plugins
When installing Oracle database monitoring plugins, you may encounter the following error: DPY-6005: cannot connect to database. [Errno 111] Connection refused This error indicates that there is an error connecting to the Oracle database server. Here ...Troubleshoot Error 404, Error 111, and "no host given" error when installing the Apache plugin
When installing the Apache monitoring plugin, you may encounter the following errors: Error_code : URL Error no host given: The "no host given" error message typically indicates an issue with a URL or request that lacks a hostname. If you encounter ...Troubleshoot connection errors in the MySQL plugin
When configuring the MySQL plugin, you may encounter the following errors: Error : Connection Error - This error typically indicates that there is a problem establishing a connection to the database. Sometimes, this message is supplemented with an ...