Connection issue of elastalert2 with elasticsearch #1354
-
I am trying to connect elastalert2 with elasticsearch but unable to make connection below is my docker-compose file version: '3.6' Logstash: Kibana: elastalert: volumes: networks: ######################## This is the folder that contains the rule yaml filesrules_folder: /opt/elastalert/rules run_every: buffer_time: Connect with TLS to Elasticsearchuse_ssl: False Verify TLS certificatesverify_certs: False alert_time_limit: ################################################## Getting below error in elastalert2 logs elasticsearch.exceptions.ConnectionError: ConnectionError(HTTPConnectionPool(host='elasticsearch', port=9200): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd8567d1f70>: Failed to establish a new connection: [Errno 111] Connection refused'))) caused by: ConnectionError(HTTPConnectionPool(host='elasticsearch', port=9200): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd8567d1f70>: Failed to establish a new connection: [Errno 111] Connection refused'))) |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
@nsano-rururu please help me out with it |
Beta Was this translation helpful? Give feedback.
-
@jertel please help me out with it |
Beta Was this translation helpful? Give feedback.
-
Perhaps when you bring up the full 4 container cluster the ES server isn't fully initialized, so ElastAlert2 can't connect and exits. Have you tried adding |
Beta Was this translation helpful? Give feedback.
Perhaps when you bring up the full 4 container cluster the ES server isn't fully initialized, so ElastAlert2 can't connect and exits.
Have you tried adding
restart: always
to the ElastAlert2 docker compose block? Or have you tried manually restarting the ElastAlert2 container a few minutes after ES starts?