Gemfire server nodes crash with SIGBUS fatal error

Products

• VMware Tanzu Gemfire

Issue/Introduction

Gemfire nodes crash throwing SIGBUS fatal errors in the logs as shown below.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0x00007f1b8a61236f, pid=327604, tid=175724
#
# JRE version: Java(TM) SE Runtime Environment (17.0.10+11) (build 17.0.10+11-LTS-240)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.10+11-LTS-240, mixed mode, sharing, tiered, compressed class ptrs, z gc, linux-amd64)

# Problematic frame:

# v  ~StubRoutines::aescrypt_encryptBlock
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h" (or dumping to /data/gemfire/XXX/core.327604)
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp

#

Environment

GemFire Supported Versions

JRE version: Java(TM) SE Runtime Environment (17.0.10+11) (build 17.0.10+11-LTS-240)

 

Cause

A SIGBUS error occurs at the hardware level when the CPU tries to access memory that doesn’t exist and is not an indication of an issue with Gemfire. There is also a possibility that this can occur when swap is enabled as mentioned in this related article. 

Resolution

Check for a faulty disk or hardware on all nodes that throw this error.

Ensure that the OS version is supported.