{"action":"closed","issue":{"url":"https://api.github.com/repos/driskell/log-courier/issues/200","labels_url":"https://api.github.com/repos/driskell/log-courier/issues/200/labels{/name}","comments_url":"https://api.github.com/repos/driskell/log-courier/issues/200/comments","events_url":"https://api.github.com/repos/driskell/log-courier/issues/200/events","html_url":"https://github.com/driskell/log-courier/issues/200","id":93190360,"number":200,"title":"logstash log-courier plugin output not working properly","user":{"login":"dsolsona","id":876945,"avatar_url":"https://avatars.githubusercontent.com/u/876945?v=3","gravatar_id":"","url":"https://api.github.com/users/dsolsona","html_url":"https://github.com/dsolsona","followers_url":"https://api.github.com/users/dsolsona/followers","following_url":"https://api.github.com/users/dsolsona/following{/other_user}","gists_url":"https://api.github.com/users/dsolsona/gists{/gist_id}","starred_url":"https://api.github.com/users/dsolsona/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsolsona/subscriptions","organizations_url":"https://api.github.com/users/dsolsona/orgs","repos_url":"https://api.github.com/users/dsolsona/repos","events_url":"https://api.github.com/users/dsolsona/events{/privacy}","received_events_url":"https://api.github.com/users/dsolsona/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/driskell/log-courier/labels/awaiting%20feedback","name":"awaiting feedback","color":"fad8c7"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-06T05:11:17Z","updated_at":"2015-10-20T08:29:16Z","closed_at":"2015-10-20T08:29:16Z","body":"Hi Jason,\r\n\r\nI'm back on trying to migrate my lumberjack logstash output configuration to log-courier.\r\n\r\nI'm running logstash 1.4 on the logstash server where I have the log-courier output configured, and logsatsh 1.5 on the server where I have log-courier input.\r\n\r\nI'm frequently seeing these errors in the logs\r\n\r\n```\r\n{:timestamp=>\"2015-07-06T04:55:50.311000+0000\", :hint=>\"Unknown error, connection aborted\", :peer=>\"aa.bb.cc.dd:54255\", :level=>:warn, :message=>\"Unexpected end-of-input: expected close marker for OBJECT (from [Source: [B@3acde403; line: 1, column: 0])\\n at [Source: [B@3acde403; line: 1, column: 2177]\", :exception=>JrJackson::ParseError, :backtrace=>[\"com/jrjackson/JrJacksonRaw.java:75:in `parse_raw'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/jrjackson-0.2.9/lib/jrjackson/jrjackson.rb:23:in `load'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/multi_json-1.11.1/lib/multi_json/adapters/jr_jackson.rb:11:in `load'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:176:in `process_jdat'\", \"org/jruby/RubyKernel.java:1511:in `loop'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:147:in `process_jdat'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:76:in `run'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:256:in `run'\", \"org/jruby/RubyKernel.java:1511:in `loop'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:232:in `run'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:203:in `run_thread'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:167:in `run'\"]}\r\n\r\n\r\n{:timestamp=>\"2015-07-06T04:55:56.359000+0000\", :hint=>\"Unknown error, connection aborted\", :peer=>\"aa.bb.cc.dd:54256\", :level=>:warn, :message=>\"Unexpected end-of-input: expected close marker for OBJECT (from [Source: [B@2dc269a9; line: 1, column: 0])\\n at [Source: [B@2dc269a9; line: 1, column: 2177]\", :exception=>JrJackson::ParseError, :backtrace=>[\"com/jrjackson/JrJacksonRaw.java:75:in `parse_raw'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/jrjackson-0.2.9/lib/jrjackson/jrjackson.rb:23:in `load'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/multi_json-1.11.1/lib/multi_json/adapters/jr_jackson.rb:11:in `load'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:176:in `process_jdat'\", \"org/jruby/RubyKernel.java:1511:in `loop'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:147:in `process_jdat'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server.rb:76:in `run'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:256:in `run'\", \"org/jruby/RubyKernel.java:1511:in `loop'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:232:in `run'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:203:in `run_thread'\", \"/opt/logstash/vendor/bundle/jruby/1.9/gems/log-courier-1.7/lib/log-courier/server_tcp.rb:167:in `run'\"]}\r\n```\r\n\r\nI can see that some log events are making it's way through both logstash servers."}}