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

Whoa we shouldn't get this frame #1

Open
celesteking opened this issue May 22, 2015 · 8 comments
Open

Whoa we shouldn't get this frame #1

celesteking opened this issue May 22, 2015 · 8 comments

Comments

@celesteking
Copy link

Guys, is this right repo to log issues against lumberjack ruby client? Great!

Here's a test case:

  1. send normally using client
  2. terminate logstash
  3. try to write some more data using client
  4. get the error:
RuntimeError: Whoa we shouldn't get this frame:  : /home/lst/lst/vendor/bundle/ruby/2.1.0/gems/jls-lumberjack-0.0.22/lib/lumberjack/client.rb:116:in `ack',
/home/lst/lst/vendor/bundle/ruby/2.1.0/gems/jls-lumberjack-0.0.22/lib/lumberjack/client.rb:109:in `write_hash',
/home/lst/lst/vendor/bundle/ruby/2.1.0/gems/jls-lumberjack-0.0.22/lib/lumberjack/client.rb:44:in `write'

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.

@ph
Copy link
Contributor

ph commented May 22, 2015

logstash-plugins/logstash-input-lumberjack#8

As soon as the PR is rebased and the CLA signed I'll merge it.

@celesteking
Copy link
Author

That's unrelated. I'm talking about lumberjack/client.rb , not about logstash input plugin.

@ph
Copy link
Contributor

ph commented May 22, 2015

Sorry read too fast, yes this is the right place.

@aadicodes
Copy link

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

@jordansissel
Copy link
Contributor

That error does not seem similar to me. Can you open another ticket?

On Wednesday, September 7, 2016, aadicodes [email protected] wrote:

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=>#, :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


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIC6kZDUoihX40X4gLfu_zsFqg82xboks5qnyODgaJpZM4ElHOD
.

@stevenh
Copy link

stevenh commented Dec 19, 2019

seeing this as well connecting to golang servers

@ph
Copy link
Contributor

ph commented Dec 19, 2019

@stevenh Which library are you using for the server part? our official one?

@stevenh
Copy link

stevenh commented Dec 20, 2019

Deleted previous replies, had the wrong tab open, will check what lib it's using at the other end.

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

No branches or pull requests

5 participants