# Expected \[START\_OBJECT\] but found \[VALUE\_STRING\]

**URL:** <https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883>\
**Category:** Logstash\
**Created:** [April 27, 2018, 8:08pm UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883 "2018-04-27T20:08:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 27, 2018, 8:08pm UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/1 "2018-04-27T20:08:16Z")

</div>

I followed [Elasticsearch input plugin | Logstash Reference](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-elasticsearch.html#_scheduling) to implement "Scheduling" of my pipeline:

```
# grep schedule pipeline.cfg 
                schedule => '0 * * * *'
# 

```

yet logstash produces errors such as this:

[logstash13 | { 2298 rufus-scheduler intercepted an error: logstash13 | 2298 - Pastebin.com](https://pastebin.com/m5EcaB9v)

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [April 27, 2018, 8:43pm UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/2 "2018-04-27T20:43:09Z")

</div>

Looks like a problem with the query.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 27, 2018, 8:56pm UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/3 "2018-04-27T20:56:35Z")

</div>

@magnusbaeck why do you think that is? `rufus-scheduler` is the one that producing error, besides before adding `schedule` query worked just fine, but I'll go ahead and double check it anyways.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [April 28, 2018, 9:14am UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/4 "2018-04-28T09:14:53Z")

</div>

> rufus-scheduler is the one that producing error

rufus-scheduler is the one _reporting_ the error. The error occurs in the elasticsearch input plugin.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [April 28, 2018, 11:55am UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/5 "2018-04-28T11:55:48Z")

</div>

I have multiple pipelines in logstash, and it looks like at least one of pipeline query was misconfigured and that's why rufus-scheduler was reporting an error, I was looking into wrong pipeline at first, but then I found issue in another)

Thanks!

---

<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:** [May 26, 2018, 11:56am UTC](https://discuss.elastic.co/t/expected-start-object-but-found-value-string/129883/6 "2018-05-26T11:56:03Z")

</div>

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