Issue #1190 has been updated by andrew. Status changed from Closed to Assigned Complexity changed from Easy to Unknown
This is not entirely a duplicate of 1200, nor will the loop proposed for 1200 fix this. Just making puppetd never die is not going to fix this. ---------------------------------------- Bug #1190: Puppetd exits if it receives a bad certificate http://reductivelabs.com/redmine/issues/show/1190 Author: init Status: Assigned Priority: Normal Assigned to: andrew Category: executables Target version: 0.24.5 Complexity: Unknown Patch: Insufficient Stage: Accepted When starting puppetd in daemon mode, a bad certificate received from the puppet master causes the client to exit. This is (according to me) undesirable behavior. Why not just retry once in a while like when there is no signed client certificate on the master for this host? As of now, if the client is reinstalled without first removing the old puppet client certificate, the system administrator must then manually login to the client to restart the puppet daemon (after removing the old certificate). In my opinion, a daemon should not exit unless in encounters a truly fatal error, and this error is not one of them. An example of a truly fatal error would be a missing dependency. Unfortunately, I do not know Ruby (yet), so I cannot fix it. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
