-
Notifications
You must be signed in to change notification settings - Fork 17
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
Whoa we shouldn't get this frame #1
Comments
logstash-plugins/logstash-input-lumberjack#8 As soon as the PR is rebased and the CLA signed I'll merge it. |
That's unrelated. I'm talking about lumberjack/client.rb , not about logstash input plugin. |
Sorry read too fast, yes this is the right place. |
I am trying to ship filtered logs from one logstash to another using lumberjack output plugin. I got similar error. Appreciate if any inputs on how to fix it ? Client write error, trying connect {:e=>#<RuntimeError: Whoa we shouldn't get this frame: >, :backtrace=>["/opt/logstash/logstash/vendor/bundle/jruby/1.9/gems/jls-lumberjack-0.0.26/lib/lumberjack/client.rb:146:in `ack'", "/opt/logstash/logstash/vendor/bundle/jruby/1.9/gems/jls-lumberjack-0.0.26/lib/lumberjack/client.rb:13 |
That error does not seem similar to me. Can you open another ticket? On Wednesday, September 7, 2016, aadicodes [email protected] wrote:
|
seeing this as well connecting to golang servers |
Deleted previous replies, had the wrong tab open, will check what lib it's using at the other end. |
Guys, is this right repo to log issues against lumberjack ruby client? Great!
Here's a test case:
Ideas on fixing this are welcome. Ideally, there should be a notification that server is gone and either auto-reconnection code added or just an exception thrown to user that connection is dead.
The text was updated successfully, but these errors were encountered: