# Crash logstash after updating from 5.3 to 5.5 **URL:** \ **Category:** Logstash\ **Created:** [July 7, 2017, 12:16pm UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262 "2017-07-07T12:16:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![b2ron](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@b2ron](https://discuss.elastic.co/u/b2ron)\ **Post date:** [July 7, 2017, 12:16pm UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/1 "2017-07-07T12:16:03Z")
I have CentOS release 6.9 logstash 5.3.3-1 java version "1.8.0\_92" I'm trying to update to logstash 5.5. After the update, the logstash does not start, and in the logs [2017-07-07T12:02:47,540][FATAL][logstash.runner] An unexpected error occurred! {:error=\>#\>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/inspector.rb:163:in`merge\_custom\_defaults!'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome\_print-1.8.0/lib/awesome\_print/inspector.rb:50:in `initialize'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/core_ext/kernel.rb:9:in`ai'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.3/lib/logstash/codecs/rubydebug.rb:39:in `encode_default'", "org/jruby/RubyMethod.java:120:in`call'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.3/lib/logstash/codecs/rubydebug.rb:35:in `encode'", "/usr/share/logstash/logstash-core/lib/logstash/codecs/base.rb:50:in`multi\_encode'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/codecs/base.rb:50:in`multi\_encode'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:90:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/single.rb:15:in`multi\_receive'", "org/jruby/ext/thread/Mutex.java:149:in `synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:47:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:420:in`output\_batch'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:419:in`output\_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:365:in `worker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:330:in`start\_workers'"]} I would be grateful for the help. Thanks ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 10, 2017, 6:49am UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/2 "2017-07-10T06:49:59Z")
What's your config look like? ---
**Author:** ![ericrdgz](https://avatars.discourse-cdn.com/v4/letter/e/dc4da7/32.png) [@ericrdgz](https://discuss.elastic.co/u/ericrdgz)\ **Post date:** [July 11, 2017, 5:07am UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/3 "2017-07-11T05:07:04Z")
I too am having this issue. OS: Amazon Linux 2017.03 Logstash: 5.5.0-1 JDK: 1.8.0\_131 **Error Trace:** `[2017-07-11T04:54:26,314][FATAL][logstash.runner] An unexpected error occurred! {:error=>#, :backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome\_print-1.8.0/lib/awesome\_print/inspector.rb:163:in `merge_custom_defaults!'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome_print-1.8.0/lib/awesome_print/inspector.rb:50:in`initialize'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/awesome\_print-1.8.0/lib/awesome\_print/core\_ext/kernel.rb:9:in `ai'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.3/lib/logstash/codecs/rubydebug.rb:39:in`encode\_default'", "org/jruby/RubyMethod.java:120:in `call'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-rubydebug-3.0.3/lib/logstash/codecs/rubydebug.rb:35:in`encode'", "/usr/share/logstash/logstash-core/lib/logstash/codecs/base.rb:50:in `multi_encode'", "org/jruby/RubyArray.java:1613:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/codecs/base.rb:50:in `multi_encode'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:90:in`multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:15:in `multi_receive'", "org/jruby/ext/thread/Mutex.java:149:in`synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb:47:in`multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:420:in `output_batch'", "org/jruby/RubyHash.java:1342:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:419:in `output_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:365:in`worker\_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:330:in `start_workers'"]}` **1 and only config . in /etc/logstash/conf.d/** ``` input { file { path => "/shared/prod_elb_logs/**/*" type => "elb" start_position => "beginning" sincedb_path => "/shared/.prod_elb_logs_since.db" } } filter { if [type] == "elb" { grok { match => ["message", "%{TIMESTAMP_ISO8601:timestamp} %{NOTSPACE:loadbalancer} %{IP:client_ip}:%{NUMBER:client_port:int} %{IP:backend_ip}:%{NUMBER:backend_port:int} %{NUMBER:request_processing_time:float} %{NUMBER:backend_processing_time:float} %{NUMBER:response_processing_time:float} %{NUMBER:elb_status_code:int} %{NUMBER:backend_status_code:int} %{NUMBER:received_bytes:int} %{NUMBER:sent_bytes:int} %{QS:request}"] } date { match => ["timestamp", "ISO8601"] } } } output { elasticsearch { hosts => ["172.31.45.27:9200"] } stdout { codec => rubydebug } } ``` ---
**Author:** ![b2ron](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@b2ron](https://discuss.elastic.co/u/b2ron)\ **Post date:** [July 11, 2017, 10:37am UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/4 "2017-07-11T10:37:30Z")
Crashes if I apply such a filter ``` filter { if [type] == "postfix-events" { grok { patterns_dir => ["/etc/logstash/patterns.d"] match => { "message" => ["%{PF}"] } } date { match => ["timestamp", "MMM dd HH:mm:ss"] } } # monitor metrics and health of logstash metrics { meter => ["events"] add_tag => "metric" } } ``` and I have fields with dots. But in version 5.3, this did not cause a crash. ---
**Author:** ![dawncold](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dawncold/32/20026_2.png) [@dawncold](https://discuss.elastic.co/u/dawncold)\ **Post date:** [July 13, 2017, 8:05am UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/5 "2017-07-13T08:05:25Z")
you'd better comment out `stdout { codec => rubydebug }` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2017, 8:05am UTC](https://discuss.elastic.co/t/crash-logstash-after-updating-from-5-3-to-5-5/92262/6 "2017-08-10T08:05:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.