Driver failed programming external connectivity on endpoint pmm-server

Percona Monitoring and Management (PMM)
1

Hello,
I am getting below error while starting the container for PMM, please help.

earlier it was running fine and I change the docker volumes path from /var/lib/docker to other mountpoint due to storage consumption and after that its not getting started.

[root@sqlrtr05 var]# docker start pmm-server
Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (8f185c26af9fd35791c198ee4fa82378f719dff3e66a06c5fcaef9bc48ddcd8d): Bind for 0.0.0.0:443 failed: port is already allocated
Error: failed to start containers: pmm-server
[root@sqlrtr05 var]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 44 hours ago Created pmm-server
83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data
[root@sqlrtr05 var]#

2

Hi @farhan.ext thank you for posting to the Percona forums! This error is being reported because something is already running on port 443/tcp which is probably the pmm-server container.

You can try by doing a docker stop pmm-server container, rename it docker rename pmm-server pmm-server-backup, then do a docker run, let us know how that goes!

3

Hello @Michael_Coburn ,
I ran the below commands as suggested and logs are as below, please let me know what I am doing wrong and how we can fix this:

[root@tmpsrv ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 2 days ago Created pmm-server
83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data

[root@tmpsrv ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

[root@tmpsrv ~]# docker stop pmm-server
pmm-server

[root@tmpsrv ~]# docker rename pmm-server pmm-server-backup
[root@tmpsrv ~]#

[root@tmpsrv ~]# docker run --detach --restart always \

–publish 443:443
-v pmm-data:/apps/docker
–name pmm-server
percona/pmm-server:2.37.0
fd7adc50a22f3a0f9a3c9b1d5b5a7d01249c77a87c94c53a1da52830029fa936
/usr/bin/docker-current: Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (2ae5f366a4fb58764b5d02bc657e4bd3baf725045b414213829d756bcdc36ca6): Bind for 0.0.0.0:443 failed: port is already allocated.

[root@tmpsrv ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fd7adc50a22f percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 55 seconds ago Created pmm-server
051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 2 days ago Created pmm-server-backup
83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data
[root@tmpsrv ~]#
[root@tmpsrv ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[root@tmpsrv ~]#

4

Hello @Michael_Coburn,

can you please advise what I am missing here?

5

You have something listening on port 443 already. Can you please execute:

docker stop pmm-server
docker ps -a | grep 443

This will tell us if there is another container using port 443/tcp

6

Dear @Michael_Coburn,
please find below the status of your commands, there is nothing on 443 port but this error is not going away.

Should I load the pmm image again and create another volumn?

[root@tmpsrv ~]#docker stop pmm-server
pmm-server
[root@tmpsrv ~]#docker ps -a | grep 443
[root@tmpsrv ~]#

7

Then it seems like you have something else listening on 443/tcp , can you check:

ss -4np | 443

This will display network sockets for IPV4 in numerical format and to share the name of the listening process.

8

Dear @Michael_Coburn ,
ss -4np | grep 443 is showing nothing