search for: ca_pub

...ry, :backup=>false, :mode=>"770", :loglevel=>:debug, :path=>"/var/lib/puppet/.puppet/ssl/ca"}'' Aug 7 14:33:38 puppetmaster-02 puppet-master[27451]: Using settings: adding file resource ''capub'': ''File[/var/lib/puppet/.puppet/ssl/ca/ca_pub.pem]{:links=>:follow, :ensure=>:file, :backup=>false, :loglevel=>:debug, :path=>"/var/lib/puppet/.puppet/ssl/ca/ca_pub.pem"}'' Aug 7 14:33:38 puppetmaster-02 puppet-master[27451]: Using settings: adding file resource ''capub'': ''File[/var/l...

...boot all nodes could connect successfully *except* the puppet server itself: the old error message was back. After some digging, I found in $ssldir the following files that were created around the time that the old puppet server was created: certs/ca.pem ca/private/ca.pass ca/ca_crt.pem ca/ca_pub.pem ca/ca_key.pem certs/ca.pem and ca/ca_crt.pem (which are identical files) both contain: Issuer: CN=puppet.domain.com Validity Not Before: Mar 25 15:51:31 2008 GMT Not After : Mar 24 15:51:31 2013 GMT Subject: CN=puppet.domain.com I imagine I could solve this problem by comp...

...uppet] debug: /File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring File[/etc/puppet/ssl/ca/private] debug: /File[/etc/puppet/ssl/ca/serial]: Autorequiring File[/etc/puppet/ssl/ca] debug: /File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/etc/puppet/ssl/ca] debug: /File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/etc/puppet/ssl/ca] debug: Finishing transaction 2168470120 with 0 changes bouti.carbonplanet.com err: Could not call sign: Invalid argument Any ideas anyone? Thank you Jesse -- Jesse Reynolds Carbon Planet Limited - http://www.carbonplanet.com/ Virtual Artists...

.../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 = /etc//opt/csw/puppet/ssl/public_keys passfile = /etc//opt/csw/puppet/ss...

Getting this error: err: Could not call list: header too long when running puppetca commands on master. There is not a disk space issue. On the puppet master server, /var filled up to 100% during the night. Now it''s fine, down to 25% used. I rebooted server too Any fixes? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

...ppet 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/ca/inventory.txt certdir = /var/lib/puppet/ssl/certs certdnsnames = "" certificate_revocation = true certname = vusion-production classfile = /var/lib/puppet/state/classes.txt client_datadir...

...ation = /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/autosign.conf factdest = /var/puppet/facts/ hostprivk...

...a.pass]/owner: Cannot manage ownership unless running as root warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/ puppet/ssl/ca/ca_crt.pem]/owner: Cannot manage ownership unless running as root warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/ puppet/ssl/ca/ca_pub.pem]/owner: Cannot manage ownership unless running as root warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/ puppet/ssl/ca/ca_key.pem]/owner: Cannot manage ownership unless running as root warning: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/ File[/var/lib/puppe...

.../var/lib/puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/ var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/requests]: Autorequiring File[/var/ lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/ var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/ var/lib/puppet/ssl/ca] debug: Finishing transaction -607319668 debug: Using cached certificate for ca debug: Using cached certificate for ca debug: Using cached certificate for test.example.com notice: Starting Puppet master version 2.6.5 /usr/lib/ruby/site_ruby/1.8/puppe...

...ar/lib/puppet/ssl/ca/inventory.txt]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /File[/var/lib/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: Finishing transaction -607501368 debug: Using cached certificate for ca debug: Using cached certificate for ca debug: Using cached certificate for pupp...

...iring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/private]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/signed]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/main/File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /puppetconfig/main/File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /puppetconfig/ssl/File[/var/lib/puppet...

...#39;' debug: ca: Setting cacrl to ''$cadir/ca_crl.pem'' debug: ca: Setting ca to ''true'' debug: ca: Setting serial to ''$cadir/serial'' debug: ca: Setting cakey to ''$cadir/ca_key.pem'' debug: ca: Setting capub to ''$cadir/ca_pub.pem'' debug: ca: Setting ca_ttl to ''5y'' debug: ca: Setting cacert to ''$cadir/ca_crt.pem'' debug: fileserver: Setting fileserverconfig to ''$confdir/fileserver.conf'' debug: filebucket: Setting clientbucketdir to ''$vardir/clientbuck...

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

...ssl/ca/requests]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/main/File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet] debug: /puppetconfig/main/File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /puppetconfig/ca/File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/var/lib/puppet/ssl/ca] debug: /puppetconfig/ca/File[/etc/puppet/autosign.conf]: Autorequiring File[/etc/puppet] debug: /puppetconfig/main/File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/ cs...

...dir/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_pub.pem''. capub = /etc/puppet/ssl/ca/ca_pub.pem # Where the CA stores certificate requests # The default value is ''$cadir/requests''. csrdir = /etc/puppet/ssl/ca/requests # Where the serial number for certificates is stored. # The default value is ...

Hi, I am using a template to create an /etc/exports file. I have a template that looks like this (but results in the puppetmasterd dying on the server when the client updates): <% nfsHomeClients.split.each do |host| -%> /nfs <%= host %>(<%= mainshareoptions %>) <% nfspaths.each do |path| -%> <%= path %> <%= host %>(<%= nfsoptions %>) <% end

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

I''ve gone over the documentation several times now and I can''t figure out how to ''apply'' a manifest to a client. The client does have a signed certificate but the only thing in the /etc/puppet folder on the client is an ssl directory. I have a manifest that works fine on the puppet ''master'' I have added the client into

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd