Thanks JM. Your config files look good and the existence of all of those
tables in your puppetdb database certainly makes it look as though puppetdb
is communicating with postgres properly. Since increasing the heap size
seems to have gotten you past the issues for now, my next guess is that i
Hi,
The configuration files are attached.
Here is the postgres login:
[root@puppetmaster]:/data/local/postgresql/dumps # psql -h localhost
puppetdb puppetdb
psql (8.4.12)
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.
puppetdb=> \l
Lis
JM,
Hmm... so, those versions of Java seem fine--those are probably the ones
we've done the most testing with.
So, the error message that you sent indicates that the JVM is running out
of RAM. This could possibly indicate that you are still using the embedded
database instead of postgres--the
In fact I am starting to have more and more errors regarding java exception:
2012-08-07 16:39:23,864 ERROR [command-proc-77] [puppetdb.command] Fatal
error parsing command java.lang.OutOfMemoryError: Java heap space
2012-08-07 16:39:26,628 WARN [command-proc-77]
[listener.DefaultMessageListenerCon
Here is the puppetdb.log:
2012-08-05 10:39:12,431 WARN [qtp2101818118-104743]
[server.AbstractHttpConnection] /commands
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2894)
at
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.j
Hello A_SAAS,
- Do you see any messages in the file "/var/log/puppetdb/puppetdb.log"?
- If not, can you try editing the file "/etc/puppetdb/log4j.properties"
and replace "INFO" with "DEBUG", and then see if you get any messages in
the aforementioned log file?
- What version of jav
