Node.js client crashing


#1

Hello

We are using node.js

ubuntu@ip-XXX-XXX-XXX-XXX:/path/to/app/node_modules/aerospike$ ls -l
total 196
-rw-r--r-- 1 ubuntu ubuntu 116266 May 26 07:01 aerospike-1.0.40.tgz
drwxr-xr-x 6 root   root     4096 Jun 12 15:05 aerospike-client-c
drwxr-xr-x 2 ubuntu ubuntu   4096 Jun 12 15:05 benchmarks
-rw-r--r-- 1 ubuntu ubuntu   2460 May 26 07:01 binding.gyp
drwxr-xr-x 4 root   root     4096 Jun 12 15:05 build
drwxr-xr-x 2 ubuntu ubuntu   4096 Jun 12 15:05 docs
drwxr-xr-x 2 ubuntu ubuntu   4096 Jun 12 15:05 examples
drwxr-xr-x 2 ubuntu ubuntu   4096 Jun 12 15:05 lib
-rw-r--r-- 1 ubuntu ubuntu  11357 May 26 07:01 LICENSE
drwxr-xr-x 3 ubuntu ubuntu   4096 Jun 12 15:05 node_modules
-rw-r--r-- 1 ubuntu ubuntu   1625 Jun 12 15:05 package.json
-rw-r--r-- 1 ubuntu ubuntu  12477 May 26 07:01 README.md
drwxr-xr-x 2 ubuntu ubuntu   4096 May 26 07:01 scripts
drwxr-xr-x 4 ubuntu ubuntu   4096 Jun 12 15:05 src
drwxr-xr-x 4 ubuntu ubuntu   4096 Jun 12 15:05 test

On an ubuntu machine

ubuntu@ip-XXX-XXX-XXX-XXX:$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.5 LTS
Release:        12.04
Codename:       precise

We have upgraded to the latest (sudo ap-get upgrade)

When running our program crashes and syslog says:

Jun 12 19:06:42 ip-192-168-26-222 kernel: [2171613.888023] node[30348]: segfault at 4 ip 00007f11af1c9823 sp 00007f11a7ffe9f8 error 6 in libc-2.15.so[7f11af080000+1b4000]

We would greatly appreciate any help

Thank you


#2

Ran gdb. Here is the trace

[...]
Loaded symbols for /usr/local/lib/libprotobuf.so.7
0x00007f3bf9863539 in syscall () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f3bf3fff700 (LWP 41366)]
0x00007f3bf98bd833 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) backtrace
#0  0x00007f3bf98bd833 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f3bf950f2e7 in as_vector_append (vector=<optimized out>, value=0x7f3bf3ffeda0) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
#2  as_batch_execute (as=<optimized out>, as@entry=<error reading variable: Cannot access memory at address 0x7f3bf3ffede8>, 
    err=<error reading variable: Cannot access memory at address 0x7f3bf3ffecf0>, policy=<error reading variable: Cannot access memory at address 0x7f3bf3ffecc0>, 
    callback=<error reading variable: Cannot access memory at address 0x7f3bf3ffecb8>, udata=<error reading variable: Cannot access memory at address 0x7f3bf3ffedf0>, 
    read_attr=<error reading variable: Cannot access memory at address 0x7f3bf3ffedf8>, bins=<error reading variable: Cannot access memory at address 0x7f3bf3ffee00>, 
    n_bins=<error reading variable: Cannot access memory at address 0x7f3bf3ffee08>, batch=<optimized out>) at src/main/aerospike/aerospike_batch.c:424
(gdb)

#3

I noticed the json client is downloading aerospike c version 3.1.8. Will attempt to get it to download the latest.


#4

I upgraded to 3.1.16. It still crashed.

Program received signal SIGSEGV, Segmentation fault.
0x000000000074b074 in v8::internal::GlobalHandles::Destroy(v8::internal::Object**) ()
(gdb) bt
#0  0x000000000074b074 in v8::internal::GlobalHandles::Destroy(v8::internal::Object**) ()
#1  0x00007f145d3f4f28 in v8::Persistent<v8::Function>::Dispose() () at /home/ubuntu/.node-gyp/0.10.31/deps/v8/include/v8.h:4245
#2  0x00007f145d3f5032 in void NanAssignPersistent<v8::Function>(v8::Persistent<v8::Function>&, v8::Handle<v8::Function>) () at ../node_modules/nan/nan.h:872
#3  0x00007f145d3f72da in prepare () at ../src/main/client/batch_select.cc:138
#4  0x00007f145d4184ef in async_invoke(v8::Arguments const&, void* (*)(v8::Arguments const&), void (*)(uv_work_s*), void (*)(uv_work_s*, int)) () at ../src/main/util/async.cc:39
#5  0x00007f145d3f8463 in AerospikeClient::BatchSelect(v8::Arguments const&) () at ../src/main/client/batch_select.cc:381
#6  0x00000000006fdbab in ?? ()
#7  0x00003ba51b806362 in ?? ()
#8  0x00003ba51b849855 in ?? ()
#9  0x00003ba51b8062c1 in ?? ()

#5

We are using node.js 0.10.38. We are porting our app to 0.12.4 to see if it fixes the issue


#6

Hi mlabour,

I am looking into this issue. I’ll update you as soon as I root cause the issue. Sorry for the inconvenience.

Thanks