# Trouble "reconnecting" APM after upgrade to 6.6.0 **URL:** \ **Category:** APM\ **Created:** [February 8, 2019, 4:29pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667 "2019-02-08T16:29:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![bigdamhero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigdamhero/32/34478_2.png) [@bigdamhero](https://discuss.elastic.co/u/bigdamhero)\ **Post date:** [February 8, 2019, 4:29pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/1 "2019-02-08T16:29:14Z")
If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂 **Kibana version** : 6.6.0 **Elasticsearch version** : 6.6.0 **APM Server version** : 6.6.0 **APM Agent language and version** : **Browser version** : **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: **Fresh install or upgraded from other version?** upgrade from ver 6.5.4 **Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc. Install is on my TEST environment (lowest environment) No security single Elastic Node and APM on a separate machine. **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: service apm-server status shows : apm-server.service - Elastic APM Server Loaded: loaded (/lib/systemd/system/apm-server.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2019-02-08 09:41:35 CST; 44min ago Docs: [https://www.elastic.co/solutions/apm](https://www.elastic.co/solutions/apm) Main PID: 94215 (apm-server) Tasks: 10 Memory: 9.0M CPU: 609ms CGroup: /system.slice/apm-server.service └─94215 /usr/share/apm-server/bin/apm-server -c /etc/apm-server/apm-server.yml -path.home /usr/share/apm-server -path.config /etc/apm-server -path.data /var/lib/apm-server -path.logs / when I go into setup to check server status it must see the indexes from the past and says its connected but then it is not showing any new indexes. **Steps to reproduce** : 1. 2. 3. **Errors in browser console (if relevant)**: **Provide logs and/or server output (if relevant)**: I only saw a few things in the syslog and I cleaned up those issues but still no connection. Is there a different logging area? is there a way to turn up the logging to see more details? As always thank you for any assistance. ---
**Author:** ![bigdamhero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigdamhero/32/34478_2.png) [@bigdamhero](https://discuss.elastic.co/u/bigdamhero)\ **Post date:** [February 8, 2019, 5:04pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/2 "2019-02-08T17:04:39Z")
I found the settings for turning up logging levels. ``` 2019-02-08T11:00:50.838-0600 DEBUG [monitoring] elasticsearch/client.go:49 Monitoring client: connect. 2019-02-08T11:00:50.839-0600 DEBUG [elasticsearch] elasticsearch/client.go:739 GET https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled 2019-02-08T11:00:50.855-0600 DEBUG [monitoring] elasticsearch/elasticsearch.go:237 Monitoring could not connect to elasticsearch, failed with X-Pack capabilities query failed with: Get https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:00:52.851-0600 ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(https://dhpxtlmd4:9300)): Get https://dhpxtlmd4:9300: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:00:52.851-0600 INFO pipeline/output.go:93 Attempting to reconnect to backoff(elasticsearch(https://dhpxtlmd4:9300)) with 5 reconnect attempt(s) 2019-02-08T11:00:52.851-0600 DEBUG [elasticsearch] elasticsearch/client.go:697 ES Ping(url=https://dhpxtlmd4:9300) 2019-02-08T11:00:52.869-0600 DEBUG [elasticsearch] elasticsearch/client.go:701 Ping request failed with: Get https://dhpxtlmd4:9300: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:01:20.855-0600 DEBUG [monitoring] elasticsearch/client.go:49 Monitoring client: connect. 2019-02-08T11:01:20.856-0600 DEBUG [elasticsearch] elasticsearch/client.go:739 GET https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled 2019-02-08T11:01:20.868-0600 DEBUG [monitoring] elasticsearch/elasticsearch.go:237 Monitoring could not connect to elasticsearch, failed with X-Pack capabilities query failed with: Get https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:01:24.869-0600 ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(https://dhpxtlmd4:9300)): Get https://dhpxtlmd4:9300: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:01:24.869-0600 INFO pipeline/output.go:93 Attempting to reconnect to backoff(elasticsearch(https://dhpxtlmd4:9300)) with 6 reconnect attempt(s) 2019-02-08T11:01:24.869-0600 DEBUG [elasticsearch] elasticsearch/client.go:697 ES Ping(url=https://dhpxtlmd4:9300) 2019-02-08T11:01:24.882-0600 DEBUG [elasticsearch] elasticsearch/client.go:701 Ping request failed with: Get https://dhpxtlmd4:9300: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" 2019-02-08T11:01:50.868-0600 DEBUG [monitoring] elasticsearch/client.go:49 Monitoring client: connect. 2019-02-08T11:01:50.868-0600 DEBUG [elasticsearch] elasticsearch/client.go:739 GET https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled 2019-02-08T11:01:50.882-0600 DEBUG [monitoring] elasticsearch/elasticsearch.go:237 Monitoring could not connect to elasticsearch, failed with X-Pack capabilities query failed with: Get https://dhpxtlmd4:9300/_xpack?filter_path=features.monitoring.enabled: net/http: HTTP/1.x transport connection broken: malformed HTTP status code "is" ``` ---
**Author:** ![gil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gil/32/41911_2.png) [@gil](https://discuss.elastic.co/u/gil)\ **Post date:** [February 8, 2019, 5:08pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/3 "2019-02-08T17:08:12Z")
@bigdamhero This is suspicious as port 9300 is typically used by elastisearch for internal communication, while 9200 is the default for queries: ```auto 2019-02-08T11:00:52.851-0600 ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(https://dhpxtlmd4:9300)): Get https://dhpxtlmd4:9300: net/http: ``` Can you double check that configuration? ---
**Author:** ![bigdamhero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigdamhero/32/34478_2.png) [@bigdamhero](https://discuss.elastic.co/u/bigdamhero)\ **Post date:** [February 8, 2019, 5:11pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/4 "2019-02-08T17:11:30Z")
You are correct I was trying to see if that would throw a different error. Another question, I was pointing this to a coordinating node and I needed to change that to one of my master/data nodes. Does this sound correct? ---
**Author:** ![bigdamhero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigdamhero/32/34478_2.png) [@bigdamhero](https://discuss.elastic.co/u/bigdamhero)\ **Post date:** [February 8, 2019, 5:24pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/5 "2019-02-08T17:24:33Z")
I changed the port to :9200 and I change the FQDN of the server back to the host name and its showing up in monitoring now. Thank you !! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 1, 2019, 1:24pm UTC](https://discuss.elastic.co/t/trouble-reconnecting-apm-after-upgrade-to-6-6-0/167667/6 "2019-03-01T13:24:35Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.