Constant Errors ECONNRESET
See original GitHub issueIs there an existing issue for this?
- I have searched the existing issues
What happened?
Constant errors in log for power strip despite things working.
What, if anything, has recently changed?
Nothing network wise has changed, and nothing I am aware of has changed since the issue began.
Version
7.0.0
Node Version
14.18.3
Homebridge Version
1.4.0
Which OS/Platform?
Linux/Pi
Relevant log output
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
Configuration
Default config.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:27 (7 by maintainers)
Top Results From Across the Web
How do I debug error ECONNRESET in Node.js?
ECONNRESET occurs when the server side closes the TCP connection and your request to the server is not fulfilled. The server ...
Read more >Read ECONNRESET error during "Retrieving the source data"
Answer. ECONNRESET typically can say 3 things: Internet connection suddenly interrupted. Remote server stopped to respond (Salesforce environment maitenance is ...
Read more >axioserror: read econnreset | The AI Search Engine You Control
check error log at api side. In my case, it was error from api side which was throwing exception and its leading to...
Read more >Error Codes (The GNU C Library)
The error code macros are defined in the header file errno.h . All of them expand into integer constant values. Some of these...
Read more >Tuning HTTP Keep-Alive in Node.js - ConnectReport
We suffered some difficult to track down ECONNRESET errors in our Node.js proxy service until we learned a lot about HTTP persistent ......
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 FreeTop 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
Top GitHub Comments
@mven This doesn’t sound like the same issue please open a bug report here with more detail that includes model info
Still having the issue here, any way to suppress this so it isn’t eating up log space?
[12/10/2022, 3:29:52 PM] [TP-Link.API] TCP 192.168.1.122:9999 Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: ‘ECONNRESET’, syscall: ‘read’ } [12/10/2022, 3:29:52 PM] [TP-Link.API] [Seagate] device.send() Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: ‘ECONNRESET’, syscall: ‘read’ } [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link.API] TCP 192.168.1.122:9999 Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: ‘ECONNRESET’, syscall: ‘read’ } [12/10/2022, 3:29:52 PM] [TP-Link.API] [Seagate] device.send() Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: ‘ECONNRESET’, syscall: ‘read’ } [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”} [12/10/2022, 3:29:52 PM] [TP-Link] [Seagate] {“errno”:-104,“code”:“ECONNRESET”,“syscall”:“read”}