[GH-ISSUE #85] Lost TCP conetion.. #64

New issue

Closed

opened 2026-02-26 05:31:13 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @airclear on GitHub (Jun 29, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/85

when the log.io-harvester was killed

log.io-server always echo "eror : Lost TCP Connection..."

how can handle this ?

Originally created by @airclear on GitHub (Jun 29, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/85 when the log.io-harvester was killed log.io-server always echo "eror : Lost TCP Connection..." how can handle this ?

kerem closed this issue

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

kerem commented

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

Author

Owner

@airclear commented on GitHub (Jul 2, 2013):

it Cause by the ping interval ...
need to clear it .

@airclear commented on GitHub (Jul 2, 2013): it Cause by the ping interval ... need to clear it .

kerem commented

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

Author

Owner

@xakraz commented on GitHub (Jul 18, 2013):

I'm using log.io 0.3.3 and have the same issue when a harvester node stop.

More over, when the same node restart log.io-harvester, it does not reappear in the Web UI
(in fact it register and a few second after it goes away....)

How can we handle harvest node connection / Deconnection / reconnection to the server?
The only way I have found is to :

stop every harvester
restart the server
restart every harvester

@xakraz commented on GitHub (Jul 18, 2013): I'm using log.io 0.3.3 and have the same issue when a harvester node stop. More over, when the same node restart log.io-harvester, it does not reappear in the Web UI (in fact it register and a few second after it goes away....) How can we handle harvest node connection / Deconnection / reconnection to the server? The only way I have found is to : - stop every harvester - restart the server - restart every harvester

kerem commented

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

Author

Owner

@dvliman commented on GitHub (Jul 29, 2013):

I am having the same issue where the harvester stop and throw ENOENT on a log that was used to able to open
and as a result, log.io-server stops and says: Lost TCP connection

@dvliman commented on GitHub (Jul 29, 2013): I am having the same issue where the harvester stop and throw ENOENT on a log that was used to able to open and as a result, log.io-server stops and says: Lost TCP connection

kerem commented

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

Author

Owner

@msmathers commented on GitHub (Aug 1, 2014):

This has been addressed in v0.3.4. Both the server and harvester will gracefully recover from connection thrashing.

@msmathers commented on GitHub (Aug 1, 2014): This has been addressed in v0.3.4. Both the server and harvester will gracefully recover from connection thrashing.