Detail
When trying to start Aerospike on on node upgraded to 7.2, a message similar to the following is received :-
Oct 29 10:38:15 test-server1 systemd[1]: aerospike_X@1.service: Control process exited, code=exited status=203
Oct 29 10:38:15 test-server1 systemd[1]: aerospike_X@1.service: Failed with result 'exit-code'.
Oct 29 10:46:06 test-server1 systemd[490726]: aerospike_X@0.service: Failed to execute command: No such file or directory
Oct 29 10:46:06 test-server1 systemd[490726]: aerospike_X@0.service: Failed at step EXEC spawning /usr/bin/asd-systemd-helper: No such file or directory
Answer
The aerospike_X@0.service likely indicates that numa has been setup with custom systemd scripts as per our documentation :-
https://aerospike.com/docs/server/operations/manage/aerospike/multiple
Because 7.2 has now removed the asd-systemd-helper, a new custom start script will have to be generated.
It is also important that the new best-practices are followed as these formed part of the old asd-system-helper.
https://aerospike.com/docs/server/operations/manage/aerospike
https://aerospike.com/docs/reference/release_notes/server/7.2-server-release-notes
- New best practice checks at startup:
rmem-max(which comes from /proc/sys/net/core/rmem_max) must be greater than 15MiBwmem-max(which comes from /proc/sys/net/core/wmem_max) must be greater than 5MiB- The
asd-systemd-helperscript used to set rmem_max and wmem_max, and also potentially raised shmmax to 1GiB (less useful now that data may also use shmem). This script has been removed.