# :error=\>#\<ArgumentError: Setting "" hasn't been registered\> from logstash v5.5.0

**URL:** https://discuss.elastic.co/t/error-argumenterror-setting-hasnt-been-registered-from-logstash-v5-5-0/132990
**Category:** Logstash
**Created:** [May 23, 2018, 12:26pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-hasnt-been-registered-from-logstash-v5-5-0/132990 "2018-05-23T12:26:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![gayathri](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@gayathri](https://discuss.elastic.co/u/gayathri)
#### Post date: [May 23, 2018, 12:26pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-hasnt-been-registered-from-logstash-v5-5-0/132990/1 "2018-05-23T12:26:18Z")

</div>

Hi Team,

We are getting below error while starting logstash 5.5.0 from bin:

[2018-05-23T05:09:47,737][FATAL][logstash.runner] An unexpected error occurred! {:error=\>#\<ArgumentError: Setting "" hasn't been registered\>, :backtrace=\>["/opt/logstash-5.5.0/logstash-core/lib/logstash/settings.rb:32:in `get_setting'", "/opt/logstash-5.5.0/logstash-core/lib/logstash/settings.rb:64:in`set\_value'", "/opt/logstash-5.5.0/logstash-core/lib/logstash/settings.rb:83:in `merge'", "org/jruby/RubyHash.java:1342:in`each'", "/opt/logstash-5.5.0/logstash-core/lib/logstash/settings.rb:83:in `merge'", "/opt/logstash-5.5.0/logstash-core/lib/logstash/settings.rb:135:in`validate\_all'", "/opt/logstash-5.5.0/logstash-core/lib/logstash/runner.rb:244:in `execute'",

PFB, logstash configuration of the same:

input {  
redis{  
host =\> "localhost"  
data\_type =\> "list"  
codec =\> "json"  
}  
}

}  
output{  
elasticsearch{  
hosts =\> ["elastic\_server:9200"]  
index =\> "logstash-%{+YYYY.MM.dd}"  
}  
}

Regards,  
Gayathri T R

---

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [May 23, 2018, 1:27pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-hasnt-been-registered-from-logstash-v5-5-0/132990/2 "2018-05-23T13:27:48Z")

</div>

Look very closely at your logstash.yml. "Setting hasn't been registered" means there is a line in the yml that has a name that no code has registered to process. If you add a line at the top of the yml that says " foo : bar" you would expect to get 'ArgumentError: Setting "foo" hasn't been registered'. I cannot think how you could get Setting "", but that's where I would start looking.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 20, 2018, 1:27pm UTC](https://discuss.elastic.co/t/error-argumenterror-setting-hasnt-been-registered-from-logstash-v5-5-0/132990/3 "2018-06-20T13:27:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.