# Logstash errors on filebeat received apache logs

**URL:** <https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808>\
**Category:** Logstash\
**Created:** [June 13, 2018, 11:39pm UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808 "2018-06-13T23:39:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ocabj](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@ocabj](https://discuss.elastic.co/u/ocabj)\
**Post date:** [June 13, 2018, 11:39pm UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/1 "2018-06-13T23:39:33Z")

</div>

After an upgrade from 6.2 to 6.3, I am now getting indexing errors for apache logs.

[2018-06-13T16:12:18,782][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"apache-2018.06.13", :\_type=\>"apache", :\_routing=\>nil}, #LogStash::Event:0x4db324f8], :response=\>{"index"=\>{"\_index"=\>"apache-2018.06.13", "\_type"=\>"apache", "\_id"=\>"tidr-2MB8IC994mx1\_US", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [host]", "caused\_by"=\>{"type"=\>"illegal\_state\_exception", "reason"=\>"Can't get text on a START\_OBJECT at 1:970"}}}}}  
[2018-06-13T16:12:18,790][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"apache\_error-2018.06.13", :\_type=\>"apache\_error", :\_routing=\>nil}, #LogStash::Event:0x74e641ce], :response=\>{"index"=\>{"\_index"=\>"apache\_error-2018.06.13", "\_type"=\>"apache\_error", "\_id"=\>"tydr-2MB8IC994mx1\_US", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [host]", "caused\_by"=\>{"type"=\>"illegal\_state\_exception", "reason"=\>"Can't get text on a START\_OBJECT at 1:175"}}}}}

Any ideas?

---

<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:** [June 14, 2018, 5:47am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/2 "2018-06-14T05:47:47Z")

</div>

What's the mapping of the `host` field? Use the ES get mapping API.

---

<div class="post-metadata">

**Author:** ![ocabj](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@ocabj](https://discuss.elastic.co/u/ocabj)\
**Post date:** [June 14, 2018, 6:20am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/3 "2018-06-14T06:20:59Z")

</div>

```
{
  "apache-2018.06.13": {
    "mappings": {
      "apache": {
        "host": {
          "full_name": "host",
          "mapping": {
            "host": {
              "type": "text",
              "fields": {
                "keyword": {
                  "type": "keyword",
                  "ignore_above": 256
                }
              }
            }
          }
        }
      }
    }
  }
}
```

---

<div class="post-metadata">

**Author:** ![nxhack](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nxhack/32/3939_2.png) [@nxhack](https://discuss.elastic.co/u/nxhack)\
**Post date:** [June 14, 2018, 6:32am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/4 "2018-06-14T06:32:53Z")

</div>

It may be related to this issuse.

[Metricbeat `host` namespace causes mapping conflict when used with Logstash](https://github.com/elastic/beats/issues/7050)

I installed the version of filebeat back to 6.2.4. it works fine.

---

<div class="post-metadata">

**Author:** ![nxhack](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nxhack/32/3939_2.png) [@nxhack](https://discuss.elastic.co/u/nxhack)\
**Post date:** [June 14, 2018, 8:35am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/5 "2018-06-14T08:35:56Z")

</div>

A few years ago there was also such discussion about LS, Beat compatibility.

[Copy beat.hostname into host](https://github.com/logstash-plugins/logstash-input-beats/issues/25)

---

<div class="post-metadata">

**Author:** ![ocabj](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@ocabj](https://discuss.elastic.co/u/ocabj)\
**Post date:** [June 14, 2018, 1:47pm UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/6 "2018-06-14T13:47:13Z")

</div>

I reverted to filebeat 6.2.4 and now the insertions are taking place without issue / as expected. I'm trying to understand the host field issue as described in the link you posted.

---

<div class="post-metadata">

**Author:** ![nxhack](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nxhack/32/3939_2.png) [@nxhack](https://discuss.elastic.co/u/nxhack)\
**Post date:** [June 15, 2018, 1:46am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/7 "2018-06-15T01:46:01Z")

</div>

Duplicate: [Logstash errors after upgrading to filebeat-6.3.0](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984)

---

<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:** [July 13, 2018, 1:46am UTC](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808/8 "2018-07-13T01:46:02Z")

</div>

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