Issue #4600 has been updated by Markus Roberts. Status changed from Unreviewed to Investigating
Could you try it with the testing branch, which has a fix to #4527 (the "can't save facts to the code store" bug for the 2.6.x series) that you hit trying 2.6.1rc2? ---------------------------------------- Bug #4600: file server problems running under passenger http://projects.puppetlabs.com/issues/4600 Author: Steve Feehan Status: Investigating Priority: Normal Assigned to: Category: Target version: Affected version: 2.6.0 Keywords: passenger, fileserving Branch: We're running puppet via passenger-2.2.15. We are upgrading from a working 0.25.4 installation. Upon upgrading 2.6.0 (and applying the patches in #4367, #4319 and #4378) I still have one remaining issue: <pre> err: /Stage[main]/Auth/File[/etc/pam.d/chsh]: Could not evaluate: Error 400 on SERVER: Not authorized to call find on /file_metadata/files/pam.d/chsh Could not retrieve file metadata for puppet:///files/pam.d/chsh: Error 400 on SERVER: Not authorized to call find on /file_metadata/files/pam.d/chsh at /export/home/puppet/manifests/classes/auth.pp:49 </pre> This only happens when running under passenger, it works OK when running via webrick. And it only happens for our top-level [files] module (ie. one that is defined in fileserver.conf and not w/in a module). Files served from within a module-specific files directory work OK. I've tried with the default auth.conf and with no auth.conf (which I think should be the same). The fileserver.conf looks like: <pre> [files] path /export/home/puppet/files allow *.ourdomain.com [plugins] allow *.ourdomain.com </pre> The file resource referenced in the error above look like: <pre> file { "/etc/pam.d/chsh": source => "puppet:///files/pam.d/chsh", owner => "root", group => "root", mode => 0644; } </pre> Versions are: <pre> puppet: 2.6.0 (w/ patches mentioned above) passenger: 2.2.15 ruby: 1.8.7 rack: 1.2.1 </pre> While picking an affected version, I saw that there were an rc1 and rc2 available. I've now tried both: rc1 fails with the same error, rc2 fails w/ the error in #4527 and doesn't get far enough to demonstrate the error in this ticket. Steve -- 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.
