Displaying 20 results from an estimated 2000 matches similar to: "Man pages"
2007 Oct 09
9
puppetca is unable to sign certificate
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
2012 Oct 01
10
Puppet 3.0 fails install on Solaris 10 w/ ruby 1.8.7
There''s a problem installing puppet on Solaris 10 -- in this situation, we
aren''t really doing anything with puppet there.
The version we''re using is:
ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9]
Here''s the first error:
# gem update puppet
>
> Updating installed gems
>
> Updating puppet
>
> Building native extensions. This
2007 Nov 28
7
puppetrun failing: "connect'': tlsv1 alert unknown ca"
I''m trying to get puppetrun to work, without luck so far.
I have my puppetmaster and clients working fine with the clients polling
the master. Now I want to be able to force an update. Using version
0.23.2
On the client I set listen=true and created the namespaceauth.conf file.
Restarted puppetd and it appears fine.
On the master I run puppetrun as root and get
root@plane:/etc/puppet#
2011 Feb 15
11
Puppetmasterd not receiving certificate request
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
2010 May 31
9
Problem with dashboard using live report aggregation
Hey,
I''m exploring puppet-dashboard right now and I want to get the live
aggregation running.
But somehow I''m already failing at the puppet.conf entries ;)
The Dashboard readme says:
### Live report aggregation
To enable report aggregation in Puppet Dashboard, the file `lib/puppet/
puppet_dashboard.rb` must be available in Puppet''s lib path. The
easiest way to do this
2008 Jun 27
2
puppetrun?
Hi,
I''m having trouble getting puppetrun to work, it returns:
# puppetrun --debug --host serverb
debug: Puppet::Network::Client::Runner: defining puppetrunner.run
Triggering serverb
debug: Calling puppetrunner.run
warning: peer certificate won''t be verified in this SSL session
err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 Internal Server Error >
2008 Jan 02
4
Puppetmaster doesn''t know itself
I restarted puppetmasterd and it announced that the Cert does not match
existing key !
[root@puppet ~]# puppetmasterd --verbose --no-daemonize
info: Starting server for Puppet version 0.24.1
info: mount[files]: allowing 10.100.0.0/16 access
info: mount[files]: allowing *.gridapp.com access
info: mount[files]: allowing *.dev.gridapp.com access
info: Retrieving existing certificate for
2012 Dec 05
8
Error: Could not request certificate: Connection refused - connect(2)
Hi all,
I am new at puppet and Im using the puppet learning tutorial. I execute
until Basic agent/master puppet. Everything worked ok but after 2 or 3
days, running the command "puppet agent --test", start throw the error in
subject. That left me with the following questions:
how to puppet agent connect to master without service started on master?
If this connection is possible (
2011 Oct 25
6
Regenerating puppet master certificate
Hi all,
Is there a more elegant way to regenerate the Puppet master certificate than what''s described in the CVE-2011-3872 toolkit?
> If you can maintain a secondary shell session to the puppet master server, you can start a WEBrick master with puppet master --no-daemonize --verbose and stop it with ctrl-C.
> If you prefer to only maintain one shell session, you can start a
2007 Mar 19
3
certificate trouble
Hi Puppet-Team,
first thanks for this great configuration management tool !
My name is Matt and i am on creating a puppet plugin for openQRM.
The basic framework is already existing and working well so far.
Now, after having it working ok once i now ran into a problem that
my puppet-clients do not get their configuration any more from the
puppetmasterd. What i saw on the puppetmasterd logs is :
2008 Jun 06
8
useradd provider not working?
I have this config:
# BL00070 - Disable NFS
service {["nfs","nfslock","netfs","portmap"]:
ensure => stopped,
enable => false,
}
user {"rpc": ensure => absent, provider => "useradd" }
user {"rpcuser": ensure => absent, provider => "useradd" }
file
2007 Dec 24
5
could not find user puppet ?
err:
/Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]:
Failed to retrieve current state of resource: Could not find user puppet
debug: Finishing transaction 75413780 with 2 changes
since i put the last version on this test server i cannot launch puppet
manualy:
mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \
mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \
2006 Oct 18
19
Creating client certificates
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
2012 Nov 29
7
Puppet CA corruption
Hello everyone,
Just getting my first puppet master set up and I am having a problem that I
just do not know how to get past. For some reason, my certificate store
keeps getting corrupted. Basically what happens is that the server will
issue itself a valid certificate (after removing the ''bad'' cert) and will
run just fine. When I start puppetDB (I am pretty sure it happens
2008 Aug 29
3
Could not call puppetca.getcert: #<Errno::EHOSTUNREACH: No route to host
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:
2006 Dec 12
3
Variables available in configs...
Is there a list somewhere?
How do I know what $operatingsystem, for example, is going to be set
to? Using ''solaris'' seems to work, but I haven''t tested ''ubuntu'' and
''redhat'' yet (haven''t gotten that far).
It''d be nice to have a list of available vars, along with "how they are set."
-Charlie
2010 May 23
12
Puppet Dashboard error.
Hi i have the running i both sides, client and server sides the puppet
0.25.4
Get this error on server side:
puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length
format
And receive this error on my client side:
warning: Value of ''preferred_serialization_format'' (pson) is invalid for
report, user default (b64_zlib_yaml)
I am getting any reports on my
2008 May 27
12
Puppetting the puppetmaster problems
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
2008 Dec 04
4
puppetmaster built via puppetd
hi,
i''m trying to set up my puppetmaster infrastructure with multiple
puppetservers behind load balancers in each of our datacenters. i''m
using 0.24.6. i''ve read the howto on puppet scalability, and i think
i''ve got the ssl config working correct, but i''m noticing that when
puppetd is used to build a puppetmaster, some of the files in $vardir/
ssl
2009 Nov 13
2
Multihomed puppet-server Multidomain SSL Problem
Hello List,
I have a problem with the CA on my Puppetmaster. This Puppetmaster is
connected to different Networks with different sub domainnames. The Puppet
clients connecting via different Interfaces. There is no routing between
subnets. Only one subnet can connect successfully. This is because the
subject in the Certificate is the name of this subnet. All other clients get:
Could not