Status: Open (View Workflow)
RHEL 6 Linux x86_64
JVM crashed in
jenkins.log shows the following:
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@6f77e5d4: defining beans [filter,legacy]; root of factory hierarchy Mar 10, 2011 3:01:36 PM hudson.TcpSlaveAgentListener <init> INFO: JNLP slave agent listener started on TCP port 37072 Mar 10, 2011 3:01:51 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started ThinBackup Worker Thread Mar 10, 2011 3:01:51 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished ThinBackup Worker Thread. 5 ms # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000003f9ac0e511, pid=27459, tid=140470306912000 # # JRE version: 6.0_23-b05 # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.0-b09 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libdbus-1.so.3+0xe511] # # An error report file with more information is saved as: # /acl/usr/local/jenkins/.hudson/jobs/rtolap.procolap/hs_err_pid27459.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
but I don't know what Jenkins was doing at the time.
I'm using 1.399 ; I've not had a chance to update to 1.400 (or even check how stable it is)
I've only seen this once, however. It does not happen repeatedly. I've been using 1.399 since it was released
- is related to
JENKINS-9097 Jenkins crashes with error in D-Bus : arguments to dbus_message_unref were incorrect in file dbus-message.c line 1397
Long shot but David, did you ever figure out the cause of this "pam" issue? I'm seeing the same org.jvnet.libpam.PAM.authenticate jvm crash, though unrelated to jenkins. Java 7 on CentOS 6.4.
Sorry, no, I never tracked it down and simply went with the workaround I noted above.
I think the root bug is in a standard RedHat/CentOS 6 PAM module related to finger print scanners. Fix with "yum remove fprintd-pam". For repro see: https://github.com/kohsuke/libpam4j/issues/8.
I've had this exception occur several more times, including when we upgraded to Jenkins 1.401.
It was impacting us seriously, so I disabled PAM authentication and switched Jenkins to use its own user database.
However, I'd prefer to go back to Linux /etc/passwd authentication if this can be fixed.