Issue #1684 has been reported by nslm. ---------------------------------------- Bug #1684: puppetmasterd fails assertion when log directory doesn't already exist and client sends log http://projects.reductivelabs.com/issues/show/1684
Author: nslm Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.5 Keywords: Using puppetmasterd straight out of RH EPEL under CentOS 5.2 with the ruby-ldap module When I add a new machine to puppet, and attempt a first connection the client bombs out with puppetreports.report: #<EOFError: end of file reached> And the puppetmasterd bombs out silently on the server. Having run an strace on the puppetmasterd it appears to be receiving a SIGABORT (usually caused by a failed assertion) Just prior to this it attempts an lstat on "/var/puppet/reports/XXXXX.bath.ac.uk" (where XXXXXX.bath.ac.uk is the hostname of the machine I was adding at the time) If I manually create the directory (chowned to puppet:puppet) prior to running the client, then the master doesn't bomb out, the client succeeds and everything is happy. Subsequent updates all seem to work fine. While this may be the same bug as 506 it definately is NOT a load issue. There was negligible load on the master at the time. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
