similar to: Could not call puppetca.getcert HTTP-error: 500

Hi all puppet-Users, i try to get my first puppet installation up and running. (puppet-0.24.5, ruby-1.8.5) everything works as expected witch puppetmasterd + puppetd on the same machine. but i''ve problems connecting to the puppet-server from any client host. all i get is the error ------------ debug: Calling puppetca.getcert err: Could not call puppetca.getcert:

Hi, I''ve just been configuring my new Puppet 3.1.1 / Dashboard setup with Passenger to use PuppetDB for the inventory service. I configured it via the puppetdb forge module, and it all seems to be configured correctly as far as the docs describe. When I look at a node in the dashboard, under the inventory section, I just see: Could not retrieve facts from inventory service: 404

After upgrading my puppetmaster to 0.24.7 from 0.24.6 i am getting the following errors in the puppetmaster logs. Any help would be appreciated. Thu Dec 18 16:11:39 +1100 2008 Puppet (err): Could not store configs: undefined method `environment='' for #<Puppet::Rails::Host:0xb72c0c38> I do not use environment''s and they are not defined anywhere in the puppet.conf

Hi Guys, Im trying to turn on storeconfigs with a mysql db backend. On my testing server in our lab, i configured this successfully and can see if keeping information on all test hosts. When trying to implent the same idea onto our production puppet server, I get the following errors: Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/

Hi: I''m trying to configure Puppet on Ubuntu, and strangely I am never able to generate a certificate because my server never shows any pending certificate requests. Put differently, on the server I am running puppetmasterd and on the client I am able to connect to the server, but the client continues printing notice: Did not receive certificate warning: peer certificate

Hi all, I am new to Puppet and now I do some test with 2 Virtual Machines running Centos 6.4 and puppet 3.3.1 And I manage to sign the client cert, but still I can not get any file updated on the client VM. If I run the client in test mode puppet agent --server=p-master.localdomain --noop --test There is no errors in the output. Info: Retrieving plugin Info: Caching catalog for

Dear all, I see this error message in my *masterhttp.log* repeatedly: ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 > read client certificate A: tlsv1 alert unknown ca > I saw a similar mail in the list but there was no definitive answer to that post. Does anyone know what am I missing here? I do understand what *unknown ca* means but I can''t think

I''m suddenly getting the below errors from Rack during puppetd -t (excerpted from the pink HTML output and cleaned for readability): Could not prepare for execution: Got 10 failure(s) while initializing: change from absent to directory failed: Could not set ''directory on ensure: Permission denied - /var/lib/puppet/yaml; change from absent to directory failed: Could not set

Seeing ''SSL_read'' errors being logged by puppetmaster. Anyone know what causes these or how to correct? They''re sporadic, not happening all the time or on all puppet runs. /var/log/puppet/masterhttp.log [2011-07-25 10:00:10] ERROR OpenSSL::SSL::SSLError: SSL_read:: internal error /var/log/messages Jul 25 10:00:10 cmd-box puppet-master[22572]: SSL_read:: internal error

Currently the puppetca CA password is set to ''secret'' How would one go about changing it? I agree with puppetlabs documentation that you should be an SSL expert to implement your own CA. I am not. However I would like to use puppet''s CA PKI infrastructure with ActiveMQ over TLS and it is seems logical to use puppet''s KPI with this for mcollective and

I''m a noob puppeteer. I''m following the directions here: http://shapeshed.com/setting-up-puppet-on-ubuntu-10-04/ I''m running two identical Ubuntu VMs. I can apparently set up the master ok. But, when I try to connect with an agent I get the following error from the agent: Error: Failed to apply catalog: SSL_connect returned=1 errno=0 state=SSLv3 read server

I am using Puppet 0.23.2 I am trying to add a new client -- v26.domain.com This is what I am doing from client side - v26.doamin.com #puppetd --test info: Creating a new certificate request for v26.domain.com info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/v26.domain.com.pem warning: peer certificate won''t be verified in this SSL session. notice: No

I have a node that has some bad stored configs (namely the wrong ssh host keys) that I''m trying to clear out. Looking around it seems I''m supposed to do: puppet node clean foo.example.com However, that keeps bailing out because it''s trying to open a SQLite3 db where stored configs are normally kept, but my stored configs are kept in puppetdb (http://pastie.org/7814483

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

Hi @all, i have a foreman-proxy server, build from scratch, works fine and i can build unattended hosts. I don''t want to configure all my foreman-proxys manually, so i build them in puppet, and only setup the OS (SL) and basic puppet config manually. I can run the puppet configuration sucsessfully, my config is exactly what i want, but i am unable to build unattended hosts anymore,

Greetings! As you undoubtedly know, the fixes for CVE 2007-5162 in ruby break installations where puppetca has created certificates with a CommonName different from the server's real hostname. The Puppet clients quite correctly complains about hostname mismatch. A number of better and worse solutions have been suggested for this problem, especially in ticket #896. IMHO, there are two good

Has anyone attempted to get openvpn to work with puppets certificates? I am thinking that it should work without to much fuss. My current openvpn implementation uses the following certificates and beside these are what i think would be the appropriate puppet ones. openvpn server: ca /etc/openvpn/ca.crt -> /var/lib/puppet/ssl/certs/ca.pem cert /etc/openvpn/fqdn.crt ->

All, I have --confdir=/etc/puppet/common in my /etc/init.d/puppetmaster and /etc/init.d/puppet files, vardir set to /var/lib/puppet in /etc/puppet/common/puppet.conf, and yet, every time I run puppetca it creates /etc/puppet/ssl. Anyone know why? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the

Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM