[GH-ISSUE #56] log.io-harvester crashing #42

New issue

Closed

opened 2026-02-26 05:31:08 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @ydnitin on GitHub (Mar 4, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/56

Hi,
Thanks for all the work that you have put into this. I recently installed the server on a VM and the client is my app servers.

harvester crashes after a while with this error.
fs.js:1259
throw new Error('start must be <= end');
^
Error: start must be <= end
at new fs.ReadStream (fs.js:1259:13)
at Object.fs.createReadStream (fs.js:1218:10)
at LogStream._readNewLogs (/usr/local/lib/node_modules/log.io/lib/harvester.js:89:20)
at LogStream._watchFile (/usr/local/lib/node_modules/log.io/lib/harvester.js:79:19)
at Object.oncomplete (fs.js:297:15)

I am also getting " error: Invalid TCP message". The streams are all messed up, restarting server, harvester doesn't help.

Versions:
Node: 0.8.20
Installed via npm install.
exports.config = {
nodeName: "server1",
logStreams: {
app1: [ "/var/log/app1/current" ],
app2: [ "/var/log/app2/current" ]
},
server: {
host: '192.168.128.146',
port: 28777
}
}

Let me know if you need more info.

Originally created by @ydnitin on GitHub (Mar 4, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/56 Hi, Thanks for all the work that you have put into this. I recently installed the server on a VM and the client is my app servers. harvester crashes after a while with this error. fs.js:1259 throw new Error('start must be <= end'); ^ Error: start must be <= end at new fs.ReadStream (fs.js:1259:13) at Object.fs.createReadStream (fs.js:1218:10) at LogStream._readNewLogs (/usr/local/lib/node_modules/log.io/lib/harvester.js:89:20) at LogStream._watchFile (/usr/local/lib/node_modules/log.io/lib/harvester.js:79:19) at Object.oncomplete (fs.js:297:15) I am also getting " error: Invalid TCP message". The streams are all messed up, restarting server, harvester doesn't help. Versions: Node: 0.8.20 Installed via npm install. exports.config = { nodeName: "server1", logStreams: { app1: [ "/var/log/app1/current" ], app2: [ "/var/log/app2/current" ] }, server: { host: '192.168.128.146', port: 28777 } } Let me know if you need more info.

kerem closed this issue

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

kerem commented

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

Author

Owner

@msmathers commented on GitHub (Mar 4, 2013):

My guess is that this was caused by file truncation, which wasn't being checked for. Just pushed the patch to npm, give it a try now.

@msmathers commented on GitHub (Mar 4, 2013): My guess is that this was caused by file truncation, which wasn't being checked for. Just pushed the patch to npm, give it a try now.