-
Notifications
You must be signed in to change notification settings - Fork 8
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
seems to stop sending information randomly? #3
Comments
I ran into this problem too, last week. I found this issue, and tried upgrading to logstash 1.5.4, and this seemed to fix things for me. What version are you running? |
logstash:all/stable 1:1.5.4-1 uptodate for me, im not sure if its my logstash. i tried checking the logs for errors but didn't get any |
Having the same problem. Is there a fix to this? |
It's definitely not a problem we're seeing - we use bunyan-lumberjack on a number of servers, and they're all happily sending data. There was a bug in an earlier version of lumberjack-protocol which caused it to throw an uncaught exception when messages were dropped, but this should be an extremely rare occurrence and has been fixed. |
If you have a recipe for reproducing this, though, I'd definitely be interested. We have a lot of production servers that rely on this, so if it's broken I want to know. :) |
would love to see if I can have a skype session with you to show you. |
For me the last log thats created by a node process before exiting with a code 0, was the one missing from the logs. But then again, it started working after a logstash reinstall. I am not sure both those might be connected, but flushing the streams might be the likely cause. |
for some reason, the logstash forwarder works well when I first start it up, but silently gives up after a while?
The text was updated successfully, but these errors were encountered: