After memory upgrade PMM3.0 is giving error on webpage

Percona Monitoring and Management (PMM) PMM 3.x
1

Background. Was running latest version of PMM2. Upgraded using the migration steps to PMM3.0 provided and all seemed to be working as expected. Memory was added and it broke PMM. I looked for logs in /etc/suvpervisord.d but no directory with this name. Not sure where to go from here.
Tried starting docker and it gave message:
Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (1c3d0e194ae9e16a628b3f49db78bbfe86bbe9ef4527ccd90a25e98ccf3cfb82): Bind for 0.0.0.0:443 failed: port is already allocated

Suggestions?

2

Hi!

Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (1c3d0e194ae9e16a628b3f49db78bbfe86bbe9ef4527ccd90a25e98ccf3cfb82): Bind for 0.0.0.0:443 failed: port is already allocated

You cannot have 2 services executing concurrently and using the same port. Do you have any other PMM install or any other software already using port 443?

1 Like
3

Doesn’t look like anything is running on that port:

root@pmm:/var/lib/docker/containers# docker version
Client: Docker Engine - Community
Version: 27.1.1
API version: 1.46
Go version: go1.21.12
Git commit: 6312585
Built: Tue Jul 23 19:57:19 2024
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 27.1.1
API version: 1.46 (minimum version 1.24)
Go version: go1.21.12
Git commit: cc13f95
Built: Tue Jul 23 19:57:19 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.19
GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc:
Version: 1.7.19
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
root@pmm:/var/lib/docker/containers# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5cbcf97e7933 percona/watchtower “/watchtower --clean…” 11 days ago Up 7 days (healthy) 8080/tcp watchtower
c11df1c3fbfd percona/pmm-server:3.0.0 “/opt/entrypoint.sh” 11 days ago Exited (137) 7 days ago pmm-server
b3c09024250a percona/pmm-server:3.0.0 “/opt/entrypoint.sh” 11 days ago Created pmm2
f0611696fe97 percona/pmm-server:2 “/opt/entrypoint.sh” 9 months ago Up 7 days (unhealthy) 80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp pmm-server-2025-03-13-103733n
fb812e112def percona/pmm-server:2 “/bin/true” 9 months ago Created pmm-data
root@pmm:/var/lib/docker/containers# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 503/sshd: /usr/sbin
tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 455/nrpe
tcp6 0 0 :::22 :::* LISTEN 503/sshd: /usr/sbin
tcp6 0 0 :::5666 :::* LISTEN 455/nrpe
root@pmm:/var/lib/docker/containers# netstat -ano | grep 443
root@pmm:/var/lib/docker/containers#

4

removed container and was able to docker start pmm-server and it started but is getting this error:
“PermissionError: [Errno 13] Permission denied: ‘/srv/logs/supervisord.log’\n”,“stream”:“stderr”,“time”:“2025-03-24T22:42:25.792673869Z”}

I am looking into permissions

5

closing, had to revert back to 2.44 to get this to work again. I was able to get PMM3 running again but I could not get access from the webpage. On PMM3 NGINX is crashing silently or not binding at all, even though supervisord thinks it’s “running.” Docker, the container starts and reports as healthy, but NGINX refuses all incoming connections on port 80 and 443. Investigation shows that the /etc/nginx/conf.d directory is empty, and no default server configuration is present. Will increase the space while running PMM2 and then upgrade again to PMM3 to see if I still have the problem.