search for: cadir

...t.pem'' debug: certificates: Setting passfile to ''$privatedir/password'' debug: certificates: Setting localcacert to ''$certdir/ca.pem'' debug: certificates: Setting certdir to ''$ssldir/certs'' debug: ca: Setting cert_inventory to ''$cadir/inventory.txt'' debug: ca: Setting caprivatedir to ''$cadir/private'' debug: ca: Setting ca_md to ''md5'' debug: ca: Setting signeddir to ''$cadir/signed'' debug: ca: Setting csrdir to ''$cadir/requests'' debug: ca: Setting req...

...certificate # request to overwrite an existing certificate. # allow_duplicate_certs = false # The type of hash used in certificates. # The default value is ''md5''. # ca_md = md5 # A Complete listing of all certificates # The default value is ''$cadir/inventory.txt''. cert_inventory = /etc/puppet/ssl/ca/inventory.txt # The root directory for the certificate authority. # The default value is ''$ssldir/ca''. cadir = /etc/puppet/ssl/ca # The CA public key. # The default value is ''$cadir/ca_...

...eturns within 10 seconds with: err: Could not retrieve catalog: Certificates were not trusted: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol warning: Not using cache on failed catalog Nevertheless, a certificate for myhost.mydomain appears in $cadir/signed - despite there being no $confdir/autosign.conf file nor an ''autosign'' entry in $confdir/puppet.conf. The Mandriva packages also include a couple of additional config files, /etc/sysconfig/puppetd and /etc/sysconfig/puppetmasterd; but every non-blank line in both those fil...

.../ca_crt.pem caprivatedir = /etc//opt/csw/puppet/ssl/ca/private capass = /etc//opt/csw/puppet/ssl/ca/private/ca.pass cakey = /etc//opt/csw/puppet/ssl/ca/ca_key.pem csrdir = /etc//opt/csw/puppet/ssl/ca/requests serial = /etc//opt/csw/puppet/ssl/ca/serial cacrl = /etc//opt/csw/puppet/ssl/ca/ca_crl.pem cadir = /etc//opt/csw/puppet/ssl/ca capub = /etc//opt/csw/puppet/ssl/ca/ca_pub.pem certdir = /etc//opt/csw/puppet/ssl/certs privatedir = /etc//opt/csw/puppet/ssl/private hostcert = /etc//opt/csw/puppet/ssl/certs/puppet-test.example.net.pem localcacert = /etc//opt/csw/puppet/ssl/certs/ca.pem publickeydir...

...c/puppet/autosign.conf bindaddress = "" bucketdir = /var/lib/puppet/bucket ca = true ca_days = "" ca_md = md5 ca_name = Puppet CA: vusion-production ca_port = 8140 ca_server = puppet ca_ttl = 5y cacert = /var/lib/puppet/ssl/ca/ca_crt.pem cacrl = /var/lib/puppet/ssl/ca/ca_crl.pem cadir = /var/lib/puppet/ssl/ca cakey = /var/lib/puppet/ssl/ca/ca_key.pem capass = /var/lib/puppet/ssl/ca/private/ca.pass caprivatedir = /var/lib/puppet/ssl/ca/private capub = /var/lib/puppet/ssl/ca/ca_pub.pem catalog_format = "" catalog_terminus = compiler cert_inventory = /var/lib/puppet/ssl/c...

> I guess we have to look at the conf files then, first these two: Thank you for the config file snippets. I can confirm mine were almost identical, so I've tweaked them so that they are now exactly the same as yours except for the "--require-membership-of=example\authorization_groupname" line in ntlm_auth. Unfortunately it's still erroring out: (7) mschap: Creating

...= false railslog = /var/puppet/log/rails.log dblocation = /var/puppet/state/clientconfigs.sqlite3 cert_inventory = /etc/puppet/ssl/ca/inventory.txt cakey = /etc/puppet/ssl/ca/ca_key.pem caprivatedir = /etc/puppet/ssl/ca/private capass = /etc/puppet/ssl/ca/private/ca.pass cadir = /etc/puppet/ssl/ca capub = /etc/puppet/ssl/ca/ca_pub.pem csrdir = /etc/puppet/ssl/ca/requests serial = /etc/puppet/ssl/ca/serial cacert = /etc/puppet/ssl/ca/ca_crt.pem cacrl = /etc/puppet/ssl/ca/ca_crl.pem signeddir = /etc/puppet/ssl/ca/signed autosign = /etc/puppet/au...

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

...nventory.txt]{:links=>:follow, :ensure=>:file, :backup=>false, :mode=>"644", :loglevel=>:debug, :path=>"/var/lib/puppet/.puppet/ssl/ca/inventory.txt"}'' Aug 7 14:33:38 puppetmaster-02 puppet-master[27451]: Using settings: adding file resource ''cadir'': ''File[/var/lib/puppet/.puppet/ssl/ca]{:links=>:follow, :ensure=>:directory, :backup=>false, :mode=>"770", :loglevel=>:debug, :path=>"/var/lib/puppet/.puppet/ssl/ca"}'' Aug 7 14:33:38 puppetmaster-02 puppet-master[27451]: Using setti...

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

I''m running a previously working set of modules with the Puppet master version 3.1.0-rc2. I''m getting the Error: stack level too deep Here is a chunk of the debug Debug: Scope(Class[Zabbix]): Retrieving template zabbix/zabbix.conf.php.erb Debug: template[/etc/puppet/environments/production/modules/zabbix/templates/zabbix.conf.php.erb]: Bound template variables for