# Start aerospike.service fail with aerospike-server-community\_6.4.0.19

**URL:** <https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324>\
**Category:** General Discussion\
**Created:** [July 29, 2024, 3:40am UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324 "2024-07-29T03:40:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhicun](https://avatars.discourse-cdn.com/v4/letter/z/977dab/32.png) [@zhicun](https://discuss.aerospike.com/u/zhicun)\
**Post date:** [July 29, 2024, 3:40am UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324/1 "2024-07-29T03:40:42Z")

</div>

```auto
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

```

---

<div class="post-metadata">

**Author:** ![pgupta](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/pgupta/32/2351_2.png) [@pgupta](https://discuss.aerospike.com/u/pgupta)\
**Post date:** [July 31, 2024, 8:11pm UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324/2 "2024-07-31T20:11:08Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![zhicun](https://avatars.discourse-cdn.com/v4/letter/z/977dab/32.png) [@zhicun](https://discuss.aerospike.com/u/zhicun)\
**Post date:** [August 1, 2024, 7:12am UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324/3 "2024-08-01T07:12:07Z")

</div>

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.

```auto
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
        }
}

```

---

<div class="post-metadata">

**Author:** ![meher](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/meher/32/1644_2.png) [@meher](https://discuss.aerospike.com/u/meher)\
**Post date:** [August 20, 2024, 9:32pm UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324/4 "2024-08-20T21:32:11Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [August 20, 2025, 9:32pm UTC](https://discuss.aerospike.com/t/start-aerospike-service-fail-with-aerospike-server-community-6-4-0-19/11324/5 "2025-08-20T21:32:25Z")

</div>

Closed on August 20, 2025, 9:32pm UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.