Thanks Jason and Jared,
I think, like Jared said, that the user trying to create the tempfile
cannot write to it (this user may well be puppet, not root.
So i checked on puppetmaster:
-permissions:/etc/init.d ls -la
-rwsr-xr-x 1 root root 3727 Sep 12 22:57 puppetmaster
/var/lib/puppet/yaml$ ls -la
total 16
drwxr-xr-x 4 puppet puppet 4096 Sep 27 13:06 .
drwxrwxrwx 15 puppet puppet 4096 Sep 27 17:59 ..
drwxr-xr-x 2 root root 4096 Oct 9 15:33 facts
I also checked for disk full and inodes too.
Il giorno mercoledì 9 ottobre 2013 21:52:27 UTC+2, Jared Jennings ha
scritto:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> cannot generate tempfile
> `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
>
> warning: Not using cache on failed catalog
>
> err: Could not retrieve catalog; skipping run
>
>
>
> Security Problem?Suggestion?
>
>
>
>
>
> “Error 400 on SERVER” means that the problem outlined in the next words
> happened on the server, not the client. The details of the problem are
> after “Error 400:” there are dozens of things that can cause an error 400.
> In this case, a tempfile could not be written. Perhaps the directory
> /var/lib/puppet/yaml/facts does not exist; perhaps the user trying to
> create the tempfile cannot write to it (this user may well be puppet, not
> root, even if you ran the server as root); or perhaps the disk is full.
> That’s where to start; where you will end up I don’t know.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
