You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, gettin an error while running Elasticsearch Analyzer in docker container
Describe the bug
When attempting to execute the Cortex Elasticsearch Analyzer, I encountered the following error message:
{
"errorMessage": "/usr/bin/env: ‘python3\\r’: No such file or directory\n",
"input": null,
"success": false
}
I suspect that the error is caused by the presence of the carriage return character ("\r") in the elk.py Python file (analyzers/Elasticsearch/elk.py). This character may be causing the file path to be incorrectly interpreted, resulting in the "No such file or directory" error for the python3 command.
To Reproduce
Steps to reproduce the behavior:
Set up the Cortex Elasticsearch Analyzer environment using the Docker containers.
Execute the analyzer, either through the provided script or manually.
Observe the error message mentioned above.
Expected behavior
The Cortex Elasticsearch Analyzer should execute successfully without any errors related to the python3 command or file paths.
Possible solutions
I think removing the carriage return character ("\r") from the elk.py Python file (analyzers/Elasticsearch/elk.py). By doing so, the file path should be correctly interpreted, and the error should be eliminated.
The text was updated successfully, but these errors were encountered:
How to fix this if I am using an dockerized instance of Cortex? I am not sure if just fixing this would solve the problem for Linux users but break it for Windows platform?
Hi there, gettin an error while running Elasticsearch Analyzer in docker container
Describe the bug
When attempting to execute the Cortex Elasticsearch Analyzer, I encountered the following error message:
I suspect that the error is caused by the presence of the carriage return character ("\r") in the elk.py Python file (analyzers/Elasticsearch/elk.py). This character may be causing the file path to be incorrectly interpreted, resulting in the "No such file or directory" error for the python3 command.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Cortex Elasticsearch Analyzer should execute successfully without any errors related to the python3 command or file paths.
Work environment
Possible solutions
I think removing the carriage return character ("\r") from the elk.py Python file (analyzers/Elasticsearch/elk.py). By doing so, the file path should be correctly interpreted, and the error should be eliminated.
The text was updated successfully, but these errors were encountered: