Its possible, I realized I had a recurse => true when I removed it seems to work. In my email I just typed it up real quick and didnt paste the actual type I have in my manifest. So that would explain it as under that directory there are device files and recursively is failing to set the perms.
One minor complaint, the debug output from puppetd doesn't really explain what the exact issue is and where its failing. ie, would be good if it said it was attempting to chown/chmod a directory or file. Thx for the assistance. -Chris On Thu, Jul 15, 2010 at 10:59 AM, Patrick Mohr <kc7...@gmail.com> wrote: > I might know the problem. Do you have device files or sockets in > /var/named/chroot? If so puppet might be trying to manage the permissions > on stuff in that folder and failing the sanity check when is sees they > aren't regular files. > > > On Jul 15, 2010, at 7:21 AM, Christopher Johnston wrote: > > They exist for sure.. > > # ls -ld /var/named/ > drwxr-x--- 6 root named 4096 2010-07-15 06:20 /var/named/ > # ls -ld /var/named/chroot/ > drwxr-xr-x 5 named named 4096 2010-07-15 06:20 /var/named/chroot/ > > > On Thu, Jul 15, 2010 at 12:09 AM, Patrick Mohr <kc7...@gmail.com> wrote: > >> I'd check to see if /var/named exists or if /var/named/chroot is a >> symlink. >> >> On Jul 14, 2010, at 2:24 PM, Christopher Johnston wrote: >> >> > I don't see anything out of the ordinary here, seems like its not >> honoring the type as a directory but as a file any ideas? >> > >> > err: //bind::slave/File[/var/named/chroot]: Failed to generate >> additional resources using 'eval_generate': Cannot manage files of type >> characterSpecial >> > >> > file { '/var/named/chroot': >> > ensure => directory, >> > owner => named, >> > group => named, >> > mode => 0755, >> > require => Package['bind-chroot']; >> > } >> > >> > >> > -- >> > 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<puppet-users%2bunsubscr...@googlegroups.com> >> . >> > For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> -- >> 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<puppet-users%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> > > -- > 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. > > > -- > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- 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.