Open leyue opened 6 years ago
add some info: form docker container: ###################################################
socketcluster-sample@1.0.0 start:docker /usr/src node dockerwait.js && node ${SOCKETCLUSTER_MASTER_CONTROLLER:-server.js}
[0;33m[Busy][0m Launching SocketCluster
Broker PID: 43 WorkerCluster PID: 53 Worker PID: 59 [0;32m[Active][0m SocketCluster started Version: 13.1.7 Environment: prod WebSocket engine: ws Port: 8000 Master PID: 33 Worker count: 1 Broker count: 1
{ SocketProtocolError: Socket hung up
at SCSocket._onSCClose (/usr/src/node_modules/scc-broker-client/node_modules/socketcluster-client/lib/scsocket.js:652:15)
at SCTransport.
These errors seem to indicate that the server could not be reached or it took too long to establish the connection. Maybe there is a load balancer/proxy which is blocking or throttling the connection. You can also get this error if a socket disconnects abruptly without sending a WebSocket close control frame.
It's normal to get these 'Socket hung up' messages from time to time in production though.
env:
1: ingress rules:
bug:
Most of the time can be connected successfully but some times: (from chrome devtool)