Hi Jan,
This is the problem of postgresql database server. Check postgreSQL
server on your machine working or not.
First start the postgresql server and then try to run puppet enterprise
installation.
Thanks and Regards,
Rahul Khengare
NTT DATA OSS Center Pune, India.**
On Tuesday, August
Hi Ed,
Puppet execute their file resource only if contents of target file get
changed at the before execution of puppet run.
I checked your problem on RHEL-6.2 using puppet version 2.7.12, httpd.conf
file not transferred each time if there is not change in the contents.
You may have to chec
On Tue, Aug 20, 2013 at 2:15 PM, joel johnston wrote:
> The url is bad/wrong. For some reason it is injecting this %2F in
> front of pub where it SHOULD just be /pub/
%2F is a '/' in url encoding, maybe there is a trailing slash
somewhere you can remove which will allow a proper URL to be
con
Hello,
I have an event tagged err, which is not being forwarded by tagmail
correctly. The entry in JSON:
{
"level": "err",
"message": "Could not retrieve catalog from remote server:
Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error
ArgumentError: Inval
Well I've been using an initial solution for the past month or two which
seems to be working ok.
I have a custom puppet function that reads the version of the artifact
being deployed and I add that to the mcollective facts.yaml file at the
same time that the artifact is deployed. I've also got
I need to define data for roles so I add the 'role' dynamic data source.
- "%{::environment}/%{::clientcert}"
- "%{::clientcert}"
- "%{::environment}
- "%{::role}"
- common
Our site.pp uses a hostname regex to classify nodes into roles e.g.
node /^ns\d+$/ {
include role::nameserver
}
Can we
Here's a friendly reminder for those of you attending PuppetConf to join
Henrik, Eric0 and myself tomorrow afternoon for the Armatures workshop:
http://sched.co/14zaQjw
Armatures are a great way to influence the future direction of Puppet, and
provide a unique opportunity to collaborate directl
Hi all,
I have similar problem. When I start puppet interactive console and run
'puppet agent -t' it complete successfully. But when I start puppet service
under same (or any other use) it fail with powershell crash
*Fault bucket , type 0*
*Event Name: PowerShell*
*Response: Not available*
*Cab
Hi,
We're looking for a skilled Puppet developer for a 6 month contract. We
use a mixture of
custom modules/facts and modules from forge/github, mainly LAMP stack stuff
and a few things
specific to our infrastructure. Most of our focus is on RHEL/CentOS, with
a bit of
Ubuntu, CloudStack, ES
I have several NFS mounts to manage, on many systems. On each system, I
must ensure that the root directory and path exist and have the correct
permissions beforehand, then ensure they are mounted in Puppet.
For each, I would normally do:
file { "/home/directory1":
>
>e
You can fake interation. "$name" is a free variable for whatever you're
passing in. I have NOT tested this, but it might look something like this:
define my_mounts {
mount { "/home/$name":
>
>device => "our-thumper.domain.com:/export/$name",
atboot => yes,
Yes, that will work. We actually do something slightly ickier, so the
data all stays in hiera:
hiera hierarchy:
- nodes/%{hostname}
- ...
- roles/%{role}
nodes/foo.yaml:
...
role: desktop
classes:
- "roles::%{role}"
node default {
$role = hiera('role')
include hiera('classes')
Hello,
I have configured puppet and puppetdb (storeconfig) with postgresql and the
service run and the collecting are good for example:
I can make query with the next command and responds ok .
[.]
[root@master]# curl -X GET -H 'Accept: application/json'
http://127.0.0.1:
So I would need to define $mounts, presumably as:
$mounts = "directory1 directory2 directory3"
?
Where is $name being defined here.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
Will Farrington, Andrew Parker, Mike Stahnke, and I just had a conversation at
PuppetConf about the future of 2.7 and decided that Will and I will be
maintaining and managing releases for the 2.7 branch. This means that Puppet
Labs will be hosting 2.7 packages on the releases page and in packa
you might want to explicitly top-scope role, ie.
$::role = 'nameserver'
Not sure if that will matter in this case, but I don't think it can hurt.
As an aside, we set our role variable with facter.d on the nodes
themselves, as we don't have hostnames that easily work out to roles.
On Wednesday,
Like, the postgresql database? First, I have to ask: why you want to go
poking around in there?
Anyway, assuming you set it up with user: puppetdb, databasename: puppetdb
and the recommended potgresql settings, you can use the psql client, like
so:
psql -h 127.0.0.1 puppetdb puppetdb
On Wedne
I'm having some trouble with getting an ENC to work alongside site.pp:
Even with a 'default' node definition, and an ENC that only returns 0,
regardless of input, consistently results in a 'cannot find node' error.
I'm wondering what I've missed here.
I've tried to reduce everything to a 'base
You define an array-containing variable like this:
$mounts = [ 'directory1', 'directory2', 'directory3' ]
You can also put newlines after the commas for easier reading. The following
code should be functional:
class test_case {
$mounts = [
'directory1',
'directory2',
I am at Puppetconf today. I just set up a new VM running a brand new
version of FreeBSD 9.2 . I created my Puppetmaster during a Puppet course
today, using a VM from puppetlabs.com .
When I attempt to acquire a certificate from the Puppetmaster, I get a
strange error. The agent & master can bot
Stefan,
If you do not have cert auto-signing enabled, the first time an agent connects
to the master, you should use the -w option, e.g.:
puppet agent -t -w 30
This will tell the agent to wait for the master (you) to sign the cert request.
Once that's done, the rest of the puppet run should ki
Hi,
I'm trying to do ssl offload on amazon ELB for my puppetmaster servers, it
seems amazon ELB is not sending ssl_client_header & client_verify_header
puppetmaster
Listen 8141
SSLEngine off
DocumentRoot /etc/puppet/rack/puppetmaster_8141/public/
RackBaseURI /
PassengerE
Great! I remember glancing at your nametag (A fellow -ski!)
Thanks for the pointer. However, it still isn't working.
root@agent2:~ # puppet agent --test --waitforcert 30
Error: Could not request certificate: SSL_connect returned=1 errno=0
state=SSLv2/v3 read server hello A: (null)
Error: Could no
23 matches
Mail list logo