I think I solved my problem. I changed my fileserver.conf from: # This file consists of arbitrarily named sections/modules # defining where files are served from and to whom
# Define a section 'files' # Adapt the allow/deny settings to your needs. Order # for allow/deny does not matter, allow always takes precedence # over deny [files] path /etc/puppet/files # allow *.example.com # deny *.evil.example.com # allow 192.168.0.0/24 [plugins] # allow *.example.com # deny *.evil.example.com # allow 192.168.0.0/24 to # This file consists of arbitrarily named sections/modules # defining where files are served from and to whom # Define a section 'files' # Adapt the allow/deny settings to your needs. Order # for allow/deny does not matter, allow always takes precedence # over deny [files] path /etc/puppet/files allow * # allow *.example.com # deny *.evil.example.com # allow 192.168.0.0/24 [modules] allow * [plugins] allow * # allow *.example.com # deny *.evil.example.com # allow 192.168.0.0/24 and now everything works! I still have no idea why this error starting appearing. Kyle http://www.kylehall.info Mill Run Technology Solutions ( http://millruntech.com ) Crawford County Federated Library System ( http://www.ccfls.org ) Meadville Public Library ( http://www.meadvillelibrary.org ) On Wed, Jun 22, 2011 at 11:29 AM, Kyle Hall <kyle.m.h...@gmail.com> wrote: > Hello All, > I'm just starting with puppet and I've run into an issue I cannot > figure out. I'm trying to sync the home directory for a user from a > home directory stored on my puppet server. Here is my manifest code: > > > user { "public": > ensure => present, > shell => '/bin/bash', > home => '/home/public', > managehome => true, > password => 'chestnut', > } > > file { "public-home": > path => '/home/public', > ensure => directory, > owner => 'public', > group => 'public', > recurse => true, > replace => true, > purge => true, > ignore => '.git', > source => 'puppet:///files/users/home/public', > require => User['public'], > } > > The files are stored in /etc/puppet/files/users/home/public > > What is really strange is that it was working fine, except that it > appeared that the replace and purge options were not working. Then, > after a few test runs, I started seeing this error: > > err: Could not run Puppet configuration client: Error 400 on SERVER: > Not authorized to call find on /file_metadata/files/users/home/public > at /etc/puppet/manifests/public-base.pp:58 > > Any ideas? I tried chmod'ing the files directory on the server to 777, > but that did not help. I've moved the file around a few times trying > different things without success. If I comment out the file section, > my catalog runs just fine. > > Thanks, > Kyle > > http://www.kylehall.info > Mill Run Technology Solutions ( http://millruntech.com ) > Crawford County Federated Library System ( http://www.ccfls.org ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
