# geoIP failure

**URL:** <https://discuss.elastic.co/t/geoip-failure/102487>\
**Category:** Logstash\
**Created:** [October 2, 2017, 8:36pm UTC](https://discuss.elastic.co/t/geoip-failure/102487 "2017-10-02T20:36:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jose\_Campos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jose_campos/32/11259_2.png) [@Jose\_Campos](https://discuss.elastic.co/u/Jose_Campos)\
**Post date:** [October 2, 2017, 8:36pm UTC](https://discuss.elastic.co/t/geoip-failure/102487/1 "2017-10-02T20:36:46Z")

</div>

Hello

A few days ago, I updated my elastic cloud to version 5.5.3, and started to give me this error.

"error" =\> {"type" =\> "mapper\_parsing\_exception", "reason" =\> "failed to parse", "caused\_by" =\> {"type" =\> "illegal\_argument\_exception", "reason" =\> "object field starting or ending with a [.] makes object resolution ambiguous: "}}}},: level =\>: warn}

But to elastic 5.0 if I loaded the information correctly.

This I think has to do with the field of IP's, and geoip

This is my logstash.

![image](https://us1.discourse-cdn.com/elastic/original/3X/8/8/888bc82a88d16b62843b0540dcfd6c389ff81bb4.png)

I'm running with logstash 2.0

Regards

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 6, 2017, 7:07am UTC](https://discuss.elastic.co/t/geoip-failure/102487/2 "2017-10-06T07:07:09Z")

</div>

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them 🙂

---

<div class="post-metadata">

**Author:** ![Jose\_Campos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jose_campos/32/11259_2.png) [@Jose\_Campos](https://discuss.elastic.co/u/Jose_Campos)\
**Post date:** [October 10, 2017, 3:06pm UTC](https://discuss.elastic.co/t/geoip-failure/102487/3 "2017-10-10T15:06:10Z")

</div>

Hi there

The issue continues, I was analyzing about the issue and the field geo.location was indexed as number not as geo\_point. This way I have no problem when mapping my public IP's. When I update the template to change geo.location from number to geo\_point, it works, but my public IP's doesn't map.

And shows me the same error "mapper\_parsing\_exception"

Regards

---

<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:** [November 7, 2017, 3:06pm UTC](https://discuss.elastic.co/t/geoip-failure/102487/4 "2017-11-07T15:06:31Z")

</div>

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