The client tried twice requests with the non-exist namespace and the server is down. Log as below:
Nov 17 2015 03:37:40 GMT: WARNING (demarshal): (thr_demarshal.c::570) Can't get namespace from AS_MSG (peeked 83 bytes) ~~ Using default thr_demarshal arena.
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::160) SIGSEGV received, aborting Aerospike Community Edition build 3.5.15
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: found 7 frames
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 0: /opt/aerospike/bin/asd(as_sig_handle_segv+0x59) [0x46f718]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 1: /lib64/libc.so.6() [0x3dc08326a0]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 2: /opt/aerospike/bin/asd(as_msg_peek_data_in_memory+0x32) [0x4676e2]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 3: /opt/aerospike/bin/asd(thr_tsvc_process_or_enqueue+0x29) [0x4c027f]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 4: /opt/aerospike/bin/asd(thr_demarshal+0x38f) [0x48416a]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 5: /lib64/libpthread.so.0() [0x3dc0c07a51]
Nov 17 2015 03:37:40 GMT: WARNING (as): (signal.c::162) stacktrace: frame 6: /lib64/libc.so.6(clone+0x6d) [0x3dc08e893d]
Which client are you using? Is that the full stack trace?
Did you test in a later Aerospike version?
@Vincent_Lee,
Help is on the way. In the meantime, please be aware that at the time of this writing, we are now on Aerospike Server Community Edition v3.6.4 and have implemented a number of improvements, new features and bug fixes since v3.5.15, which came out in July.
using Java client，maybe caused by Key key = new Key(null, “demo”, “putgetkey”); with null namespace?
I have read the release note and found the new version has some big changes. We currently use aerospike for online service so we need to do more test and wait that version to be stable.
Please can you paste the full stack trace and your OS, I will see if it matches any known issues
The above is the full stack trace already. My OS is centos: 2.6.32-504.16.2.el6.x86_64
cool thanks, I’ll see if it’s a known problem
Hi Vincent, this is a known issue which is being tracked under AER-4589
1 Like
Got it, Thanks.
I could not find that in the release note and it would be next release, is that right?
right now it is still showing as unresolved and so we do not have a target release. Please keep an eye on the release notes as this is where you will see it logged.
We found a new crash while using the newest version 3.7.1 and not sure if this is the same issue.
By the way, this happened while we did the secondary index query without namespace or null namespace.
Feb 22 2016 07:08:11 GMT: WARNING (demarshal): (thr_demarshal.c::610) Can't get namespace from AS_MSG (peeked 120 bytes) ~~ Using default thr_demarshal arena.
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::161) SIGSEGV received, aborting Aerospike Community Edition build 3.7.1 os el6
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: found 7 frames
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 0: /usr/bin/asd(as_sig_handle_segv+0x62) [0x48c607]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 1: /lib64/libc.so.6() [0x3dc08326a0]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 2: /usr/bin/asd(as_msg_peek_data_in_memory+0x32) [0x485f95]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 3: /usr/bin/asd(thr_tsvc_process_or_enqueue+0x29) [0x4da32e]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 4: /usr/bin/asd(thr_demarshal+0xc5f) [0x4a2f81]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 5: /lib64/libpthread.so.0() [0x3dc0c07a51]
Feb 22 2016 07:08:11 GMT: WARNING (as): (signal.c::163) stacktrace: frame 6: /lib64/libc.so.6(clone+0x6d) [0x3dc08e893d]