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

Fix docker user specified syslogging #3184

Merged
merged 1 commit into from
Sep 11, 2017
Merged

Fix docker user specified syslogging #3184

merged 1 commit into from
Sep 11, 2017

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Sep 10, 2017

Fixes #3182

@shantanugadgil
Copy link
Contributor

Hi,
I did the following:

git checkout b-docker-logging
git pull
git log -p
make pkg/linux_amd64/nomad

Copied the binary to one of my client machines.
Logs appear correctly when I stop and start the service, but Nomad keep crashing upon startup.
Possibly related to #3188
(FWIW, I have stats reporting to a statsite enabled).

For now, I am reverting to version 0.6.2 GA

@dadgar
Copy link
Contributor Author

dadgar commented Sep 11, 2017

@shantanugadgil can you build off of stable-v0.6.3 branch. Master isn't stable right now

@shantanugadgil
Copy link
Contributor

just confirming; I too am seeing the same traceback:

2017/09/11 06:38:27 [INFO] (runner) creating new runner (dry: false, once: false)
fatal error: sync: RUnlock of unlocked RWMutex
goroutine 356 [running]:
runtime.throw(0x146faf6, 0x21)
...

@dadgar ok, I'll try building from stable-v0.6.3.

Q: But your syslog fix isn't merged to the branch stable-v0.6.3, right?

@dadgar
Copy link
Contributor Author

dadgar commented Sep 11, 2017

You should be able to rebase it onto the stable branch or cherry pick the commit.

@dadgar
Copy link
Contributor Author

dadgar commented Sep 11, 2017

Can you post the full stack trace as well! Thank you

@shantanugadgil
Copy link
Contributor

@shantanugadgil
Copy link
Contributor

@dadgar I chery picked the single commit from b-docker-logging into stable-v0.6.3 and can see the logs on the central server correctly.

@dadgar dadgar merged commit 49c4189 into master Sep 11, 2017
@dadgar dadgar deleted the b-docker-logging branch September 11, 2017 16:31
@shantanugadgil
Copy link
Contributor

hi @dadgar @schmichael
this hasn't made its way into 0.6.3 GA right?
because I am seeing the same behavior with the 0.6.3 that I downloaded.
reverting to the file I have compiled myself works as expected with the logs appearing on the central server?

Regards,
Shantanu

@dadgar
Copy link
Contributor Author

dadgar commented Sep 12, 2017

@shantanugadgil Ah shoot. I am sorry I forgot to cherry pick that commit into the branch! 0.7.0 will be out soon, sorry about that.

@shantanugadgil
Copy link
Contributor

Thanks for the confirmation! Till 0.7.0 is out, I'll live with the file I have! 😄

@shantanugadgil
Copy link
Contributor

Hi @dadgar
just wondering if this is in the 0.7.0 branch (?)
Asking as I didn't see it in the changelog
https://github.com/hashicorp/nomad/blob/master/CHANGELOG.md

waiting for 0.7.0 with much anticipation! 👏 👏 😁

@dadgar
Copy link
Contributor Author

dadgar commented Sep 14, 2017

@shantanugadgil Added to changelog

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, 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 Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants