Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9008

SIGSEGV (JVM crash) in Jenkins native method hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • pam-auth-plugin
    • None
    • RHEL 6 Linux x86_64

      JVM crashed in

      j org.jvnet.libpam.PAM.authenticate(Ljava/lang/String;Ljava/lang/String;)Lorg/jvnet/libpam/UnixUser;+34
      j hudson.security.PAMSecurityRealm$PAMAuthenticationProvider.authenticate(Lorg/acegisecurity/Authentication;)Lorg/acegisecurity/Authe

      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

            Unassigned Unassigned
            davidbiesack David Biesack
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: