[Ndn-lib] ndn-js proxy crash FYI

Alexander Horn alexnano at ucla.edu
Fri Mar 15 15:32:49 PDT 2013


ok, i'll put all app boxes on loop... i'll still accumulate stderr

On Fri, Mar 15, 2013 at 3:02 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:

>  As far as possible, it needs to be resilient for Sunday-Tuesday, though
> J.
>
>   From: Alexander Horn <alexnano at ucla.edu>
> Date: Fri, 15 Mar 2013 14:59:40 -0700
> To: Alex Afanasyev <alexander.afanasyev at ucla.edu>
> Cc: "ndn-lib at lists.cs.ucla.edu" <ndn-lib at lists.cs.ucla.edu>
> Subject: Re: [Ndn-lib] ndn-js proxy crash FYI
>
>  yes of course - we did this w/ video publishing on appboxes - but only
> after we tested it and got the bugs out for 6+ months :)
>
>  meanwhile, it's still early days for this (traffic/usage wise) - so it's
> useful to have it crash so we find this stuff.
>
>  if it gets to be an issue for stability, i'll wrap in while loop.
>
>  thanks !
>
>
> On Fri, Mar 15, 2013 at 1:26 PM, Alex Afanasyev <
> alexander.afanasyev at ucla.edu> wrote:
>
>>  I guess it may not be a good idea for the development stage, but why
>> not to wrap ws-proxy in some watchdog app (e.g., bash script like   while
>> true; do node <proxy>; sleep 1; <email somebody>; done) ?
>>
>>  This is what I approximately do with macports version, but relying on
>> OSX watchdog capabilities (launchd).
>>
>>  --
>> Alex
>>
>>   On Mar 15, 2013, at 1:18 PM, Alexander Horn <alexnano at ucla.edu> wrote:
>>
>>   Team,
>>
>>  it's great to see ndn-js getting used in multiple projects.
>>
>>  ws-proxy is pretty stable on the app boxes... yet last night, after a
>> few weeks of uptime the ws-proxy on UCLA app box crashed.
>>
>>  ccndstatus indicates route to hub was still up; box appeared normal -
>> ccnd & route up, online... just no ws-proxy.
>>
>>  The only thing different about this app box, is it's
>> directly communicating w/ Wentao's latest ndn-js client for BMS/repo data.
>> http://borges.metwi.ucla.edu/ndn-sensor/status.html
>>
>>  I have full packet capture via ws-proxy logging (15MB) if wanted;
>> meanwhile here's stderr:
>>
>>
>> /home/localadmin/NDNAppBox/installer/ndn-js/wsproxy/node_modules/ws/lib/WebSocket.js:175
>>     else throw new Error('not opened');
>>          ^
>> Error: not opened
>>     at WebSocket.send
>> (/home/localadmin/NDNAppBox/installer/ndn-js/wsproxy/node_modules/ws/lib/WebSocket.js:175:16)
>>     at Socket.<anonymous>
>> (/home/localadmin/NDNAppBox/installer/ndn-js/wsproxy/wsproxy-tcp.js:101:7)
>>     at Socket.EventEmitter.emit (events.js:96:17)
>>   _______________________________________________
>> Ndn-lib mailing list
>> Ndn-lib at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-lib
>>
>>
>>
>  _______________________________________________ Ndn-lib mailing list
> Ndn-lib at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-lib
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/mailman/private/ndn-lib/attachments/20130315/3284d749/attachment-0001.html>


More information about the Ndn-lib mailing list