GDP

The summary is it seems like logdname = edu.berkeley.eecs.gdp-01.gdplogd is causing problems, but changing it to edu.berkeley.eecs.gdp-02.gdplogd works?

Below are the details.

The accessors build is hanging during gcl create under Ubuntu, RHEL and Mac OS X.

To replicate:

svn co https://repo.eecs.berkeley.edu/svn-anon/projects/terraswarm/accessors/trunk/accessors
cd accessors/web
ant tests.mocha

The output will end with:

     [exec]   NodeHost
     [exec] GDPLogAppend.js: setup()
     [exec] Instantiated accessor GDPLogCreateAppendReadJS.js with class ./gdp/test/auto/GDPLogCreateAppendReadJS.js
     [exec] GDPLogCreate.js: initialize()
     [exec] GDPLogAppend.js: initialize()
     [exec] JavaScriptGDPLogName: ptolemy.actor.lib.jjs.modules.gdp.test.auto.GDPLogSubscribeJS.0.3682781502617527
     [exec] GDPLogCreate.js: create() Start.

If I use place the ant process in the background, use ps to find the node process and gdb -p to attach to the process, I get:

(gdb) where
#0  0x000000344b20e334 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x000000344b2095d8 in _L_lock_854 () from /lib64/libpthread.so.0
#2  0x000000344b2094a7 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x00007f3ee080ce01 in _ep_thr_mutex_lock (mtx=0x3558390, file=0x7f3ee0811168 "gdp_req.c", line=347,
    name=0x7f3ee081115c "&req->mutex") at ep_thr.c:232
#4  0x00007f3ee0803a04 in _gdp_req_lock (req=0x3558390) at gdp_req.c:347
#5  0x00007f3ee0803fee in _gdp_req_freeall (reqlist=0x3558580, shutdownfunc=0) at gdp_req.c:307
#6  0x00007f3ee07fd56a in _gdp_gcl_freehandle (gcl=0x3558540) at gdp_gcl_ops.c:132
#7  0x00007f3ee07fb541 in _gdp_gcl_decref (gclp=0x7fff77307ce0) at gdp_gcl_cache.c:603
#8  0x00007f3ee07fd9c7 in _gdp_gcl_create (
    gclname=0x3532608 "\363\034\362\201\216\217\036\226\207Rf\352\001\375k\357?\331\004\as\204\255\216xReBJ\201\223 ۛ\221b\
\001^\271\271\365|9\355Ҋw\353\071\223\334o5\355\224ӆ\372Y\203\370\244\254\023U", logdname=<value optimized out>,
    gmd=0x353ca40, chan=0x353c5b0, reqflags=<value optimized out>, pgcl=0x3532600) at gdp_gcl_ops.c:285
#9  0x00007f3ee07f7cd8 in gdp_gcl_create (
    gclname=0x3532608 "\363\034\362\201\216\217\036\226\207Rf\352\001\375k\357?\331\004\as\204\255\216xReBJ\201\223 ۛ\221b\
\001^\271\271\365|9\355Ҋw\353\071\223\334o5\355\224ӆ\372Y\203\370\244\254\023U",
    logdname=0x3532628 "\233\221b\001^\271\271\365|9\355Ҋw\353\071\223\334o5\355\224ӆ\372Y\203\370\244\254\023U",
    gmd=0x353ca40, pgcl=0x3532600) at gdp_api.c:331
#10 0x00007f3ee0c2a84c in ffi_call_unix64 ()
   from /tmp/atest/accessors/web/node_modules/ffi/build/Release/ffi_bindings.node
#11 0x00007f3ee0c29ff3 in ffi_call () from /tmp/atest/accessors/web/node_modules/ffi/build/Release/ffi_bindings.node
#12 0x00007f3ee0c22ae4 in FFI::FFICall(Nan::FunctionCallbackInfo<v8::Value> const&) ()
   from /tmp/atest/accessors/web/node_modules/ffi/build/Release/ffi_bindings.node
#13 0x00007f3ee0c22436 in Nan::imp::FunctionCallbackWrapper(v8::FunctionCallbackInfo<v8::Value> const&) ()
   from /tmp/atest/accessors/web/node_modules/ffi/build/Release/ffi_bindings.node
#14 0x0000000000981681 in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> cons\
t&)) ()
#15 0x00000000009d5b0b in v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiC\
allHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtr\
aArguments)1>) ()
#16 0x00000000009d60b1 in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) ()
#17 0x000033f454e0961b in ?? ()
#18 0x00001eed3f2412b1 in ?? ()

However, gcl_create works fine.

I'm not sure what happened, I had a successful run on Dec 12, 2016 9:01:07 AM.

I updated the @terraswarm/gdp package after that, but I believe I was able to run the gdp tests.

I checked out a version of the accessors repo from before yesterday's changes and that did not change anything.

So, perhaps there is something up with the gdp server?

I changed the logdname server to edu.berkeley.eecs.gdp-02.gdplog and the problem went away.