# APM 7.4 error with default pipeline \[apm\] **URL:** \ **Category:** APM\ **Tags:** java, server\ **Created:** [October 2, 2019, 2:33pm UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976 "2019-10-02T14:33:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [October 2, 2019, 2:33pm UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/1 "2019-10-02T14:33:13Z")
Today I have upgraded full stack to 7.4 in my test environment. I have also the APM server component installed. When I start it, all the documents are indexed for several minutes than it starts to log this error: `2019-10-02T16:29:11.633+0200 DEBUG [elasticsearch] elasticsearch/client.go:541 Bulk item insert failed (i=0, status=500): {"type":"exception","reason":"java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: '10.10.10.123:51122' is not an IP string literal.","caused_by":{"type":"illegal_argument_exception","reason":"java.lang.IllegalArgumentException: '10.10.10.123:51122' is not an IP string literal.","caused_by":{"type":"illegal_argument_exception","reason":"'10.10.10.123:51122' is not an IP string literal."}},"header":{"processor_type":"geoip"}}` furthermore, into Elasticsearch logs I'm facing this error: ``` [2019-10-02T16:31:29,629][DEBUG][o.e.a.b.TransportBulkAction] [saelklab1.crifnet.com] failed to execute pipeline [apm] for document [apm-7.4.0-transaction/_doc/null] org.elasticsearch.ElasticsearchException: java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: '10.10.10.123:51122' is not an IP string literal. ``` Elastic's log should be relevant since it is indicating [apm] pipeline currently configured in this way: ``` { "apm" : { "description" : "Default enrichment for APM events", "processors" : [ { "pipeline" : { "name" : "apm_user_agent" } }, { "pipeline" : { "name" : "apm_user_geo" } } ] } } ``` where apm\_user\_agent is ``` "apm_user_agent" : { "description" : "Add user agent information for APM events", "processors" : [ { "user_agent" : { "field" : "user_agent.original", "target_field" : "user_agent", "ignore_missing" : true } } ] } } ``` and apm\_user\_geo is: ``` { "apm_user_geo" : { "description" : "Add user geo information for APM events", "processors" : [ { "geoip" : { "database_file" : "GeoLite2-City.mmdb", "field" : "client.ip", "target_field" : "client.geo", "ignore_missing" : true } } ] } ``` another interesting behavior: if I restart the apm-server, it will index docs again when it will be started up but after several mins it will stop again. my apm-client are are composed by java apm client. ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [October 2, 2019, 6:53pm UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/2 "2019-10-02T18:53:49Z")
Hi @rschirin, for a quick fix you can disable the pipelines in the [apm-server.yml](https://github.com/elastic/apm-server/blob/master/apm-server.yml#L403). What happens is that the GeoIp and the UserAgent pipelines are enabled now by default on incoming data, but it looks like some of the data are not in the right format. We have to look into how this can happen. ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [October 3, 2019, 7:30am UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/3 "2019-10-03T07:30:12Z")
hi @simitt, I cannot understand. in my apm-server.yml file I have not configured any pipeline (to be exact, pipeline block is commented). furthermore, I have deleted with DELETE method pipelines indicated into the first post. edit: with Elastic stack 7.4 and APM-Server 7.2 there is no issue. to be honest, I don't like to have different versions ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [October 3, 2019, 2:18pm UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/4 "2019-10-03T14:18:27Z")
You actually don't need to enable the processors, as from `7.3` on the _apm_ pipeline is enabled by default, applying the GeoIP and UserAgent processors to apm data. If you want to disable that you can set `pipeline: "_none"` in the `apm-server.yml`. I created an [issue](https://github.com/elastic/apm-server/issues/2765) in the APM Server repo to ensure only information that can be processed by the default pipelines is indexed in the `client.ip` field. ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [October 3, 2019, 2:43pm UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/5 "2019-10-03T14:43:00Z")
ok, so this should be a bug for apm v7.4? I will try to disable explicitly the pipeline values in apm-server.yml. thanks in advance! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 24, 2019, 10:43am UTC](https://discuss.elastic.co/t/apm-7-4-error-with-default-pipeline-apm/201976/6 "2019-10-24T10:43:00Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.