Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If Logentries connection fails, unbounded memory growth occurs, causing potential crash and loss of logs #1

markstos opened this issue Jun 18, 2015 · 3 comments


Copy link

@markstos markstos commented Jun 18, 2015

It appears that if the connection to Logentries fails, waiting logs are pushed on to an in-memory queue. When the connection starts working again, the queue is flushed.

However, I see no bound on the queue size. Eventually the memory growth of buffered logs could exhaust system memory and cause a crash, taking the buffered logs with it.

The issue could be addressed by putting a limit on the queue size, and making sure that buffered logs beyond the queue size are logged to STDERR as a backup option. This is generally approach that the official Logentries client]( takes.

Copy link

@No9 No9 commented Jun 18, 2015

@markstos thanks for such a clear report and your interest.

If we bump the dependency to le_node I think that would produce the effect you are looking for.
The internal lib is which now directs to le_node.

TBH this could do with a some house keeping anyway.

Copy link

@No9 No9 commented Jun 19, 2015

Updated here 22e15c7

The stream now emits errors which according to this documentation you can put to stderr as you suggested.

Copy link

@No9 No9 commented Jul 14, 2015

k I am going to close this off as the patch answers the original issue

@No9 No9 closed this Jul 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.