I'm sure this is probably an easy fix, but I cannot seem to resolve this
issue. The puppetmaster starts correctly and so does the puppet agent,
which receives the update correctly if I restart the puppet agent
service manually or during the timed updates; however, if I perform an
"puppet kick", it just fails with the following error:
Triggering agent1.example.org
Host agent1.example.org failed: Got 1 failure(s) while initializing:
change from directory to file failed: Could not set 'file on ensure: Is
a directory - /var/lib/puppet/facts
agent1.example.org finished with exit code 2
Failed: agent1.example.org
I am running puppet 2.6.4, Centos 5.5, and ruby 1.8.5-5.el5_4.8 on both
puppetmaster and agent. Here is my /var/lib/puppet directory on the
puppetmaster:
drwxr-xr-x 9 root root 4096 Feb 8 10:57 ./
drwxr-xr-x 15 root root 4096 Feb 8 11:19 ../
drwxr-x--- 2 root root 4096 Feb 8 10:57 client_data/
drwxr-x--- 3 root root 4096 Feb 8 10:57 client_yaml/
drwxr-x--- 7 root root 4096 Feb 9 13:17 clientbucket/
drwxrwxrwx 2 root root 4096 Feb 8 10:57 facts/
drwxr-xr-x 2 root root 4096 Feb 8 10:57 lib/
drwxrwxrwt 2 root root 4096 Feb 9 13:17 run/
drwxr-xr-t 3 root root 4096 Feb 9 13:17 state/
And in my /etc/puppet/auth.conf on the puppet agent, I have the
following (mention in release notes somewhere):
path /run
method save
allow *
And, in my /etc/puppet/puppet.conf on the puppet agent (note, the server
is not puppet.example.org):
[agent]
server = myserver.example.org
report = true
listen = true
puppetdlog = /var/log/puppet/puppet.log
logdir = /var/log/puppet
httplog = /var/log/puppet/http.log
autoflush = true
Any help would be greatly appreciated.
Thank you,
Edwin
> Hello puppet world,
>
> I'm sure this is probably an easy fix, but I cannot seem to resolve this issue. The puppetmaster starts correctly and so does the puppet agent, which receives the update correctly if I restart the puppet agent service manually or during the timed updates; however, if I perform an "puppet kick", it just fails with the following error:
This is incredibly similar to a problem I've been having with the puppet master[1]. Let me know if you find a resolution.. no one has replied to my posting or to earlier postings about similar issues from other users.
[1] <http://groups.google.com/group/puppet-users/browse_thread/thread/531d110306636003?hl=en#>
If I find a resolution, I'll let you know, but as of yet, I do not have
a fix. After tracing a little into the code on the puppetmaster side, I
believe the error comes from the puppet agent and not on the puppet
master, but I cannot confirm this definitively. I have also tried
setting the chmod and the owner on the /var/lib/puppet/facts with no avail.
If anyone has any other suggestions as to what to look into, that would
be greatly appreciated.
Thanks,
Edwin