# Logstash processing twice then 'block\_in\_start\_workers'

**URL:** <https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080>\
**Category:** Logstash\
**Created:** [January 22, 2020, 2:46pm UTC](https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080 "2020-01-22T14:46:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![guctum](https://avatars.discourse-cdn.com/v4/letter/g/ec9cab/32.png) [@guctum](https://discuss.elastic.co/u/guctum)\
**Post date:** [January 22, 2020, 2:46pm UTC](https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080/1 "2020-01-22T14:46:28Z")

</div>

Using Logstash to get information from Oracle Enterprise Manager, keep getting an error relating to multi\_recieve with 'block in start\_workers' repeating over and over whenever Logstash tries again. I have the below conf file that queries every 2 minutes, I'm exporting this data to Grafana and can see that it runs twice and then I just see the block. Is it something with my query that's resulting in this? Do I need a different way of running Logstash? I'm running it on Windows via bash terminal, command "./logstash -f oem.conf". Thanks for any info that can be given.

Here is my conf file:

```auto
    input {
        jdbc {
                jdbc_validate_connection => true
                jdbc_connection_string => "connection"
                jdbc_user => "username"
                jdbc_password => "password"
                jdbc_driver_class => ""
                statement => "SELECT * FROM V$ACTIVE_SESSION_HISTORY"
                schedule => "*/2 * * * *"
        }
}
filter
{
        if [@timestamp] {
                mutate {
                        add_field => { "logstash_timestamp" => "%{@timestamp}" }
                }
        }
        mutate { remove_field => ["force_matching_signature"] }
        mutate { convert => ["sample_time" , "string"] }
        date { match => ["sample_time" , "ISO8601"] }
}
output {
        elasticsearch { hosts => ["localhost:9200"] }
        # stdout { codec => rubydebug }
}

```

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [January 22, 2020, 11:28pm UTC](https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080/2 "2020-01-22T23:28:29Z")

</div>

Can you paste the actual error message (and possibly the surrounding messages)?

---

<div class="post-metadata">

**Author:** ![guctum](https://avatars.discourse-cdn.com/v4/letter/g/ec9cab/32.png) [@guctum](https://discuss.elastic.co/u/guctum)\
**Post date:** [January 23, 2020, 1:58pm UTC](https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080/3 "2020-01-23T13:58:33Z")

</div>

[2020-01-23T08:54:56,318][ERROR][logstash.outputs.elasticsearch][main] An unknown error occurred sending a bulk request to Elasticsearch. We will retry indefinitely {:error\_message=\>""\xE5" from ASCII-8BIT to UTF-8", :error\_class=\>"LogStash::Json::GeneratorError", :backtrace=\>["C:/Users/aiuhmb3/bin/logstash-7.5.1/logstash-core/lib/logstash/json.rb:27:in `jruby_dump'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/http_client.rb:119:in `block in bulk'", "org/jruby/RubyArray.java:2584:in `map'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/http_client.rb:119:in `block in bulk'", "org/jruby/RubyArray.java:1800:in `each'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/http_client.rb:117:in `bulk'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/common.rb:302:in `safe_bulk'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/common.rb:205:in `submit'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/common.rb:173:in `retrying_submit'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.2.3-java/lib/logstash/outputs/elasticsearch/common.rb:38:in `multi\_receive'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:118:in `multi_receive'", "org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:101:in `multi\_receive'", "C:/Users/aiuhmb3/bin/logstash-7.5.1/logstash-core/lib/logstash/java\_pipeline.rb:251:in `block in start\_workers'"]}

So based on this, I actually think it's something that I configured with Elasticsearch. I know this originated as a Logstash post, but is there anything I can do to my Elasticsearch index to have it handling my database query? My index is properly mapped, my Kibana and Grafana instances show documents in the index.

---

<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:** [February 20, 2020, 1:58pm UTC](https://discuss.elastic.co/t/logstash-processing-twice-then-block-in-start-workers/216080/4 "2020-02-20T13:58:39Z")

</div>

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