Have you found a solution to this problem? I am having the same issue
after upgrading to puppet 0.25.4 and passenger.

The error message im getting is: Error 400 on SERVER: Not authorized
to call find on /file_metadata/hp_psp/opsywnsr0099.aus.optiver.com.pem
Could not retrieve file metadata for 
puppet:///hp_psp/opsywnsr0099.aus.optiver.com.pem

This will intermittently be reported on client's puppet runs and then
the next run may work correctly.

Any help with this would be appreciated.

On Apr 11, 9:57 pm, Mark Nelson <m...@tardis.cx> wrote:
> Hello
>
> I am using the following software -
>
> *Operating System:
>
> *Scientific Linux SL release 5.3 (Boron), Scientific Linux is a rebuild
> of Redhat Enterprise
>
> *Ruby version:*
>
> ruby-shadow-1.4.1-7.el5.x86_64
> ruby-irb-1.8.5-5.el5_3.7.x86_64
> grub-0.97-13.2.x86_64
> ruby-libs-1.8.5-5.el5_3.7.x86_64
> ruby-rdoc-1.8.5-5.el5_3.7.x86_64
> ruby-1.8.5-5.el5_3.7.x86_64
> ruby-augeas-0.3.0-1.el5.x86_64
> ruby-ldap-0.9.7-3.el5.x86_64
>
> *Puppet Version:
>
> *puppet-0.25.4-1.el5.noarch
> puppet-server-0.25.4-1.el5.noarch
>
> I am  getting an "Error 400 message" when I try to download a file from
> the puppet server I'm getting the following error when running puppet
> --test -dv
>
> err: //dns/File[/etc/resolv.conf]: Failed to retrieve current state of
> resource: Error 400 on SERVER: Not authorized to call find on
> /file_metadata/common/etc/resolv.conf Could not retrieve file metadata
> for puppet://puppet/common/etc/resolv.conf: Error 400 on SERVER: Not
> authorized to call find on /file_metadata/common/etc/resolv.conf at
> /etc/puppet/manifests/classes/dns.pp:8
>
> Running the puppermasterd in debug mode produces the following error
> message
>
> info: mount[files]: allowing * access
> err: Not authorized to call find on /file_metadata/common/etc/resolv.conf
>
> Both the client and the server are running on the same machine.  There
> are references to similar issues in puppet 0.25.1 I'm not sure if these
> issues are fixed in  0.25.4
>
> My configuration files are as follows -
>
> *Auth.conf *
>
> # inconditionnally allow access to all files services
> # which means in practice that fileserver.conf will
> # still be used
> path /file
> allow *
>
> *Fileserver.conf
>
> *[files]
>   path /etc/puppet/files
>   #allow *.int.tardis.cx
>   allow *
>   #deny *.examp
>
> Thanks
>
> Mark.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to