On Jun 30, 2009, at 3:48 PM, Brice Figureau wrote:
>
> Hi,
>
> I happen to read open tickets from time to time, and I found that many
> time people getting a puppet error post the error message without a
> stack trace.
> Usually James or Luke answer by asking a stack trace informing the
> user
> about the --trace option. So the user usually runs puppetd with --
> trace.
> Unfortunately about 50% of the time the error is on the server side,
> so
> a --trace on puppetd only show a trace to the REST system :-(
> So we add another round trip: this is frstrating for the user because
> she find the system more complex, and this is frustrating for us
> because
> we have to wait a long time before to even start working on a fix,
> which
> in turn is more frustrating for the users...
>
> I was wondering lately if we couldn't:
>
> 1) Inconditionally run puppetmasterd with --trace (this is completely
> harmless, has no performance penalty)
I don't really like this, partially because most people only care
about traces when filing tickets and also because I've tended to be a
bit lazy about tracing and I expect there are more traces than people
really want to see. I could be convinced, but that's my initial
thought.
>
> 2) add a message on the client when we get an exception from the
> network that the error is server side and the user should have a
> look in
> their master log.
That is a good idea.
--
Is life worth living? That is a question for an embryo, not a man.
--Samuel Butler
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
