An excellent write-up, thank you.
In our case puppet-master is actually an LXC container instance. On
reflection the values reported by top are meaningless, and I'm not
convinced I know the solution for monitoring purposes. I might suggest
however that part of application support now needs to
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
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
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
