-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filebeat throws Unexpected file stat rror: stat /dev/stdin: bad file descriptor #1029
Comments
Which OS are you using? |
The agent is running inside a Docker container based on busybox. The binary is the linux-386 |
What is the data you are feeding into stdin? Do you have any reproduction steps? |
This happens when filebeat hits the end of input on stdin (pipe closed, end of file). I was expecting filebeat to exit cleanly once it hits the end of stdin. My intended use case of filebeat is to run something like Logstash startup takes ~30s there and only does ~1k events per second, even without grok filters. |
@chrono This is very similar to the request here: https://github.com/elastic/filebeat/issues/134 @fiunchinho If the error above is because stdin was closed, I think the error is somehow correct? |
Every time a chunk of data is received through stdin, that error will appear on the logs. Maybe the log message just needs to be improved? |
This message isn't an issue anymore if you look at the latest filebeat output log:
|
In filebeat 1.1, when using prospector for stdin, it works fine but filebeat throws erros
The prospector configuration is only
With logstash output, but I guess that's not relevant. Logstash receives everything fine.
The text was updated successfully, but these errors were encountered: