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

syslog forwarding stopped working with Nomad v0.6.3-rc1 #3182

Closed
shantanugadgil opened this issue Sep 10, 2017 · 2 comments
Closed

syslog forwarding stopped working with Nomad v0.6.3-rc1 #3182

shantanugadgil opened this issue Sep 10, 2017 · 2 comments

Comments

@shantanugadgil
Copy link
Contributor

Upgrading the client agent to version Nomad v0.6.3-rc1 makes syslog forwarding to a central server stop working.
It works fine with Nomad v0.6.2

Nomad version

Server: Nomad v0.6.3-rc1

Agent:
Nomad v0.6.3-rc1
Nomad v0.6.2

Operating system and Environment details

CentOS 7 (with latest updates)

Issue

Upgrading the Nomad agent on the client machine to version v0.6.3-rc1 makes syslog forwarding to a central server stop working.

Reproduction steps

update agent to Nomad v0.6.3-rc1; stop and start the job.
(you'll see that the logs don't appear on the central server)

replace the agent version with Nomad v0.6.2; stop and start the job.
(you'll see that the logs appear on the central server)

Nomad Server logs (if appropriate)

???

Nomad Client logs (if appropriate)

???

Job file (if appropriate)

relevant config section:

...
config {
  logging {
    type = "syslog"

    config = {
      syslog-address = "tcp://local-logs.example.com:10514"
      tag            = "my_task_tag"
    }
  }
...

Regards,
Shantanu

@dadgar
Copy link
Contributor

dadgar commented Sep 10, 2017

Seems like the offender: #3135. Needs investigation

@github-actions
Copy link

github-actions bot commented Dec 8, 2022

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants