Help! Could not autoload puppet/provider/package/rpm

[staceyt...@gmail.com]

Hi all,

I am using Puppet agent 3.7.3 on Red Hat Linux. On one of my machines, when I run "puppet agent --test", I received error:

Puppet (err): Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock
Puppet (err): Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock
Puppet (err): Could not retrieve catalog from remote server: Could not intern from text/pson: Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock
Puppet (err): Could not retrieve catalog; skipping run

Any clue why this happens? 

Thanks,
Stacey

[Wil Cooley]

SELinux enabled post-install, so various bits don't have the right labels?

It might take a while, but "restorecon(8)" might help? Maybe start with `restorecon -n -v -r /`?

Wil 

[staceyt...@gmail.com]

Wil,

Thank you for the reply.

Yes, I checked and found that SELinux was enabled post-install.

Then I set SELinux to Permissive and reinstall everything, but still same error.

Can you explain more detail about `restorecon -n -v -r /`?

Thanks,
Stacey

[vishc...@gmail.com]

I had obtained a similar error on my dev machine CentOS 6.4 with Puppet 3.4.3. Reinstalling Puppet again on my dev machine did not help.

I had noticed that the /tmp directory permissions were changed somehow in my dev machine. I had to fix it to get puppet agent working again.

Expected : 

drwxrwxrwt 27 root root 12288 Jul 18 15:25 /tmp/

The Fix : 

sudo -i
chown -R root:root /tmp
chmod 1777 /tmp

Note: when I obtained this puppet error, I also obtained another while rebooting my VM.

There is a problem with the configuration server /usr/libexec/gconf-sanity-check-2-exited with status 256

Fixing the permission/ownership rights on /tmp directory fixed both errors for me.