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) 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. Any thoughts on this? If we agree, I'll send a patch, -- Brice Figureau My Blog: http://www.masterzen.fr/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
