Luke Kanies
2008-Mar-17 15:42 UTC
[Puppet Users] Re: files overridden with directories still
On Mar 13, 2008, at 10:41 PM, Ben wrote:> I am still seeing files being overridden with directories in > 0.24.3rc1. > > Is there something i can do to assist in tracking this bug down > because > it is killing me?Well, I spent most of the weekend working on this, as did Arjuna Christensen, and we''ve concluded that it''s a Ruby leak, not a leak in my own code. There is some evidence online that this kind of leak can usually be avoided by slight tweaking of the code, so we just need to track down where that leak is. At this point, the problem is finding that leak, which is mostly a question of using C-based leak detectors to figure it out. This mostly means valgrind[1], I think, although I might give DTrace on Solaris a try[2]. At this point, all I know is 1) there''s a leak, and 2) that leak eventually causes the server to start sending bad file information to the client. I don''t know what causes the server to suddenly start sending bad data, I don''t know what usage profile specifically triggers this problem, I don''t really know much at all, because I''ve never reproduced the issue. Anything anyone can do to add information to this is helpful, especially if you''re willing to put the time into helping to track the problem down. If you''re an awesome C hacker, this is your chance to help me and my pitiful C skills. 1 - http://blog.evanweaver.com/articles/2008/02/05/valgrind-and-ruby/ -- the main secret is to run the executable explicitly with ruby, rather than letting ''env'' figure it out. 2 - http://blogs.sun.com/sanjeevb/date/20050614 -- To define recursion, we must first define recursion. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Arjuna Christensen
2008-Mar-17 20:20 UTC
[Puppet Users] Re: files overridden with directories still
I''ve not been able to track down what, in particular, is causing the issue; Puppet running under Valgrind here is too slow to compile configurations or fetch plugins. If I could work how to make it a little faster, I might be able to track it down. Arjuna Christensen | Systems Engineer Maximum Internet Ltd DDI: + 64 9 913 9683 | Ph: +64 9 915 1825 | Fax:: +64 9 300 7227 arjuna.christensen@maxnet.co.nz| www.maxnet.co.nz -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Luke Kanies Sent: Tuesday, 18 March 2008 4:42 a.m. To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: files overridden with directories still On Mar 13, 2008, at 10:41 PM, Ben wrote:> I am still seeing files being overridden with directories in > 0.24.3rc1. > > Is there something i can do to assist in tracking this bug down > because > it is killing me?Well, I spent most of the weekend working on this, as did Arjuna Christensen, and we''ve concluded that it''s a Ruby leak, not a leak in my own code. There is some evidence online that this kind of leak can usually be avoided by slight tweaking of the code, so we just need to track down where that leak is. At this point, the problem is finding that leak, which is mostly a question of using C-based leak detectors to figure it out. This mostly means valgrind[1], I think, although I might give DTrace on Solaris a try[2]. At this point, all I know is 1) there''s a leak, and 2) that leak eventually causes the server to start sending bad file information to the client. I don''t know what causes the server to suddenly start sending bad data, I don''t know what usage profile specifically triggers this problem, I don''t really know much at all, because I''ve never reproduced the issue. Anything anyone can do to add information to this is helpful, especially if you''re willing to put the time into helping to track the problem down. If you''re an awesome C hacker, this is your chance to help me and my pitiful C skills. 1 - http://blog.evanweaver.com/articles/2008/02/05/valgrind-and-ruby/ -- the main secret is to run the executable explicitly with ruby, rather than letting ''env'' figure it out. 2 - http://blogs.sun.com/sanjeevb/date/20050614 -- To define recursion, we must first define recursion. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---