Issues to create nemespace

I am very new in aerospike, trying to create one name space in device storage engine.

namespace impressions_data {
    stop-writes-sys-memory-pct 90
    replication-factor 2
    evict-sys-memory-pct 95
    storage-engine device {
        device /dev/nvme1n1
        write-block-size 128K
    }
}

after add this name space in aerospike.conf file my aerospike engine is not starting

This are the disk I do have…

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0          7:0    0  21.6M  1 loop /snap/amazon-ssm-agent/7629
loop1          7:1    0  49.1M  1 loop /snap/core18/2810
loop2          7:2    0  59.3M  1 loop /snap/core20/2019
loop3          7:3    0 109.6M  1 loop /snap/lxd/24326
loop4          7:4    0  35.5M  1 loop /snap/snapd/20298
nvme1n1      259:0    0    50G  0 disk
nvme0n1      259:1    0     8G  0 disk
├─nvme0n1p1  259:3    0   7.9G  0 part /
└─nvme0n1p15 259:4    0    99M  0 part /boot/efi
nvme2n1      259:2    0 435.9G  0 disk

The error I am getting :

 aerospike.service - Aerospike Server
     Loaded: loaded (/lib/systemd/system/aerospike.service; disabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/aerospike.service.d
             └─aerospike.conf
     Active: failed (Result: core-dump) since Thu 2024-02-15 22:54:58 UTC; 7s ago
    Process: 2380 ExecStartPre=/usr/bin/asd-systemd-helper (code=exited, status=0/SUCCESS)
    Process: 2386 ExecStart=/usr/bin/asd $ASD_OPTIONS --config-file $ASD_CONFIG_FILE --fgdaemon (code=dumped, signal=ABRT)
   Main PID: 2386 (code=dumped, signal=ABRT)
        CPU: 118ms

Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:405) stacktrace: frame 10: /lib/aarch64-linux-gnu/libc.so.6() [0xffffa0a373fc]
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:405) stacktrace: frame 11: /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main) [0xffffa0a374cc]
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:405) stacktrace: frame 12: /usr/bin/asd(_start) [0xa60b0]
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:473) stacktrace: memory x21 0xffff9b1fffc0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:473) stacktrace: memory x23 0xaaaab37a2e30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:473) stacktrace: memory x29 0xffffe854cd40 00 00 f0 ff 00 00 00 ff 00 00 f0 ff 00 00 00 ff 02 00 00 00 00 00 00>
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:473) stacktrace: memory x30 0xaaaab34c75c0 e1 03 00 2a 00 7d 80 52 81 6a 06 b9 05 b1 f6 97 e0 03 16 2a 43 ae f6>
Feb 15 22:54:58 ip-172-31-71-216 asd[2386]: Feb 15 2024 22:54:58 GMT: WARNING (as): (signal.c:473) stacktrace: memory x31 0xffffe854cd40 00 00 f0 ff 00 00 00 ff 00 00 f0 ff 00 00 00 ff 02 00 00 00 00 00 00>
Feb 15 22:54:58 ip-172-31-71-216 systemd[1]: aerospike.service: Main process exited, code=dumped, status=6/ABRT
Feb 15 22:54:58 ip-172-31-71-216 systemd[1]: aerospike.service: Failed with result 'core-dump'.

Could you run:

journalctl -u aerospike.service --since 2024-02-15 | grep -E "WARNING|CRITICAL"

The provided trace is missing most of the stack frames.