Hi Pedro,
whatever your logstash is reading, it's not valid JSON in this case
("unexpected token at 'Uncaught exception! HTTP 500 Internal Server
Error'").
Unfortunately it's kind of hard to find out what's wrong without any
further information about your setup, the logstash configuration, and the
Graylog configuration.
Cheers,
Jochen
On Thursday, 29 January 2015 13:31:41 UTC+1, Pedro Joro wrote:
>
> Hallo.
>
> I'm new in graylog2 and stuck in a problem and in need of advice/help.
>
> I've got two graylog2 nodes where one acts as master and the second as
> slave and each node has one logstash.
> For some reason the slaves logstash doesn't work.
>
> Here's the error message of the slaves logstash:
>
> *{:timestamp=>"2015-01-29T13:29:09.954000+0200", :message=>"Exception in
> filterworker", "exception"=>#<JSON::ParserError: unexpected token at
> 'Uncaught exception!HTTP 500 Internal Server Error'>,
> "backtrace"=>["json/ext/Parser.java:251:in `parse'",
> "/opt/logstash/current/vendor/bundle/jruby/1.9/gems/json-1.8.1-java/lib/json/common.rb:155:in
>
> `parse'", "(ruby filter code):18:in `register'",
> "org/jruby/RubyProc.java:271:in `call'",
> "/opt/logstash/current/lib/logstash/filters/ruby.rb:38:in `filter'",
> "(eval):81:in `initialize'", "org/jruby/RubyProc.java:271:in `call'",
> "/opt/logstash/current/lib/logstash/pipeline.rb:262:in `filter'",
> "/opt/logstash/current/lib/logstash/pipeline.rb:203:in `filterworker'",
> "/opt/logstash/current/lib/logstash/pipeline.rb:143:in `start_filters'"],
> :level=>:error}*
>
> Has anybody encountered the same problem?
>
> Please, can somebody unstuck me?
>
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
