[Ndn-lib] ndn-js proxy crash FYI

Burke, Jeff jburke at remap.ucla.edu
Sat Mar 16 15:23:10 PDT 2013


Wentao,

I think the round-robin that Alex describes below is supposed to be the default behavior of the library.
Is the data you're publishing routable across the testbed? It should be eventually...

Jeff

From: Alexander Horn <alexnano at ucla.edu<mailto:alexnano at ucla.edu>>
Date: Sat, 16 Mar 2013 14:38:09 -0700
To: Wentao Shang <wentaoshang at gmail.com<mailto:wentaoshang at gmail.com>>
Cc: "ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>" <ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>>
Subject: Re: [Ndn-lib] ndn-js proxy crash FYI

great !

i've updated it, and I have proxy at ndnucla-staging hub on an auto-recover loop that stores crash logs.

let's see how it behaves today; i'll push both to all appboxes tomorrow.

at some point it would be wise to make your web page round-robin w/ the hubs... though not sure if Jeff wants to do that before monday's demo? depends how confident we are in testbed connectivity :)

A.ws.ndn.ucla.edu<http://a.ws.ndn.ucla.edu/> [PARC]
B.ws.ndn.ucla.edu<http://b.ws.ndn.ucla.edu/> [UCLA-APPS-STAGING]
C.ws.ndn.ucla.edu<http://c.ws.ndn.ucla.edu/> [ARIZONA]
D.ws.ndn.ucla.edu<http://d.ws.ndn.ucla.edu/> [CAIDA]
E.ws.ndn.ucla.edu<http://e.ws.ndn.ucla.edu/> [ILLINOIS]

On Fri, Mar 15, 2013 at 5:53 PM, Wentao Shang <wentaoshang at gmail.com<mailto:wentaoshang at gmail.com>> wrote:
Hi Alex,

Thanks for discovering this bug. After some analysis I believe the crash is caused by the situation when the client first asks for a data and then closes websocket connection before the server returns the answer. The proxy would then write to a broken tcp connection and throw an exception. I pushed a new version of wsproxy-tcp.js to the github, which should solve this issue. Can you help test the new code on our app box?

Best,
Wentao


On Fri, Mar 15, 2013 at 1:18 PM, Alexander Horn <alexnano at ucla.edu<mailto: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<mailto:Ndn-lib at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-lib




--
PhD student @ Internet Research Lab, Computer Science Department, University of California, Los Angeles

_______________________________________________ Ndn-lib mailing list Ndn-lib at lists.cs.ucla.edu<mailto: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/20130316/6145689b/attachment.html>


More information about the Ndn-lib mailing list