# Ip2location i/o timeout

**URL:** <https://discuss.elastic.co/t/ip2location-i-o-timeout/125203>\
**Category:** Logstash\
**Created:** [March 22, 2018, 1:45pm UTC](https://discuss.elastic.co/t/ip2location-i-o-timeout/125203 "2018-03-22T13:45:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vitich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitich/32/65611_2.png) [@vitich](https://discuss.elastic.co/u/vitich)\
**Post date:** [March 22, 2018, 1:45pm UTC](https://discuss.elastic.co/t/ip2location-i-o-timeout/125203/1 "2018-03-22T13:45:27Z")

</div>

Hi!  
Usually I use standard geoip, but have decided to test ip2location for comparison.  
When I add ip2location, my ELK server doesn't receive the log from heavy load nginx server.  
Less loaded servers continue to transfer the log  
When I remove this plugin - everything is OK  
Filebeat log:  
ERR Failed to publish events (host: 10.10.10.17:5044:10200), caused by: read tcp 10.2.2.6:10911-\>10.120.12.117:5044: i/o timeout  
2018-03-22T13:26:49Z INFO Error publishing events (retrying): read tcp 10.2.2.6:10911-\>10.10.10.17:5044: i/o timeout

> <https://github.com/ip2location/logstash-filter-ip2location/issues/3>

---

<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:** [April 19, 2018, 1:45pm UTC](https://discuss.elastic.co/t/ip2location-i-o-timeout/125203/2 "2018-04-19T13:45:31Z")

</div>

Closed on April 19, 2018, 1:45pm UTC

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