[Ndn-lib] ndn-js proxy crash FYI
alexander.afanasyev at ucla.edu
Fri Mar 15 13:26:11 PDT 2013
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).
On Mar 15, 2013, at 1:18 PM, Alexander Horn <alexnano at ucla.edu> wrote:
> 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:
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-lib