On 27/01/11 20:40, Jason Wright wrote: > On Thu, Jan 27, 2011 at 1:42 AM, Brice Figureau > <[email protected]> wrote: >> Which make me think that either you still have 0.24.x clients or I >> missed some 0.25 client feature that uses XMLRPC file serving. > > All of our OS teams upgraded to 0.25.x clients months ago. I don't > even think our manifests compile for 0.24.x clients any more and we do > not support clients earlier than 0.25.x any longer. If we do have > 0.24.x clients (and there probably are a few running around), they're > broken machines. In any case, the nodes which are reporting the 500s > which caused our Ubuntu team to open the bug in the first place are > definitely on 0.25.5. I don't know that I've reported the correct > stack traces, only some of the more common ones.
I believe you :) Can you correlate the stacktrace to a given client through the access log, and with that maybe we can find what on the client triggers this. I did a quick grep in the 0.25.5 source-code to find what could still use the xmlrpc fileserver, but couldn't find anything. Adding a couple of Puppet.info() to puppet/network/handler/fileserver.rb around line 232 to print both the client and the url would maybe help you find who is triggering this. Regarding the first stacktrace you posted in your first e-mail, I'm sure this is the writelock multiprocess issue we fixed in 2.6 and that I referred to in a previous e-mail. This is a single (ok maybe 2) line fix that is safe for you to backport to your 0.25.5 master. HTH, -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
