-
Notifications
You must be signed in to change notification settings - Fork 1.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
Docker changing default syslog format causes nomad logs not work as expected #1386
Comments
Just as an FYI. It does not look like docker actually switched to rfc5424. But does look like they changed from the DefaultFormatter to the UnixFormatter formatter.go https://github.com/docker/docker/blob/v1.11.0/daemon/logger/syslog/syslog.go#L238 The problem with the switch to the UnixFormatter is that instead of the time looking like |
@a86c6f7964 thanks! I updated the title accordingly. |
Not sure which approach y'all wanted to take, but I put in a pull request where I try to parse both types of logs. |
@wuub they merged my pull request to master. any chance you can confirm that it fixes your problem? |
@a86c6f7964 I won't be able to build and roll out my own binary this week, sorry :( but it seems that hashicorp is baking 0.4.1 as we speak and I'll definitely test that ASAP |
@wuub Did you get a chance to test this? |
@diptanu I'm testing it right now |
👍 I can confirm that current master branch works as expected with docker 1.11.2. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
v0.4.0
Operating system and Environment details
Issue
When using newer docker versions, mismatch in syslog formats causes all logs to have their prefixes lstriped as shown below (moby/moby#20121)
It also probably causing all logs to land in
.stderr
output (bad serverity detection?)I'll try to setting
--log-opt syslog-format=rfc3164
and let you know if this is reliable short term hotfix.Reproduction steps
Nomad Server logs (if appropriate)
n/a
Nomad Client logs (if appropriate)
n/a
Job file (if appropriate)
n/a
The text was updated successfully, but these errors were encountered: