Skip to content
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

console output: check stdout being available #2035

Closed
urso opened this issue Jul 14, 2016 · 2 comments

Comments

@urso
Copy link
Collaborator

commented Jul 14, 2016

Check stdout being available when init the console output. Return error and quit beat if check fails.

@urso urso self-assigned this Jul 14, 2016

@andrewkroh

This comment has been minimized.

Copy link
Member

commented Jul 14, 2016

@inqueue

This comment has been minimized.

Copy link
Contributor

commented Jul 14, 2016

The error looks like this when beats is running as a service where there is no stdout:

Jul 14 14:51:02 grok /usr/bin/filebeat[22191]: log.go:113: Harvester started for file: /var/log/nginx/error.log
Jul 14 14:51:04 grok /usr/bin/filebeat[22191]: output.go:92: Error bulk publishing events: write /dev/stdout: invalid argument
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.