Issue #13584 has been updated by Chris Price.
After further investigation it looks like Puppet::Util#exit_on_fail is probably the main culprit of this type of issue. It catches exceptions and calls "log_exception", with no way of knowing whether or not our logging has been initialized yet. ---------------------------------------- Bug #13584: in daemon mode, master swallows errors during startup https://projects.puppetlabs.com/issues/13584#change-59240 Author: Chris Price Status: Accepted Priority: Urgent Assignee: Chris Price Category: logging Target version: Telly Affected Puppet version: Keywords: Branch: Because of the way that logging is handled / initialized during master startup, failures that occur before the logging is completely initialized seem to just disappear into the void. This makes it very tricky to diagnose problems that happen during startup, e.g. during acceptance testing on the CI nodes. Would be extremely useful to find a way to get the master to keep STDOUT/STDERR alive until logging has been successfully initialized, or register a "bootstrapping" log destination for use during startup so that these errors don't just disappear. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
