Aerospike crashes (3.5.15) - resolved by upgrading to 3.6.1 [Resolved]


#1

Aerospaik (3.5.15) crashes when working with largedatasets (presumably), Is there a way to verify the cause of this?

Here the log:

Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::93) SIGABRT received, aborting Aerospike Community Edition build 3.5.15
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: found 24 frames
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 0: /usr/bin/asd(as_sig_handle_abort+0x54) [0x46ea38]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 1: /lib/x86_64-linux-gnu/libc.so.6(+0x36d40) [0x7f604e162d40]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 2: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f604e162cc9]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 3: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f604e1660d8]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 4: /lib/x86_64-linux-gnu/libc.so.6(+0x2fb86) [0x7f604e15bb86]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 5: /lib/x86_64-linux-gnu/libc.so.6(+0x2fc32) [0x7f604e15bc32]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 6: /lib/x86_64-linux-gnu/libpthread.so.0(+0x110a6) [0x7f604f0430a6]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 7: /lib/x86_64-linux-gnu/libpthread.so.0(+0x5e9f) [0x7f604f037e9f]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 8: /usr/bin/asd() [0x5a2703]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 9: /usr/bin/asd(free+0x350) [0x57ece0]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 10: /usr/bin/asd(cf_free_at+0x7e) [0x4fa508]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 11: /usr/bin/asd(as_string_val_destroy+0x3e) [0x5219fc]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 12: /usr/bin/asd(as_val_val_destroy+0x39) [0x521b4e]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 13: /usr/bin/asd(as_hashmap_clear+0x37) [0x522b79]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 14: /usr/bin/asd(as_hashmap_release+0xe) [0x522c3f]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 15: /usr/bin/asd(as_val_val_destroy+0x39) [0x521b4e]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 16: /usr/bin/asd(as_arraylist_release+0x32) [0x521cd4]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 17: /usr/bin/asd(as_val_val_destroy+0x39) [0x521b4e]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 18: /usr/bin/asd(as_msg_make_response_bufbuilder+0xa92) [0x467d43]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 19: /usr/bin/asd(tscan_tree_reduce+0x53c) [0x4b70b7]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 20: /usr/bin/asd(as_index_reduce_partial+0x190) [0x45b45a]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 21: /usr/bin/asd(tscan_partition_thr+0xa70) [0x4b8329]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 22: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7f604f03a182]
Aug 22 2015 10:33:24 GMT: WARNING (as): (signal.c::95) stacktrace: frame 23: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f604e22647d]

#2

@max83,

Help is on the way. In the meantime, please let us know what operating system you are running, please.


#3

Ubuntu, 14.04.3 AMD64.


#4

Hi Max83,

Has the issue returned? By chance, have you noticed any steps that lead up to the failure?

Are you using UDFs?

I don’t know that you would want to share this information, but would you look in /var/log/dmesg, and look for recent failures?

Thank you for your time,

-DM


#5

@max83,

We just released Aerospike Server Community Edition version 3.6.0, in which we have completely redone Scan. Please upgrade to this new version and let us know if you still experience this issue. It’s available for download here.


#6

After update to 3.6.1 have no repeats of this issue. Thanks