Articles in this section

Why is the asd service failing to start with "aligned allocation during startup" error?

Detail

Following Critical Assertion is seen in the logs on Centos 9 or Debian 13:

The CRITICAL messsage is key

 

  CRITICAL (alloc): (alloc.c:1255) aligned allocation during startup

But also these lines are important

 


Jun 17 11:20:58 mc-t44453 asd[1352]: Jun 17 2026 11:20:58 GMT: WARNING (as): (signal.c:405) stacktrace: frame 6: /usr/bin/asd(posix_memalign /work/source/cf/src/alloc.c:1201) [0x31b080]
Jun 17 11:20:58 mc-t44453 asd[1352]: Jun 17 2026 11:20:58 GMT: WARNING (as): (signal.c:405) stacktrace: frame 7: /lib/x86_64-linux-gnu/libcrypto.so.3(CRYPTO_aligned_alloc) [0x7f00e0074adb]

 

 


Answer

Issue observed when upgrading to versions of the Openssl Library 3.4 (and above):

openssl-3.5.0-1.el9.x86_64.rpm          
openssl-libs-3.5.0-1.el9.x86_64.rpm 

Current workaround is to downgrade the two packages to a version below openssl 3.4, or to upgrade Aerospike to a version that has the issue resolved.

yum downgrade openssl-libs-3.2.2-7.el9.x86_64 openssl-3.2.2-7.el9.x86_64

Aerospike details :-

https://aerospike.com/docs/database/reference/issues/?search=align#AER-6818


Notes

AER-6818 - Enterprise & Community

Issue introduced in 4.6.0.2
 
Fixed in versions :-
8.0.0.8, 7.2.0.11, 7.1.0.17, 7.0.0.25, 6.4.0.33

Applies To Earliest Version

Pre 4.9


Applies To Latest Version

8.0


Was this article helpful?
0 out of 0 found this helpful