search

cityindex-attic / logsearch

[unmaintained] A development environment for ELK
Apache License 2.0
24 stars 8 forks source link

logstash terminates with error #193

Closed fandrei closed 9 years ago

fandrei commented 11 years ago

the windows-shipper-service.out.log file contains this message:

+---------------------------------------------------------+
| An unexpected error occurred. This is probably a bug.   |
| You can find help with this problem in a few places:    |
|                                                         |
| * chat: #logstash IRC channel on freenode irc.          |
|     IRC via the web: http://goo.gl/TI4Ro                |
| * email: logstash-users@googlegroups.com                |
| * bug system: https://logstash.jira.com/                |
|                                                         |
+---------------------------------------------------------+
The error reported is: 
  code converter not found (ASCII-8BIT to UTF-8)
fandrei commented 11 years ago

added to LogStash bugtracker: https://logstash.jira.com/browse/LOGSTASH-1411

fandrei commented 11 years ago

it seems upgrade to 1.2.1 solves this problem

fandrei commented 11 years ago

this issue still happens with logstash 1.2.1, though less frequently

dpb587 commented 11 years ago

Can you confirm that you're using the stock logstash-1.2.1 download from logstash.net, and not our custom build? Our custom build wouldn't fix it, but I want to ensure it's not something the custom build may be causing.

fandrei commented 11 years ago

it's official 1.2.1

fandrei commented 11 years ago

PS error message is different with version 1.2.1

Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (ConverterNotFoundError) code converter not found (ASCII-8BIT to UTF-8)
    at org.jruby.RubyString.encode(org/jruby/RubyString.java:7590)
    at json.ext.GeneratorMethods$RbHash.to_json(json/ext/GeneratorMethods.java:71)
    at LogStash::Event.to_json(file:/C:/temp/self-monitor/logstash.jar!/logstash/event.rb:169)
    at LogStash::Outputs::Redis.receive(file:/C:/temp/self-monitor/logstash.jar!/logstash/outputs/redis.rb:140)
    at RUBY.initialize((eval):183)
    at org.jruby.RubyProc.call(org/jruby/RubyProc.java:255)
    at LogStash::Pipeline.output(file:/C:/temp/self-monitor/logstash.jar!/logstash/pipeline.rb:247)
    at RUBY.outputworker(file:/C:/temp/self-monitor/logstash.jar!/logstash/pipeline.rb:212)
    at RUBY.start_outputs(file:/C:/temp/self-monitor/logstash.jar!/logstash/pipeline.rb:140)
mrdavidlaing commented 10 years ago

@fandrei,

I've been running a set of 4 live shippers: shipper-inx-api-internal shipper-inx-dmz shipper-rdb-api-internal shipper-rdb-dmz for the last 21 days, and a grep -r 'Exception in thread' * reveals that an Exception hasn't happened for me.

I'm running logstash-1.1.13-pr19b5(patched).

I propose that for now we leave all shippers running with our patched logstash-1.1.13-pr19b5(patched) build.

This will mean that we cannot have a self-monitor shipper; but, since this hasn't proven terribly useful, I think that is a fair compromise.

cityindex/logsearch-config#47 removes the self-monitor shipper

sopel commented 9 years ago

Closed as Incomplete due to project being retired to the CityIndex Attic.