On Feb 24, 9:53 am, Brian Ferris <bdfer...@gmail.com> wrote: > Yes to running in enforcing mode. I just tried turning enforcing mode off > with a call to "setenforce 0" and I still get the same behavior.
Hmmm. This still feels like a possibility. The SELinux context of the puppetd process is definitely different from the SELinux context of an interactive shell, so that is a difference such as you asked about. It might be worth checking your logs for denial advices. Alternatively, are you using ACLs on your filesystem? It could be that one or more of the needed jars have ACLs that prevent puppetd access, even though the base file permissions appear to allow it. Are any of the needed jars located on a remote file system? That could bring additional access rules into play that might discriminate between you and puppetd. John -- 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.
