# Pmm client forgets listen-port for external services after server update to PMM 2.19

**URL:** <https://forums.percona.com/t/pmm-client-forgets-listen-port-for-external-services-after-server-update-to-pmm-2-19/11296>\
**Category:** PMM 2.x\
**Created:** [July 13, 2021, 9:16am UTC](https://forums.percona.com/t/pmm-client-forgets-listen-port-for-external-services-after-server-update-to-pmm-2-19/11296 "2021-07-13T09:16:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rapli](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@rapli](https://forums.percona.com/u/rapli)\
**Post date:** [July 13, 2021, 9:16am UTC](https://forums.percona.com/t/pmm-client-forgets-listen-port-for-external-services-after-server-update-to-pmm-2-19/11296/1 "2021-07-13T09:16:18Z")

</div>

After upgrading from PMM 2.18 to PMM 2.19 all pmm-agent seems to forget the configured port for external services (note the “…127.0.0.1:0/metrics” - port should be 42009).

Example log entry:

> Jul 13 10:48:18 envi-test-rmq-1 pmm-agent[1465384]: INFO[2021-07-13T10:48:18.935+02:00] 2021-07-13T08:48:18.935Z error VictoriaMetrics/lib/promscrape/scrapework.go:231 error when scraping “[http://127.0.0.1:0/metrics](http://127.0.0.1:0/metrics)” from job “external-exporter\_agent\_id\_a856cbdb-4a4b-442b-b9af-62957ca2477b\_mr-10s” with labels {agent\_id=“/agent\_id/a856cbdb-4a4b-442b-b9af-62957ca2477b”,agent\_type=“external-exporter”,external\_group=“external”,instance=“/agent\_id/a856cbdb-4a4b-442b-b9af-62957ca2477b”,job=“external-exporter\_agent\_id\_a856cbdb-4a4b-442b-b9af-62957ca2477b\_mr-10s”,machine\_id=“/machine\_id/a69c5724b306422387bb1b08ee1f2edb”,node\_id=“/node\_id/f5dd0e77-405a-4bcf-a3c5-7e82652f954e”,node\_name=“envi-test-rmq-1”,node\_type=“generic”,service\_id=“/service\_id/ec7a45a9-025f-4075-876c-d116c0b6f394”,service\_name=“envi-test-rmq-1-systemd”,service\_type=“external”}: error when scraping “[http://127.0.0.1:0/metrics](http://127.0.0.1:0/metrics)”: dial tcp4 127.0.0.1:0: connect: connection refused; try -enableTCP6 command-line flag if you scrape ipv6 addresses agentID=/agent\_id/5c7d46da-b037-4cb9-8e75-02e37de04f1c component=agent-process type=vm\_agent

After removing the service and adding it again everything seems to work properly - until pmm-agent is being restarted. Then the same error occurs.

In this example the external service is added with

> pmm-admin add external --metrics-path=metrics --service-name=“envi-test-rmq-1-systemd” --listen-port=42009 --scheme=http --metrics-mode=auto

This issue occurs with different pmm-client versions - at least between 2.15 and 2.19.

---

<div class="post-metadata">

**Author:** ![steve.hoffman](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/steve.hoffman/32/66_2.png) [@steve.hoffman](https://forums.percona.com/u/steve.hoffman)\
**Post date:** [July 13, 2021, 3:13pm UTC](https://forums.percona.com/t/pmm-client-forgets-listen-port-for-external-services-after-server-update-to-pmm-2-19/11296/2 "2021-07-13T15:13:48Z")

</div>

Is this only when you run a mistmatched client with 2.19.0 server? In otherwords if both client and server are on 2.19.0 does this happen on agent restart?

Would you mind opening a bug at [jira.percona.com](http://jira.percona.com) so we can get eyes on this?

Thanks!

---

<div class="post-metadata">

**Author:** ![rapli](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@rapli](https://forums.percona.com/u/rapli)\
**Post date:** [July 13, 2021, 4:05pm UTC](https://forums.percona.com/t/pmm-client-forgets-listen-port-for-external-services-after-server-update-to-pmm-2-19/11296/3 "2021-07-13T16:05:05Z")

</div>

This is happening with different client versions; I already had some nodes running with 2.19 where this is happens as well as on nodes with older client versions.  
Bug: PMM-8421.