[GH-ISSUE #120] error: Lost TCP connection... #97

New issue

Closed

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

kerem commented

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

Owner

Originally created by @needforspeed on GitHub (Jul 16, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/120

I see this in the log.io-server terminal. What caused this problem?

In addition I see incomplete log message line in the web page stream area. Each line start with time stamp, like this [Wed Jul 16 13:39:51 2014]. Most lines are complete, but some lines only shows the very first character [, without anything after that.

I'm using ubuntu 14.04 and my log.io version is 0.3.3

Originally created by @needforspeed on GitHub (Jul 16, 2014). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/120 I see this in the `log.io-server` terminal. What caused this problem? In addition I see incomplete log message line in the web page stream area. Each line start with time stamp, like this `[Wed Jul 16 13:39:51 2014]`. Most lines are complete, but some lines only shows the very first character `[`, without anything after that. I'm using ubuntu 14.04 and my `log.io` version is 0.3.3

kerem closed this issue

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

kerem commented

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

Author

Owner

@jnovack commented on GitHub (Jul 23, 2014):

I notice this when I restart the server or harvester.

It is VERY picky that it has to start up in the right order.

Start server
Start harvester(s)
Refresh webpage

We should be able to start them in any order, and restart them at will.

@jnovack commented on GitHub (Jul 23, 2014): I notice this when I restart the server or harvester. It is VERY picky that it has to start up in the right order. 1. Start server 2. Start harvester(s) 3. Refresh webpage We should be able to start them in any order, and restart them at will.

kerem commented

2026-02-26 05:31:20 +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.