Issue #3370 has been updated by Markus Roberts. Status changed from Accepted to Needs more information Assigned to changed from Markus Roberts to Robert Nagy Priority changed from Urgent to Normal
This is my third attempt to update this ticket in the past two days (redmine is acting--odd). Sorry if I sound terse, but I'm getting tired of typing this. * I'm setting the ticket to Normal from Urgent (or at least trying to) since the change in question is ~a year old, there's only this one report of the problem, and it's not clear how the fix for #1812 could cause this in isolation. * I'm assigning it back to Robert as Needs more information as there are several plausible explanations for the situation, and finding the right one depends on knowing more: ** Could some other process is trying to access the yaml files on the server and locking them? 0.24.8 would have ignored this (while possibly silently corrupting the files) ** I'm assuming that what you are saying is that only the first puppetd run works, but it is possible that you mean multiple puppetd runs work _until the puppetmaster is restarted_. Is this the case? ** Does this happen on all nodes, or only some? If only some, is it always the same ones, and are they in anyway special? ** I'm assuming it's the puppetmasterd that's on OpenBSD, is that correct? Do you have the ability to try it with an alternate puppetmasterd running on another OS (assuming it's very repeatable)? Do you have a reason for believing that it's related to OpenBSD? -- Markus ---------------------------------------- Bug #3370: YAML read/write locks broken on OpenBSD http://projects.reductivelabs.com/issues/3370 Author: Robert Nagy Status: Needs more information Priority: Normal Assigned to: Robert Nagy Category: file Target version: 0.25.5 Affected version: 0.25.4 Keywords: Branch: commit:"45144a1b9da2839fd9f8a182a8f82ecb06e17292" that introduces read and write locks broke puppet on OpenBSD. What happens is that on the first run of puppetd everything is fine, then puppetmasterd gets restarted and this error occurs: http://pastebin.ca/1841149 Then /etc/puppet/ssl gets removed and everything is fine again but only on the first run, then the same thing happens. Running --compile comes down to this: http://pastebin.ca/1841436 Reverting the changes makes puppet work again as expected. -- 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.
