Docker stops running after a period of time

[maketou]

1、
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}

2、
Node.js v18.15.0
info: Updating Game Files...
info: Logging in 011173388
debug: 011173388 About to connect
info: Logging in vyrun67834
debug: vyrun67834 About to connect
info: Listening for HTTP on port: 80
info: 011173388 Log on OK
info: 011173388 Initiating GC Connection
debug: Sending GC message ClientHello
debug: Sending hello, setting timer for next attempt to 2000 ms
debug: Got handled GC message ClientWelcome
debug: Unknown SO type 2 with 1 items
debug: Unknown SO type 7 with 1 items
debug: GC connection established
info: 011173388 CSGO Client Ready!
debug: Got handled GC message MatchmakingGC2ClientHello
debug: Got unhandled GC message ClientGCRankUpdate
debug: Got unhandled GC message GC2ClientGlobalStats
info: vyrun67834 Log on OK
info: vyrun67834 Initiating GC Connection
debug: Sending GC message ClientHello
debug: Sending hello, setting timer for next attempt to 2000 ms
debug: Got handled GC message ClientWelcome
debug: Unknown SO type 2 with 1 items
debug: Unknown SO type 7 with 1 items
debug: GC connection established
info: vyrun67834 CSGO Client Ready!
debug: Got handled GC message MatchmakingGC2ClientHello
debug: Got unhandled GC message GC2ClientGlobalStats
debug: Got unhandled GC message ClientGCRankUpdate
debug: Fetched schema.json
debug: Fetched items_game.txt
node:events:491
throw er; // Unhandled 'error' event
^

Error: read ETIMEDOUT
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'read'
}

[stazeworks]

Same for me.
I suggest that problem source is Steam User module by Alex Corn, probably in protobuf messages while processing inspections via proxy

[mdf45]

Same problem...
"steam-user": "^5.0.9"
"globaloffensive": "^3.1.0"

[wangxingzhen]

This seems to have something to do with networking, so try adding a restart policy that restarts your program when an exception exits.The change I made to this is to modify the docker_start.sh file to add some listener exit code that will wait a few minutes to restart if the code is not equal to 0.The reason we wait a few minutes for the restart is because this can happen many times over a short period of time,so, try to run multiple docker containers at the same time so that if one of them exits, it won't affect the service

while true; do
    node index.js -c /config/config.js -s /config/steam_data
    exit_status=$?
  if [ $exit_status -ne 0 ]; then
    sleep 600
  else
    exit 0
  fi
done