Jira (PUP-3347) YAML corruption in 2.6.7

[Josh Harding (JIRA)]

Title: Message Title

Josh Harding commented on an issue   Re: YAML corruption in 2.6.7 Not sure if this is related, but I get corrupt YAML files daily... I had to write a cron job to delete all .yaml files because so many clients were failing (puppet v2.6.7). In my case, the corrupt files are in /var/lib/puppet/yaml/node/HOSTNAME.yaml. When I look at them, it looks like there's extra data after what should be the end of the file. Perhaps this happens when the file is shorter and instead of writing a whole new file, it overwrites the longer file with shorter data (leaving extra data at the end). I've tried editing a corrupt file, removing the extraneous config lines, and that seems to fix it. I'm not ready to upgrade to 3.x yet, so I was hoping for a quick fix (e.g. replace O_RDWR with O_WRONLY somewhere), but I don't know Ruby... anyone else have a patch for this? Add Comment   Puppet / PUP-3347 YAML corruption in 2.6.7 Hi guys, getting YAML corruption on 2.6.7 at $dayjob: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse YAML data for node something.example.com: syntax error on line 78, col 19: `' I have no idea how to begin to troubleshoot as it is seemingly random and it doesn't happen at my other gig which is running 2.6.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.