PuppetDB crashes upon startup

145 views
Skip to first unread message

Ger Apeldoorn

unread,
Oct 9, 2012, 9:05:10 AM10/9/12
to puppet...@googlegroups.com
Hi,

I've got a Puppet Enterprise 2.6 installation on RHEL6 and have followed this installer doc: http://docs.puppetlabs.com/puppetdb/1/install.html

When I try to start the daemon, I get the following in the errorlogs:

JVMDUMP010I System dump written to /tmp/core.20121009.144917.3691.0001.dmp
JVMDUMP030W Cannot write dump to file /root/javacore.20121009.144917.3691.0002.txt: Permission denied
JVMDUMP032I JVM requested Java dump using '/tmp/javacore.20121009.144917.3691.0002.txt' in response to an event
JVMDUMP012E Error in Java dump: /tmp/javacore.20121009.144917.3691.0002.txt
JVMDUMP032I JVM requested Snap dump using '/root/Snap.20121009.144917.3691.0003.trc' in response to an event
JVMDUMP030W Cannot write dump to file /root/Snap.20121009.144917.3691.0003.trc: Permission denied
JVMDUMP010I Snap dump written to /tmp/Snap.20121009.144917.3691.0003.trc
JVMDUMP013I Processed dump event "abort", detail "".

Appareantly, Java is crashing. Snippet from the dumpfile:

3CLTEXTCLASS                    (0x00007F49B83D2C00)
3CLTEXTCLASS                    1INTERNAL      An exception occurred attempting to access in-flight data. Internal diagnostics:
NULL
2INTERNAL                J9Generic_Signal_Number: 00000004
2INTERNAL                Signal_Number: 0000000B
2INTERNAL                Error_Value: 00000000
2INTERNAL                Signal_Code: 00000001
2INTERNAL                Handler1: 00007F49BC18EE10
2INTERNAL                Handler2: 00007F49BC6A0EF0
2INTERNAL                InaccessibleAddress: 00007F4A27AFF44B
NULL
2INTERNAL                Module: /usr/lib/jvm/java-1.7.0-ibm-1.7.0.1.0.x86_64/jre/lib/amd64/default/libj9dmp26.so
2INTERNAL                Module_base_address: 00007F49BC17B000
NULL

Any help would be much appreciated!

Thanks,
Ger.

Ger Apeldoorn

unread,
Oct 9, 2012, 10:01:46 AM10/9/12
to puppet...@googlegroups.com
The issue was that there was java 1.7 installed, forcing it to a java 1.6 JVM seems to fix this.

Thanks
Ger

Op dinsdag 9 oktober 2012 13:05:10 UTC schreef Ger Apeldoorn het volgende:
Reply all
Reply to author
Forward
0 new messages