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

logging in journald #596

Open
InformatiQ opened this issue Jul 19, 2017 · 4 comments
Open

logging in journald #596

InformatiQ opened this issue Jul 19, 2017 · 4 comments
Labels
Bug Something isn't working

Comments

@InformatiQ
Copy link

Although the log4j2 config logs to console i still don't see the logs using journalctl
as far as i understand the --quiet passed to bin/elasticsearch is the issue
am I correct?

@martinb3
Copy link
Contributor

martinb3 commented Jul 20, 2017

Hi there -- yes, upstream has documented this in the systemd unit file. We are using their default shipped systemd unit files, and suggesting users drop in an override to change things, or simply supply an alternate template to this cookbook if they want to make bigger changes.

@InformatiQ
Copy link
Author

the log4j2 template in the cookbook specifies console as root logger, yet no logs are sent to console unless i remove --quiet from the systemd unit file.
so my understanding is that --quiet overrides the log4j2 config
hence any overrides in the in the properties file won't really help with that.
I have modified the systemd unit template to make --quiet configurable, so I am validating my assumption bvefore submitting a PR

@martinb3
Copy link
Contributor

martinb3 commented Jul 24, 2017

@InformatiQ This may be something you want to take upstream. It looks like it's intentional.

@martinb3 martinb3 added Bug Something isn't working upstream and removed doc labels Jul 24, 2017
@martinb3 martinb3 added this to the Support v6.0.0 milestone Dec 4, 2017
@martinb3
Copy link
Contributor

martinb3 commented Dec 4, 2017

This seems to be the case in the 6.0.0 release as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants