Well I've somehow managed to get it down to just the error on the
masterhttp.log file:

Could not prepare for execution: Got 1 failure(s) while initializing:
change from absent to file failed: Could not set 'file on ensure:
Permission denied - /var/log/puppet/masterhttp.log

There's obviously something wrong with the file permissions but I don't
know what.

# cd /var/log/puppet
# ls -al
total 12
drwxr-x---  2 puppet puppet 4096 2012-03-14 17:21 .
drwxr-xr-x 17 root   root   4096 2012-03-16 06:25 ..
-rw-rw----  1 puppet puppet 2977 2012-03-14 17:22 masterhttp.log
#

We also don't have SELinux configured. Only thing installed is libselinux1.

Apache2 runs as www-data but I think it was like that prior to this problem.

/var is not read-only. I did think of that and verified it before my
initial post.

On Thu, Mar 15, 2012 at 5:39 AM, jcbollinger <[email protected]>wrote:

>
>
> On Mar 14, 2:00 pm, Justin Lloyd <[email protected]> wrote:
> > I'm suddenly getting the below errors from Rack during puppetd -t
> > (excerpted from the pink HTML output and cleaned for readability):
> >
> > Could not prepare for execution: Got 10 failure(s) while initializing:
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/yaml;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/rrd;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/reports;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/facts;
> > change from absent to file failed: Could not set 'file on ensure:
> > Permission denied - /var/log/puppet/masterhttp.log;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/ssl;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/state;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/lib;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/bucket;
> > change from absent to directory failed: Could not set 'directory on
> ensure:
> > Permission denied - /var/lib/puppet/server_data
> >
> > I'm not sure what I may have changed that would cause this now. Thoughts?
>
>
> The agent (i.e. puppetd) needs to run privileged.  It sounds like you
> are starting it manually, so are you running it as root or via sudo?
>
> Alternatively, if your master is running SELinux in enforcing mode,
> then it is possible that starting the agent manually does not confer
> the same privileges that running it as a service does.  You can test
> this by switching to permissive mode.
>
> Or is /var [on a] read-only filesystem?  That's a long shot, because
> such a situation would probably cause a lot of other problems system-
> wide.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" 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-users?hl=en.
>
>


-- 
“We don’t need to increase our goods nearly as much as we need to scale
down our wants. Not wanting something is as good as possessing it.” --
Donald Horban

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 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-users?hl=en.

Reply via email to