mirror of
https://github.com/NarrativeScience-old/log.io.git
synced 2026-04-25 17:15:52 +03:00
[GH-ISSUE #40] Checking one specific log file on the client make the harvester to reconnect without any error message #31
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/log.io-NarrativeScience-old#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @huafu on GitHub (Sep 30, 2012).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/40
To help understand my explanation here is a little definitions:
So I have on server S1 with locally running one harvester LH1 and one Log.io server LS1, and another server S2 with an harvester LH2. There isn't a lot of data since I'm just trying Log.io. Everything works perfectly in the client interface, except ONE log file on S2. When I check this log file, I see that I checked it ([Sun Sep 30 2012 10:23:38] INFO: Enabling log file: stream_sc_serv) but immediately after the S2 representative pannel with the list of log files on the left disappear and reappear with everything unchecked and colors changed.
If I don't check it, I see the little dot flashing (I have no more than 2 messages per second in this log file) indicating that there are new messages in this log file (when there are), but as soon as I check it to display the messages in a "Stream", it reloads the section attached to that harvester LH2 on S2, unchecking everything and not allowing me to see any message of course.
The other log files for the save server are working as expected.
Here are some example log lines from that log file (labelled stream_sc_serv in the harvester) making the harvester to reconnect:
And here are the log lines of the harvester responsible to harvest this stream_sc_serv file (and others):
@Coopeh commented on GitHub (Jan 22, 2013):
Just to throw my hat in, I'm seeing the exact same problem today. Was fine when I first installed it all yesterday.
@msmathers commented on GitHub (Feb 21, 2013):
v0.3.0 has a completely rewritten harvester/server/client stack, so this should no longer apply. Feel free to reopen if it continues to happen in v0.3.0.