Databases
StackOverflow2013
Postsdbo
POPuppet error: "Could not retrieve local facts: 404 Not Found"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
    primarykey
    data
    text
    <p>I'm running Puppet version 0.25.4 from Ubuntu 10.04. When I run:</p> <pre><code>puppetd --test </code></pre> <p>on one machine, this is the error I get:</p> <pre><code>err: Could not run Puppet configuration client: Could not retrieve local facts: 404 Not Found </code></pre> <p>I am able to "sign" the machine certificate from my master, but after that, nothing more. Running the same version of Puppet on another machine, with the same configuration, works without any problem.</p> <p>Even passing:</p> <pre><code>--debug --verbose </code></pre> <p>as command line arguments doesn't give me more clues. Any ideas?</p> <p>= Update to add more context =</p> <p>This is the puppet.conf file I have on all the machines:</p> <pre><code>[main] logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter pluginsync = false templatedir = $confdir/templates prerun_command = /etc/puppet/etckeeper-commit-pre postrun_command = /etc/puppet/etckeeper-commit-post [puppetd] server = puppet report = true </code></pre> <p>This is the output of running</p> <pre><code>puppetd --debug --verbose --test </code></pre> <p>from the error-machine:</p> <pre><code>debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/run/puppet/puppetd.pid]: Autorequiring File[/var/run/puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/HOSTNAME.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys/HOSTNAME.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/public_keys/HOSTNAME.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: Finishing transaction -613406248 with 0 changes debug: Using cached certificate for ca, good until Tue Nov 22 13:59:42 UTC 2016 debug: Using cached certificate for HOSTNAME, good until Sat Nov 26 11:31:35 UTC 2016 debug: Executing '/etc/puppet/etckeeper-commit-pre' debug: Executing '/etc/puppet/etckeeper-commit-post' err: Could not run Puppet configuration client: Could not retrieve local facts: 404 Not Found </code></pre> <p>and is basically the same of the other machines, apart from the fact that this does not do anything after executing etckeeper-commit-pre (and etckeeper is not installed in any machines).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMilo Casagrande
    1. USMilo Casagrande
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. USTony Maro
      1. VTFavorite
    3. VO
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo your client 'submits' facts as a GET request to the server and I believe it stores it in a file somewhere in /var/lib/puppet/yaml/facts/hostname.yaml ... does such a file exist for the client? I'd be more interested in the puppet master logs ... run it in the foreground in debug mode and see what it says.
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. USKen Barber
    2. COThe "facts" file for the machine that gives the error does not exists. The cool part is that the server doesn't print anything if started in the foreground when I try to launch `puppetd --test` from the client. The error looks like is on the "local" (client) side of things.
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. USMilo Casagrande
    3. COThe error is remote '404 Not Found' ... thats a HTTP error - check your HTTP logs to confirm if its even connecting to that web server (and you see the 404 on the server). Did you run the puppet master using --debug when it was in the foreground?
      singulars
      1. POPuppet error: "Could not retrieve local facts: 404 Not Found"
      1. USKen Barber
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload