On Thu, 2012-05-31 at 10:38 +0100, Matthew Burgess wrote: > On Wed, May 30, 2012 at 6:58 PM, Brice Figureau > <brice-pup...@daysofwonder.com> wrote: > > > Probably that the stacktrace you'll get with --trace will be enough for > > the moment. Also if you can cat the facts file (feel free to obfuscate > > the private data you might have in there), that might help. > > OK. so another buglet here is that if you have '--debug --verbose > --trace' on the puppetmaster command line, you get no stacktrace. As > soon as I take '--verbose' out, I get the attached stacktrace. > puppet-load's logging has a similar issue in that '--verbose' seems to > override '--debug' so I get no debug output if both options are > specified.
Yes, the order is important, and --verbose will override --debug. > Anyway, attached are the debug log from the puppet master and the > facts file suitably obfuscated. > Can you run your master on the console (add --no-daemonize to the command-line)? Because due to how Puppet reports errors during compilation, the full stacktrace is only printed on the console, and I'm missing the important bits :) Thanks, -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
