Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ClusterServer: channel closed error
See original GitHub issueNot sure what’s the impact of this error. It occurs randomly on my game.
Looks like an Inter-process communication issue from memshared.
Error:
events.js:160
throw er; // Unhandled 'error' event
^
Error: channel closed
at process.target.send (internal/child_process.js:540:16)
at Store.dispatch (/root/crashracing-production/build/node_modules/memshared/lib/Store.js:20:17)
at Object.sismember (/root/crashracing-production/build/node_modules/memshared/lib/commands/set.js:74:18)
at WebSocket.<anonymous> (/root/crashracing-production/build/node_modules/colyseus/lib/matchmaking/Process.js:54:19)
at emitOne (events.js:96:13)
at WebSocket.emit (events.js:188:7)
at Receiver._receiver.onmessage (/root/crashracing-production/build/node_modules/ws/lib/WebSocket.js:141:47)
at Receiver.dataMessage (/root/crashracing-production/build/node_modules/ws/lib/Receiver.js:380:14)
at Receiver.getData (/root/crashracing-production/build/node_modules/ws/lib/Receiver.js:330:12)
at Receiver.startLoop (/root/crashracing-production/build/node_modules/ws/lib/Receiver.js:165:16)
Happened on this call:
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
A channel closed while connecting - Opster
A detailed guide on how to resolve errors related to "a channel closed while connecting"
Read more >"Channel closed" error with concurrent requests #2080 - GitHub
Does your master sometimes crash or quit prematurely? The stack trace looks like a worker trying to ping a master that is no...
Read more >Failed to add 2nd node into failover cluster (server 2012 VM: timeout ...
An error occurred while adding node ... GracefulClose(1226)' because of 'channel to remote endpoint 10.172.2.190:~50236~ is closed'
Read more >node.js: Exception in cluster master process: channel closed
My node.js cluster is able to start 2 worker processes and is working fine. Here is the pseudo code. But if I open...
Read more >Cluster Server 8.0 Agent for Oracle Installation and Configuration ...
Perform the following steps to verify if VCS Oracle agent determines a graceful shutdown of a resource as intentional offline. Bring the resource...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @endel, Thanks, problem solved with new version 0.8.13 and client version 0.8.2
(Thank you for this great library!)
ClusterServerhas been deprecated and this issue shouldn’t happen anymore (https://github.com/gamestdio/colyseus/pull/135)