Fix Issue 492: Arkime stops capturing data in Docker SELKS #496
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… for Elasticsearch before starting capture
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes Issue 492, where Arkime would stop capturing network traffic in the Docker SELKS environment. The problem occurred because Arkime_capture sometimes started before Elasticsearch was fully ready, preventing proper indexing and causing packet capture to halt. To resolve this, a startup script (start-arkime.sh) was added that waits for Elasticsearch to be available before launching Arkime_capture. The Dockerfile was updated to use this script as the container entrypoint. This ensures that Arkime reliably starts capturing data even if Elasticsearch takes some time to initialize. The fix has been tested in a Docker Compose SELKS setup, and Arkime continues to capture traffic as expected after container startup.