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

Jenkins crashed with SIGSGEV on OpenJDK 11 with 48 core server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • pipeline
    • PROD

      Jenkins crashed with below error

       

      1. JRE version: OpenJDK Runtime Environment (Red_Hat-11.0.18.0.10-1.el7_9) (11.0.18+10) (build 11.0.18+10-LTS)
      2. Java VM: OpenJDK 64-Bit Server VM (Red_Hat-11.0.18.0.10-1.el7_9) (11.0.18+10-LTS, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
      3. Problematic frame:
      4. J 24765 c2 com.sun.crypto.provider.CipherCore.init(ILjava/security/Key;Ljava/security/spec/AlgorithmParameterSpec;Ljava/security/SecureRandom;)V java.base@11.0.18 (552 bytes) @ 0x00007fce584d32e7 [0x00007fce584d01c0+0x0000000000003127]
        #
      5. No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
        #

        1. hs_err_pid3753.log
          579 kB

          [JENKINS-70789] Jenkins crashed with SIGSGEV on OpenJDK 11 with 48 core server

          Mark Waite added a comment - - edited

          Very interesting that the failure is a segmentation violation in the Java code. Typically that is not something that Jenkins can avoid, since segmentation violation usually means that the Java virtual machine attempted to do something that the operating system will not allow.

          Even more interesting that the failure is happening on a machine with 48 cores. Does it fail in a similar manner if you add -XX:ActiveProcessorCount=8 to the command line as described in a stackoverflow article?

          Mark Waite added a comment - - edited Very interesting that the failure is a segmentation violation in the Java code. Typically that is not something that Jenkins can avoid, since segmentation violation usually means that the Java virtual machine attempted to do something that the operating system will not allow. Even more interesting that the failure is happening on a machine with 48 cores. Does it fail in a similar manner if you add -XX:ActiveProcessorCount=8 to the command line as described in a stackoverflow article ?

            Unassigned Unassigned
            rajin43 Rajini
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: