Alright, so I’m deploying some new code at PageLever to move our Facebook sync code to node.js. I’ve just slaved over it for a few weeks, creating a queue/worker system (to be publicly released soon) that keeps track of lots of stats and more importantly errors. Very very important to see our errors. Is the problem with us or Facebook? Have we hit our API limits again? Did I fat-finger yet another FQL statement? You know, the vital stuff.
So now I’ve pushed it out there and started up a bunch of workers and I’m monitoring all of them. I start getting a few errors trickling in. No problem, this happens. Let’s check out what they say.
Error: socket hang up at Object. (http.js:1124:15) at CleartextStream. (http.js:1173:23) at CleartextStream.emit (events.js:64:17) at Array. (tls.js:792:22) at EventEmitter._tickCallback (node.js:190:38)