Start aerospike.service fail with aerospike-server-community_6.4.0.19

aerospike.service - Aerospike Server
     Loaded: loaded (/usr/lib/systemd/system/aerospike.service; disabled; preset: disabled)
    Drop-In: /etc/systemd/system/aerospike.service.d
             └─aerospike.conf
     Active: failed (Result: core-dump) since Mon 2024-07-29 11:30:22 CST; 9min ago
   Duration: 184ms
    Process: 18217 ExecStartPre=/usr/bin/asd-systemd-helper (code=exited, status=0/SUCCESS)
    Process: 18223 ExecStartPre=/bin/systemctl start aerospike_telemetry (code=exited, status=0/SUCCESS)
    Process: 18225 ExecStart=/usr/bin/asd $ASD_OPTIONS --config-file $ASD_CONFIG_FILE --fgdaemon (code=dumped, signal=SEGV)
    Process: 19044 ExecStopPost=/bin/systemctl stop aerospike_telemetry (code=exited, status=0/SUCCESS)
   Main PID: 18225 (code=dumped, signal=SEGV)
        CPU: 283ms

Can you share additional details like: 1) Is this a single node deployment? 2) Where is it being deployed in terms of the underlying server? Does the server have adequate memory etc.? 3) Can you share the configuration file? /etc/aerospike/aerospike.conf … ? This will help the right folks to further help you.

It’s a single node deployment . It’s deployed on the Dell PowerEdge R7625 . How can i make sure whether it have enough memory . This is the unique part for my config file.

namespace test {
        replication-factor 2
        memory-size 64G

#       storage-engine memory
        storage-engine device {
                device /dev/nvme0n1
                write-block-size 128K
                data-in-memory true
        }
}

Did you have anything in the log file itself that would shed some light? You can check through journald or in the file itself (typically /var/log/aerospike/aerospike.log) depending on how you have configured the logging.