[Puppet Users] puppetdb 4.3 on PG 9.4 fresh install fails to start with DB UTF8 encoding error

Hi everyone, I'm trying to do my first ever install of PuppetDB. I'm installing PuppetDB 4.3 from RPM with Postgres 9.4. When I try to start PuppetDB I get the following errors (removed some of the non-important java debugging lines): 2017-02-16 14:19:54,539 INFO [p.p.s.migrate] Applying

[Puppet Users] noob problem: Could not find a directory environment named 'development'

Hi all, I'm hoping you can point out some detail I'm missing. Puppet agent seems to run fine until I introduce hiera. I believe the issue is configuration path related: I'm using opensource pupperserver version 2.7.2 on an ubuntu 16.04 machine and puppet agent version 4.9.2 on a centos 7

[Puppet Users] Error 500 on SERVER: Server Error: Not authorized to call find on /file_metadata/files/

Hi, Puppet server is launching this error message in test environment: Error: /Stage[main]/Ejecuta/File[nombre.sh]: Could not evaluate: Could not > retrieve file metadata for puppet:///files/nombre.sh: Error 500 on SERVER: > Server Error: Not authorized to call find on

[Puppet Users] puppet print config yields 'Could not find a directory environment named 'development'

Hi. I'm a new user with an environment problem. My puppet.conf on my client host (puppet agent 4.9.2) looks like this: [main] certname = centosCLIENT.pretend.com server = puppet environment = development runinterval = 1h environment_timeout = 0 and when I run*

Re: [Puppet Users] Re: hiera deep hash merges broken

Hi, On 02/16/2017 09:03 PM, Henrik Lindberg wrote: > We are adding support for eyaml in hiera 5 which means you will get explain > support and that you can use eyaml when also using the new format. We now > also test with eyaml. By the way, and just for information ;), here an issue I have

[Puppet Users] Puppet is using high CPU usage!!!

Hi, We are using high end setup for our Puppet and foreman in CentOS server: RAID5, 198GB RAM, 64 cores Processor. But, after installation of Foreman-installer puppet is eating the CPU like anything. We can observe CPU usage% is spiking > 4000! Is it because of RAID5 processor? Can anyone

[Puppet Users] Re: puppet open source reports and inventory to Satellite 6?

I did not, my Satellite 6 was on a single server. Give it a try and report your results! -- 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 it, send an email to

Re: [Puppet Users] Re: puppet open source reports and inventory to Satellite 6?

Result was unsuccessful :( PPM to SAT direct was fine, this is because PPM was using the foreman-*.* ca/cert/key SSL assets to connect to SAT. However using these certs for PPM to CAP did allow the reports to be sent successfully to the CAP foreman https api, but there is no mechanism for these

[Puppet Users] Re: inline classes

On Wednesday, February 15, 2017 at 2:41:29 PM UTC-6, Ligne Six wrote: > > Hello folks, > > I'm wondering if it is possible to define-declare a class. Something like > inlining: > > instead of: > > ``` > include hello_distro >

Re: [Puppet Users] Re: hiera deep hash merges broken

It turns out my issue was caused by eyaml no longer supporting deep hash merges. I've worked around my issue by separating out plain yaml and eyaml. Fortunately none of my existing code does a deep hash merge on the eyaml keys. It would be great to get some reassurance that eyaml will continue to

[Puppet Users] Re: ensure_resource should be the default behaviour

On Wednesday, February 15, 2017 at 11:08:09 AM UTC-6, Poil wrote: > > Hi, > > After some years of writing puppet modules, I think the ensure_resource > behaviour (from stdlib) should be the default behaviour for all resources. > > This will simplify the code, and made Puppet more accessible

Re: [Puppet Users] Re: ensure_resource should be the default behaviour

To elaborate on the problem set it would solve: If you were managing the same user in two locations and all you did was set ensure to present, by matching the create_resources behavior in default resource declaration, you'd resolve the duplicate declaration issue. Fine and dandy. If you were

[Puppet Users] Newbie Question About Puppet

Hi there guys I'm new to puppet and I'm gonna make my first install of if, I'll go with the free version and then in the near feature maybe we switch to Enterprise for support. I'm reading some docs and it seems the lates version is 4.8, the reading about the installation it talks about

Re: [Puppet Users] Augeas and custom lenses?

Dom, Sorry about resurrecting the old thread. About facts: `facter -p` (2.4.6) shows puppet facts, but not the ones loaded via puppet modules in /var/lib/puppet/facts.d (unless --external-dir is specified). For that reason, perhaps, we started putting ours in /etc/facter. -- You received this

Re: [Puppet Users] Augeas and custom lenses?

Ah, documented bug: https://tickets.puppetlabs.com/browse/FACT-696 On Thu, Feb 16, 2017 at 8:48 PM, otheus uibk wrote: > Dom, Sorry about resurrecting the old thread. About facts: `facter -p` > (2.4.6) shows puppet facts, but not the ones loaded via puppet modules in >

Re: [Puppet Users] Re: hiera deep hash merges broken

On 16/02/17 08:16, Daniel Urist wrote: It turns out my issue was caused by eyaml no longer supporting deep hash merges. I've worked around my issue by separating out plain yaml and eyaml. Fortunately none of my existing code does a deep hash merge on the eyaml keys. It would be great to get

Re: [Puppet Users] Puppet erb template create loop

On 13/02/17 18:05, Rafael Tomelin wrote: Hi dear, I is create a module and need loop in puppet class and template The my class step is: 1) My class have array declared; $pools = [ { name => 'PoolDiario', poolType => 'Backup', recycle=>

[Puppet Users] Puppet DB prune / vacuum

For cleaning up report data is the parameter prune_upto still valid? - related to version 2016.2 Or has the vacuum parameter replaced it? Do they both essentially do the same thing? https://docs.puppet.com/pe/2016.2/maintain_console-db.html Thanks -- You received this message because you

[Puppet Users] Re: Error 500 on SERVER: Server Error: Not authorized to call find on /file_metadata/files/

Where does the file 'nombre.sh' live on your Puppet master? Is it in the 'files/' directory in your module? In that case you should use 'puppet:///modules//nombre.sh' On Friday, 17 February 2017 02:31:57 UTC+2, Gustavo Moreno Fernández wrote: > > Hi, > > -- You received this message because