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

seems to stop sending information randomly? #3

Open
ayhoung opened this issue Oct 5, 2015 · 7 comments
Open

seems to stop sending information randomly? #3

ayhoung opened this issue Oct 5, 2015 · 7 comments

Comments

@ayhoung
Copy link

ayhoung commented Oct 5, 2015

for some reason, the logstash forwarder works well when I first start it up, but silently gives up after a while?

@jwalton
Copy link
Contributor

jwalton commented Oct 5, 2015

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?

@ayhoung
Copy link
Author

ayhoung commented Oct 8, 2015

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

@SatyaKuppam
Copy link

Having the same problem. Is there a fix to this?

@jwalton
Copy link
Contributor

jwalton commented Feb 12, 2016

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.

@jwalton
Copy link
Contributor

jwalton commented Feb 12, 2016

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. :)

@ayhoung
Copy link
Author

ayhoung commented Feb 12, 2016

would love to see if I can have a skype session with you to show you.

@SatyaKuppam
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants