-
Notifications
You must be signed in to change notification settings - Fork 181
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
consul not logging on Upstart #182
Comments
You got closer but an issue with permissions remains (you can't write logs in /var/log as a consul user).
I have tested this out and it works as expected on debian/ubuntu (with upstart) but I am not sure about rhel/centos. |
You can.../var/log/consul is touched and chown to consul:consul during On Monday, November 14, 2016, Jure Žvelc [email protected] wrote:
|
I just checked and I can confirm owner/g is consul:consul so it seems it is something else... Can you check if stopping/restarting upstart service works as expected? If I try to restart it I get |
What about this: This also works for me. |
The only difference is it would totally wipe out the log each restart since Restarts are a different issue but I don't think it worked under sudo On Tuesday, November 15, 2016, Jure Žvelc [email protected] wrote:
|
consul is not logging when using upstart - at least on Ubuntu.
/var/log/consul
will remain empty.This is due to a bug introduced in df10349 .
This line is incorrect because
&>>
is bash syntax, it is not compatible withbin/sh
.This should resolve the issue:
The text was updated successfully, but these errors were encountered: