[GH-ISSUE #203] log.io-server Running for a period of time, automatically throwing exceptions #171

New issue

Closed

opened 2026-02-26 05:31:30 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 05:31:30 +03:00

Owner

Originally created by @timosir on GitHub (Jan 29, 2019).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/203

events.js:173
throw er; // Unhandled 'error' event
^

Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:162:27)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process.internalTickCallback (internal/process/next_tick.js:72:19)

Originally created by @timosir on GitHub (Jan 29, 2019). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/203 events.js:173 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:162:27) Emitted 'error' event at: at emitErrorNT (internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at process.internalTickCallback (internal/process/next_tick.js:72:19)

kerem closed this issue

2026-02-26 05:31:30 +03:00

kerem commented

2026-02-26 05:31:31 +03:00

Author

Owner

@timosir commented on GitHub (Jan 29, 2019):

[root@localhost nodejs]# npm -v
6.5.0-next.0
[root@localhost nodejs]# node -v
v11.6.0

@timosir commented on GitHub (Jan 29, 2019): [root@localhost nodejs]# npm -v 6.5.0-next.0 [root@localhost nodejs]# node -v v11.6.0

kerem commented

2026-02-26 05:31:31 +03:00

Author

Owner

@msmathers commented on GitHub (Jan 12, 2020):

Looks like one or more harvester processes are resetting their connections to the server. Both the harvester and server have been rewritten in v0.4.3, give those a try and report back if the same issue occurs.

@msmathers commented on GitHub (Jan 12, 2020): Looks like one or more harvester processes are resetting their connections to the server. Both the harvester and server have been rewritten in v0.4.3, give those a try and report back if the same issue occurs.