search

csfloat / inspect

Source Code that Powers the CSFloat Inspect Link API
https://csgofloat.com
MIT License
384 stars 117 forks source link

Docker stops running after a period of time #212

Open maketou opened 5 months ago

maketou commented 5 months ago

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 commented 3 months ago

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 commented 3 months ago

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