Issue #7836 has been updated by Joe McDonagh.
Just noticed on both that node, and another one with the corruption, multiple copies of puppet agent in memory. I don't have a root cause for that since the lock file should stop that from happening. ---------------------------------------- Bug #7836: YAML corruption in 2.6.7 https://projects.puppetlabs.com/issues/7836 Author: Joe McDonagh Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.7 Keywords: yaml Branch: 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, but on a different platform. Removing the yaml in question and running the agent again fixes it. While not fixing whatever the root cause is, what are the implications of wrapping the yaml parsing bit of code inside a begin-rescue to try and catch this exception, invalidate the data, and try once more before really failing? I haven't looked at the code so I don't even know if that's feasible, just throwing it out there. -- 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.
