Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Add juju logging settings to troubleshooting for container/kvm creation #216
Conversation
|
|
|
I think logging should exist elsewhere possibly its own section. This is a good start though. |
|
I agree, I thought about starting the logging section - but its a fairly significant topic and the possibility of me writing all that tonight was close to nil, so I figured this was the best bet. Get it in troubleshooting and move it later. I'll file a bug for that. |
|
See issue #217 |
added a commit
that referenced
this pull request
Jan 6, 2015
marcoceppi
merged commit 5682f21
into
juju:master
Jan 6, 2015
chuckbutler
deleted the
chuckbutler:add-logging-trace-to-troubleshooting
branch
Jun 28, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chuckbutler commentedJan 6, 2015
It's often handy to understand why container/vm creation on a unit fails, and presently there is no way to capture that output that's very apparent to the user. By tweaking the juju logging environment settings
we can capture the TRACE of those commands yielding in more meaningful debugging sessions.