-
Notifications
You must be signed in to change notification settings - Fork 25
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
Improve "Whoa we shouldn't get this frame" message #22
Comments
The frame type is included. https://github.com/elastic/ruby-lumberjack/blob/master/lib/lumberjack/client.rb#L146 The unmentioned reporting case for this is the user was reporting this error message (excuse any typos, I am transcribing from a screenshot):
In this case, it looks like the My belief in this is based on the exception text:
And the exception message code:
As you can see in the RuntimeError, the text ends |
Any further progress on this issue ? I am facing the same error while trying to ship log from one logstash to another using lumberjack output plugin. |
Same issue here. Logstash 5.6.2 sending to another logstash through lumberjack
|
This error can happen when an incorrect frame is send back from the server and its confusing and hard to debug. I suggest that we at least include the
frame_type
that we received to get a better ideas of what actually happened.Just a note the only frame that the server can send is
A
so I dont know what actually is happenning here. Probably something bad was raised on the server side?The text was updated successfully, but these errors were encountered: