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
Description of the Issue (and unexpected/desired result)
Consul logs are not written to syslog, regardless if enable_syslog is set via command line or in configuration. This is only true of agents that are run as clients. On server nodes with a similar setup, I did not see any issues.
Reproduction steps
I have been able to write to syslog as a server and as a OS X client, but not as a client on Ubuntu 14.04.
Log Fragments
Not sure how to trace or determine where issue might exist.
The text was updated successfully, but these errors were encountered:
@slackpad Nope. Just checked again and did not see anything in stderr log when starting. I also tried restarting rsyslog before starting consul with syslog enabled, but that did not seem to work or showed anything in stderr log.
consul version
for both Client and ServerClient:
0.6.4
Server:
0.6.4
consul info
for both Client and ServerClient:
Server:
Operating system and Environment details
Ubuntu 14.04
configuration
:Description of the Issue (and unexpected/desired result)
Consul logs are not written to syslog, regardless if
enable_syslog
is set via command line or in configuration. This is only true of agents that are run as clients. On server nodes with a similar setup, I did not see any issues.Reproduction steps
I have been able to write to syslog as a server and as a OS X client, but not as a client on Ubuntu 14.04.
Log Fragments
Not sure how to trace or determine where issue might exist.
The text was updated successfully, but these errors were encountered: