Nicolai, Thanks for the reply. I think I copied the /var/lib/puppet directory from another server as a last resort after trying a bunch of other things first. For the sake of argument, though, I've deleted my entire puppet installation and begun from scratch. I did a yum install of puppet and then did the following:
[root@server ~]# puppetd --server puppetmaster.domain.com -- waitforcert 30 --test err: Could not create resources for managing Puppet's files and directories in sections [:main, :puppetd, :ssl]: Could not find a default provider for file err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file info: Creating a new SSL key for server.domain.com err: Could not request certificate: Cannot save server.domain.com; parent directory /var/lib/puppet/ssl/private_keys does not exist info: Creating a new SSL key for server.domain.com err: Could not request certificate: Cannot save server.domain.com; parent directory /var/lib/puppet/ssl/private_keys does not exist info: Creating a new SSL key for server.domain.com err: Could not request certificate: Cannot save server.domain.com; parent directory /var/lib/puppet/ssl/private_keys does not exist info: Creating a new SSL key for server.domain.com err: Could not request certificate: Cannot save server.domain.com; parent directory /var/lib/puppet/ssl/private_keys does not exist info: Creating a new SSL key for server.domain.com err: Could not request certificate: Cannot save server.domain.com; parent directory /var/lib/puppet/ssl/private_keys does not exist Cancelling startup This error keeps scrolling up the screen until I ctrl-C out of it like I did above. While this is going on, I run `puppetca --sign server.domain.com` on the puppetmaster but it fails and says there is no request from the server. At this point, I create the ssl/ private_keys directory manually. I go through the above steps a few more times and it complains about the ssl/public_keys, ssl/certs and ssl/certificate_requests directories not existing so I create them as well. After all of that, I can finally get a signed ssl cert. Then I try to start the puppet service and get the following errors in syslog: Starting Puppet client version 0.25.5 Could not create resources for managing Puppet's files and directories in sections [:main, :ssl, :puppetd]: Could not find a default provider for file Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file Could not retrieve catalog from remote server: No such file or directory - /var/lib/puppet/client_yaml/catalog Using cached catalog Could not retrieve catalog; skipping run At this point, I stop puppet and create the client_yaml/catalog directories. I restart puppet and then get the following errors in syslog which is what my original question was about: Starting Puppet client version 0.25.5 Could not create resources for managing Puppet's files and directories in sections [:main, :ssl, :puppetd]: Could not find a default provider for file Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file Could not run Puppet configuration client: Could not find a default provider for file Then puppet does nothing. If you know how to fix this error or you can point out anything in my installation that's wrong, I'd greatly appreciate it. I'm more than happy to read docs, too, if you can point me to good online documentation but I've searched all over the puppet labs site and can't find anything useful. Their docs for installing and configuring a new server are terrible, especially when it comes to adding a new client. Thanks very much for your help. Josh On Sep 15, 7:06 pm, Nicolai <nicolai.molle...@gmail.com> wrote: > There is no need to copy _anything_ from /var/lib/puppet from another > machine, actually i think it breaks stuff. > > As youre running 0.25.5 you need to run puppetd once so that it can create > its private key and cert, sign the cert on the master with puppetca --sign > machine-name. > > Then puppet should run and apply the manifests you have for the node. > > Regards > > Nicolai -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
