# APM upgrade 6.5.0 to 6.5.1 **URL:** \ **Category:** APM\ **Created:** [November 23, 2018, 10:17am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985 "2018-11-23T10:17:49Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 23, 2018, 10:17am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/1 "2018-11-23T10:17:50Z")
just got the error after yum upgrade | 2018-11-23T11:13:35.493+0100 | ERROR | pipeline/output.go:100 | Failed to connect to backoff(elasticsearch([https://xxxxxxxxxx:9200/var/log/apm-server](https://xxxxxxxxxx:9200/var/log/apm-server))): 404 Not Found: {"error":{"root\_cause":[{"type":"index\_not\_found\_exception","reason":"no such index","resource.type":"index\_expression","resource.id":"var","index\_uuid":"_na_","index":"var"}],"type":"index\_not\_found\_exception","reason":"no such index","resource.type":"index\_expression","resource.id":"var","index\_uuid":"_na_","index":"var"},"status":404} | | --- | --- | --- | --- | | 2018-11-23T11:13:35.493+0100 | INFO | pipeline/output.go:93 | Attempting to reconnect to backoff(elasticsearch([https://xxxxxxxxxxxxxxx:9200/var/log/apm-server](https://xxxxxxxxxxxxxxx:9200/var/log/apm-server))) with 12 reconnect attempt(s) | i made no other changes, all cluster has been updated before without any errors ---
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 23, 2018, 10:31am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/2 "2018-11-23T10:31:30Z")
monitoring is ok but the message of connection stay ---
**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:** [November 23, 2018, 11:34am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/3 "2018-11-23T11:34:25Z")
> monitoring is ok but the message of connection stay I am not sure what you mean by _monitoring is ok_. Please check that you haven't turned off [automatic index creation](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html#index-creation). ---
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 23, 2018, 11:38am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/4 "2018-11-23T11:38:53Z")
i mean in the section monitoring of the apm i see it running, no automatic index creation disabled ---
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 23, 2018, 11:39am UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/5 "2018-11-23T11:39:34Z")
it works well in 6.5.0 , just made a yum upgrade and restart ---
**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:** [November 23, 2018, 12:22pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/6 "2018-11-23T12:22:15Z")
Which version of Elasticsearch are you using? Are you using default settings for the server and default user and role settings? I cannot reproduce the issue with Elasticsearch version 6.5.1 and default settings. ---
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 23, 2018, 2:28pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/7 "2018-11-23T14:28:26Z")
6.5.1 elastic, kibana, apm, logstash. Now i put elastic as user for elastic output and monitoring and it's the same error with the var index ---
**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:** [November 27, 2018, 1:11pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/8 "2018-11-27T13:11:16Z")
Do you have access to the elasticsearch logs and could you please check if you see any errors there? ---
**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:** [November 27, 2018, 1:12pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/9 "2018-11-27T13:12:38Z")
How does your setup look like? Do you have logstash configured as output from the APM Server, which then writes to Elasticsearch? ---
**Author:** ![Lo\_Tel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lo_tel/32/37913_2.png) [@Lo\_Tel](https://discuss.elastic.co/u/Lo_Tel)\ **Post date:** [November 27, 2018, 1:28pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/10 "2018-11-27T13:28:16Z")
Tx Sylvia, i have open a call on support and we find the solution. It was logfile enabled commented when line of path was not commented. ---
**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:** [November 27, 2018, 2:50pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/11 "2018-11-27T14:50:16Z")
Glad to hear you figured it out, I am closing this thread then. ---
**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:** [November 27, 2018, 2:50pm UTC](https://discuss.elastic.co/t/apm-upgrade-6-5-0-to-6-5-1/157985/12 "2018-11-27T14:50:57Z")