SocketCluster / SocketCluster/socketcluster
worker crashing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
@jondubois hey man is there an easy way to track this down?
1|handler | 1527890188676 - Origin: Worker (PID 8416)
1|handler | [Error] SocketProtocolError: Socket hung up
1|handler | at SCClientSocket._onSCClose (/var/www/handler/node_modules/socketcluster-client/lib/scclientsocket.js:647:15)
1|handler | at SCTransport.<anonymous> (/var/www/handler/node_modules/socketcluster-client/lib/scclientsocket.js:292:12)
1|handler | at SCTransport.Emitter.emit (/var/www/handler/node_modules/component-emitter/index.js:133:20)
1|handler | at SCTransport._onClose (/var/www/handler/node_modules/socketcluster-client/lib/sctransport.js:212:28)
1|handler | at WebSocket.SCTransport.wsSocket.onclose (/var/www/handler/node_modules/socketcluster-client/lib/sctransport.js:66:10)
1|handler | at WebSocket.onClose (/var/www/handler/node_modules/socketcluster-client/node_modules/ws/lib/event-target.js:124:16)
1|handler | at emitTwo (events.js:126:13)
1|handler | at WebSocket.emit (events.js:214:7)
1|handler | at WebSocket.emitClose (/var/www/handler/node_modules/socketcluster-client/node_modules/ws/lib/websocket.js:172:10)
1|handler | at TLSSocket.socketOnClose (/var/www/handler/node_modules/socketcluster-client/node_modules/ws/lib/websocket.js:774:15)
1|handler | 1527890188684 - Worker 0 exited - Exit code: ****
I want to figure out what's causing it and stop it. I can't seem to figure out what's causing it. None of our other servers are doing this. Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported stack frames in node_modules/socketcluster-client/lib/scclientsocket.js:647 and sctransport.js:212, then compare the affected server with the servers that do not fail. The issue is resolved when the socket-hang-up cause is identified and the worker no longer exits unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100