### Author:  [@feijiangnan](https://discuss.elastic.co/u/feijiangnan)
#### Post date: [September 15, 2017, 3:32pm UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/4 "2017-09-15T15:32:37Z")
After removed x-pack, got infinite loop like below:
[2017-09-15T07:36:27,607][DEBUG][logstash.plugins.registry] Adding plugin to the registry {:name=\>"fb\_apache", :type=\>:modules, :class=\>#\}
[2017-09-15T07:36:27,608][INFO][logstash.modules.scaffold] Initializing module {:module\_name=\>"netflow", :directory=\>"/usr/share/logstash/modules/netflow/configuration"}
---
### Author:  [@PhaedrusTheGreek](https://discuss.elastic.co/u/PhaedrusTheGreek)
#### Post date: [September 22, 2017, 2:56pm UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/5 "2017-09-22T14:56:25Z")
This error is due to a security permissions problem with the user configured in the output. The error message displayed is obviously a mistake, and has been fixed in version 7.4.2 of the output plugin:
$ bin/logstash-plugin update logstash-output-elasticsearch
Updating logstash-output-elasticsearch
Updated logstash-output-elasticsearch 7.4.1 to 7.4.2
Now you should receive a sane error,
```auto
[2017-09-22T10:43:56,826][ERROR][logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backoff {:code=>403, :url=>"http://127.0.0.1:9200/_bulk"}
```
, which indicates that the user does not have permission to index data. In order to create a dedicated logstash write user, see [this guide](https://www.elastic.co/guide/en/x-pack/current/logstash.html#ls-http-auth-basic), or use the **elastic** superuser while testing.
---
### Author:  [@feijiangnan](https://discuss.elastic.co/u/feijiangnan)
#### Post date: [September 22, 2017, 7:05pm UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/6 "2017-09-22T19:05:31Z")
Thanks, I will try it and update you.
---
### Author:  [@Hush077](https://discuss.elastic.co/u/Hush077)
#### Post date: [September 25, 2017, 8:47pm UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/7 "2017-09-25T20:47:58Z")
I'm getting this error after a clean install of 5.6.1. I updated the plugins and now I'm getting the issue I posted about here. [Logstash 5.6.1 inifinite loop? Encountered a retryable error](https://discuss.elastic.co/t/logstash-5-6-1-inifinite-loop-encountered-a-retryable-error/101753/3)
@PhaedrusTheGreek any help would be appreciated.
---
### Author:  [@Nitin\_Yadav](https://discuss.elastic.co/u/Nitin_Yadav)
#### Post date: [October 11, 2017, 7:27am UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/8 "2017-10-11T07:27:38Z")
I could not find the solution but have a workaround for this. I have fresh installation of logstash 5.6.3 and using logstash-output-elasticsearch plugin version 9.0.0(upgraded from 7.4.2)
Error:
[2017-10-11T06:52:46,492][ERROR][logstash.outputs.elasticsearch] Encountered an unexpected error submitting a bulk request! Will retry. {:error\_message=\>"undefined method `sanitized' for \"/_bulk\":String", :cl ass=>"NoMethodError", :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-9.0.0-java/lib/logstash/outputs/elasticsearch/common.rb:250:in`safe\_bulk'", "/usr/share/logsta
sh/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-9.0.0-java/lib/logstash/outputs/elasticsearch/common.rb:113:in `submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elastics earch-9.0.0-java/lib/logstash/outputs/elasticsearch/common.rb:81:in`retrying\_submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-9.0.0-java/lib/logstash/outputs/elasticsea
rch/common.rb:33:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/shared.rb:13:in`multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegat
or.rb:49:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:434:in`output\_batch'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeli ne.rb:433:in`output\_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:381:in `worker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:342:in`start\_workers'"]}
This occurs during error handling and url sanitisation method in mentioned ruby file common.rb line 250:
Changed
log\_hash = {:code =\> e.response\_code, :url =\> e.url.sanitized.to\_s}
to
log\_hash = {:code =\> e.response\_code, :url =\> e.url, :body =\> e.response\_body }
Now that I am not sanitizing url, hence getting below appropriate message in logs:
[2017-10-11T07:14:25,097][ERROR][logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backoff {:code=\>404, :url=\>"/\_bulk", :body=\>"{"error":{"root\_cause":[{"type":"index\_not\_found\_exception","reason":"no such index and [action.auto\_create\_index] ([prod\*,.security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*]) doesn't match","index\_uuid":"_na_","index":"logstash-2017.10.11"}],"type":"index\_not\_found\_exception","reason":"no such index and [action.auto\_create\_index] ([prod\*,.security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*]) doesn't match","index\_uuid":"_na_","index":"logstash-2017.10.11"},"status":404}"}
This was the error due to configuration in elasticsearch.yml file which allowed only certain index pattern to be created automatically. Changed configuration in yml and finally index was created.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 8, 2017, 7:27am UTC](https://discuss.elastic.co/t/undefined-method-sanitized/100588/9 "2017-11-08T07:27:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.