search for: puppet1

I''m trying to setup a puppetmaster, and I''ve got a couple of questions. The first, is a design question. Since I expect to eventually have multiple puppetmaster servers, I''d like to name this one to be named puppet1.example.com. But I''d like my clients to connect via a cname as puppet.example.com. Is this pretty standard? Is there some more common way? puppetmaster seems to want to create the CA certs as puppet1.example.com. I assume one of the configuration parameters would tell it otherwise. I'...

...#39;', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call ''puppetrun --debug --host puppet2.abc.net'' : Failed to load ruby LDAP library. LDAP functionality will not be available debug: puppet: Setting vardir to ''/var/opt/csw/puppet'' debug: puppet: Setting confdir to ''/etc/opt/csw/pupp...

...look around, my default kickstart installation includes puppet which shouldn''t be a problem however the puppet client fails with Certificates were not trusted: hostname was not match with the server certificate The cause is obvious, the hostname of my puppetmaster is ''puppet1.mydomain.com'' and clients access it via a DNS cname, ''puppet.mydomain.com''. So the certificate cannot be verified as the names do not match. The solution is not obvious, all other non-fedora 8 clients access the puppetmaster via the same cname and do not report this...

...etting an error midway with no information on what went wrong. How do I troubleshoot or look for more debugging information? This is what the screen output for installation is: thanks for your help in advance! Setting up pe-rubygem-fog (1.0.0e-1puppet2) ... Setting up pe-cloud-provisioner (1.0.1-puppet1) ... ## Setting up puppet master... "/opt/puppet/share/puppet/modules" does not exist, creating. Installed "puppetlabs-pe_accounts-1.0.2" into directory: pe_accounts Installed "puppetlabs-pe_mcollective-0.0.39" into directory: pe_mcollective Installed "puppetlabs-...

...cate). If I run the same command, but use port 8140 to connect to puppet, I get a return code of 19 (which is correct). I believe that, if I fix this SSL problem then it would fix my main problem which is : Report processor failed: Failed to submit ''store report'' command for puppet1.allantgroup.com to PuppetDB at fqdn:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=fqdn] I have puppetdb in the dns_alt_names line in puppet.conf Why does it work on 8140. but not 8081? How can I f...

...ver I run the puppet agent on them everything seems to go fine and I see the catalog getting submitted to PuppetDB in the logs. However, when I run puppet on the node that should collect these resources they aren''t applied. Querying PuppetDB via the API shows no resources exported for puppet1 or puppet2. Again, all other nodes are exporting their resources as expected. The only differences I can think between the masters and regular nodes are: - The puppetdb-terminus package is installed - They have /etc/puppet/routes.yaml and /etc/puppet/puppetdb.conf - storeconfigs = true...

I''m very interested in the way that puppet appears to be able to generate nagios configurations though I can''t seem to find any documenation on how it works: http://reductivelabs.com/trac/naginator is clearly a placeholder page... Meanwhile the various pieces of info at links such as: http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host are just teasing me.

...of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me. For instance I generate the ssl cert from the 1st master, and I copy it over to the 2nd puppetmaster: puppet1>scp private_keys/puppetmaster2.pem root@puppet2:/var/lib/puppet/ssl/private_keys/puppetmaster2.pem puppet1>scp ca/signed/puppetmaster2.pem root@puppet2:/var/lib/puppet/ssl/certs/puppetmaster2.pem puppet1>scp ca/ca_crt.pem root@puppet2:/var/lib/puppet/ssl/certs/ca.pem I get the following e...