Issue #13584 has been updated by Chris Price.

After further investigation, it appears that the main situation where this 
causes problems is with code *outside* of puppet.  As far as I can tell, if we 
have a failure from within puppet code, it will most likely be logged to the 
log file as hoped / expected.  (There may be some cases where this isn't true 
but I haven't found an easy repro case yet.)

However, if third-party code (e.g. webrick) triggers the error, we don't have 
control over how it logs... thus, if it writes to stdout/stderr, we are 
susceptible to losing that info.

Therefore, an approach that relies on a "bootstrap" log destination is not 
going to work... we'll have to address this by changing how we deal with 
stdout/stderr.
----------------------------------------
Bug #13584: in daemon mode, master swallows errors during startup
https://projects.puppetlabs.com/issues/13584#change-59236

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.

Reply via email to