Closed ieth0 closed 6 years ago
fixed in #12
i have same problem how can i fix it ?? i didn't understand the solution.
logstash version 7.2.1
Hi @salarnasiri
The issue is fixed in the latest version. You can run the following command to update the plugin,
logstash-plugin update logstash-filter-ip2location
Please make sure the version of logstash-filter-ip2location is updated to v2.0.2
no it's not.
if we have source like this [nginx][access][src]
the module stop working.
Hi @salarnasiri
Are you calling the correct field of the source ip? Perhaps, can you send the error message to support@ip2location.com for our investigation?
yes. I will fix it and send you a PR soon. please review and merge it.
Description: Using ip2location v1.1.0+, clientip != ip2location.ip_address. ip2location.ip_address is always the same after starting logstash
Steps to reproduce the issue: 1) First installed latest version of ip2location ( 2.0.1 ) on logstash 5.6 and faced the problem. ip2location.ip_address wouldn't change, and it was one repetitive ip. 2) changed use_memory_mapped to true, got some errors, didn't work. 3) upgraded logstash to 6.4.2 same problem. 4) checked the codes and found cache_size which I didn't find on documents. Increase/decrease it, same problem. 5) downgraded to 2.0.0 , same. downgraded to 1.1.0 same, and finally to 1.0.3 and it worked but with horrible performance ( with 5k messages per second ). scaled logstash to 5 instances to make it work.
Since cache is implemented on v1.1.0, I think something is wrong with cache.
Describe the results you received:
Describe the results you expect:
Config: Added:
and removed geoip block.
Versions: elasticsearch 5.6.10 logstash 5.6.10 and 6.4.2