Issue #2299 has been updated by James Turnbull. Category set to transactions Status changed from Unreviewed to Needs more information Assigned to set to Luke Kanies
Luke - I think this is fixed in 0.25.0? ---------------------------------------- Bug #2299: Node YAML files being corrupted on puppet master server http://projects.reductivelabs.com/issues/2299 Author: Greg Boug Status: Needs more information Priority: Normal Assigned to: Luke Kanies Category: transactions Target version: Complexity: Unknown Affected version: 0.24.8 Keywords: There appears to be a case where the node YAML file for a given host gets corrupted. Error messages start appearing in the messages file of the client like these: May 25 08:24:32 s_lo...@client puppetd[29059]: [ID 702911 daemon.error] (//Node[default]/filesecurity/File[/etc/default/passwd]) Failed to retrieve current state of resource: Could not parse YAML data for node CLIENT.domain.com: syntax error on line 46, col 18: ` operatingsystem: Solaris' Could not describe /filesecurity/passwd-CLIENT: Could not parse YAML data for node CLIENT.domain.com: syntax error on line 46, col 18: ` operatingsystem: Solaris' at /etc//opt/csw/puppet/modules/filesecurity/manifests/init.pp:12 This issue was *possibly* triggered by circumstances outside the control of the Puppet Master (like a network failure), but its the way Puppet handles this issue that I'm more concerned about... I have seen this happen a few times under different circumstances - usually the corruption is just an entry split across two lines - not a huge corruption. The solution I have used is to remove the file which causes Puppet to rebuild it from the client the next time it is triggered. What would be better would be to detect the failure and attempt to rebuild first before alerting. Obviously it would be better to not have the corruption in the first place, but given the existance of custom facts and other code-based add-ons, this is unlikely to be something that Puppet can stop from happening. Would also be preferable to have it retry a set number of times - otherwise it could in theory get into an infinate loop... -- 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 -~----------~----~----~----~------~----~------~--~---
