I also tested hiera recursive lookup and seems to work. Here is an example:
*rdeck_port_default: '4441'rdeck_configdir_default:
'/etc/rundeck'rundeck::rdeck_jvm:java.security.auth.login.config:
%{hiera('rdeck_configdir_default')}/jaas-loginmodule.conf
server.http.port:
Hi Puppet Team,
I am facing Dependencies issue for puppet client installation. I am running
puppet 3.7 on CentOS 7 and clients are RHEL7 and CentOS 7 (Without Internet
connectivity). I ran this command on client...
curl -k https://host1.xxx.com:8140/packages/current/install.bash | sudo
bash
I have a 270MB puppetdb-oom.hprof.prev file in /var/log/puppetdb
Google reports this as http://projects.puppetlabs.com/issues/23237 however
this page is a 500 Internal Server Error at present.
On 16 February 2015 at 12:13, Ken Barber k...@puppetlabs.com wrote:
It might be that PuppetDB is
I have a 270MB puppetdb-oom.hprof.prev file in /var/log/puppetdb
This isn't unexpected behaviour per se, although it appears as such if
you haven't dealt much with Java applications. Memory usage is a hard
to predict thing, and if its too low, yes the JVM will crash itself
drop that hprof file.
16850 puppetdb 20 0 12.697g 418684 14848 S 0.9 0.4 4:32.74 java
That's top now since it began running around 10.30 this morning (GMT). 12G
of ram? It's the only proc in the list having a 'g' against it. Seems
excessive..?
On 16 February 2015 at 12:43, James Green
16850 puppetdb 20 0 12.697g 418684 14848 S 0.9 0.4 4:32.74 java
That's top now since it began running around 10.30 this morning (GMT). 12G
of ram? It's the only proc in the list having a 'g' against it. Seems
excessive..?
So, there is a difference in the columns here ... the column
Hi Puppet Team,
I am facing Dependencies issue for puppet agent installation. Please help
me to resolved this issue. I am running PE 3.7 on CentOS 7 and clients are
CentOS 7 and RHEL 7. I ran this command on puppet agent...
curl -k https://host1.xxx.com:8140/packages/current/install.bash |
Hi Ken,
thanks for the answer.
We are already using the PGDG packages, but at the moment this is just
9.2 (which is still supported).
Regards,
Stefan
On Mo, 2015-02-16 at 12:10 +, Ken Barber wrote:
In short, yes - yes 2.2.2 does support 9.2, although in the next major
release (3.x) we
Hi,
we are currently evaluating to update our Puppet infrastructure, one
open item is the required PostgreSQL version for PuppetDB 2.2.x.
Does PuppetDB 2.2.x still support PostgreSQL 9.2?
The upgrade docs only mention that Postgres 9.3 is recommended and pre
9.1 versions have been deprecated.
For the record, I've decided to port the code to ruby_gpg when running
inside the Puppetserver.
The PR is at https://github.com/sihil/hiera-eyaml-gpg/pull/24
On Thursday, February 12, 2015 at 3:22:48 PM UTC+1, Raphink wrote:
We have a puppet-master box with the following installed:
root@puppet-master:/var/log/puppetdb# dpkg -l | grep puppet
ii facter 2.4.1-1puppetlabs1 all
Ruby module for collecting simple facts about a host operating system
ii hiera
In short, yes - yes 2.2.2 does support 9.2, although in the next major
release (3.x) we will be dropping that support. We are generally
telling people to utilise the PGDG set of packages to obtain the
latest PostgreSQL version:
http://yum.postgresql.org/repopackages.php
It might be that PuppetDB is running out of heap? Check
/var/log/puppetdb for a file 'puppetdb-oom.hprof' for an indiciation
this is happening.
You can find instructions for how to adjust your heap space here:
https://docs.puppetlabs.com/puppetdb/2.2/configure.html#configuring-the-java-heap-size
13 matches
Mail list logo
