The pmm-server fails to start correctly continuously respawning createdb, createdb2, and createdb3 processes due to exits. Running on 17.12.0-ce.
docker-compose,yml file:
version: ‘3’
services:
app:
image: percona/pmm-server:latest
container_name: pmm-server
restart: on-failure:5
ports:
- “8080:80”
The following are the logs:
Recreating be30bb37cf3d_pmm-server …
Recreating be30bb37cf3d_pmm-server … done
Attaching to pmm-server
pmm-server | 2018-07-11 16:49:45,721 CRIT Supervisor running as root (no user in config file)
pmm-server | 2018-07-11 16:49:45,722 WARN Included extra file “/etc/supervisord.d/pmm.ini” during parsing
pmm-server | 2018-07-11 16:49:46,098 INFO RPC interface ‘supervisor’ initialized
pmm-server | 2018-07-11 16:49:46,099 INFO supervisord started with pid 6
pmm-server | 2018-07-11 16:49:47,105 INFO spawned: ‘mysql’ with pid 27
pmm-server | 2018-07-11 16:49:47,116 INFO spawned: ‘consul’ with pid 28
pmm-server | 2018-07-11 16:49:47,126 INFO spawned: ‘grafana’ with pid 29
pmm-server | 2018-07-11 16:49:47,138 INFO spawned: ‘nginx’ with pid 30
pmm-server | 2018-07-11 16:49:47,188 INFO spawned: ‘cron’ with pid 31
pmm-server | 2018-07-11 16:49:47,237 INFO spawned: ‘qan-api’ with pid 32
pmm-server | 2018-07-11 16:49:47,283 INFO spawned: ‘prometheus’ with pid 33
pmm-server | 2018-07-11 16:49:48,017 INFO spawned: ‘createdb2’ with pid 35
pmm-server | 2018-07-11 16:49:48,057 INFO spawned: ‘createdb3’ with pid 36
pmm-server | 2018-07-11 16:49:48,092 INFO spawned: ‘createdb’ with pid 37
pmm-server | 2018-07-11 16:49:48,270 INFO spawned: ‘dashboard-upgrade’ with pid 41
pmm-server | 2018-07-11 16:49:48,459 INFO spawned: ‘node_exporter’ with pid 42
pmm-server | 2018-07-11 16:49:48,468 INFO spawned: ‘pmm-manage’ with pid 43
pmm-server | 2018-07-11 16:49:48,490 INFO spawned: ‘pmm-managed’ with pid 44
pmm-server | 2018-07-11 16:49:49,495 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,495 INFO success: consul entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,495 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,496 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,496 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,497 INFO success: qan-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,497 INFO success: prometheus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,498 INFO success: createdb2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,498 INFO success: createdb3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,498 INFO success: createdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,499 INFO success: dashboard-upgrade entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,500 INFO success: node_exporter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,500 INFO success: pmm-manage entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:49,500 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:55,692 INFO exited: createdb2 (exit status 1; not expected)
pmm-server | 2018-07-11 16:49:55,693 INFO exited: createdb3 (exit status 1; not expected)
pmm-server | 2018-07-11 16:49:55,694 INFO exited: createdb (exit status 1; not expected)
pmm-server | 2018-07-11 16:49:56,412 INFO spawned: ‘createdb2’ with pid 76
pmm-server | 2018-07-11 16:49:56,418 INFO spawned: ‘createdb3’ with pid 77
pmm-server | 2018-07-11 16:49:56,423 INFO spawned: ‘createdb’ with pid 78
pmm-server | 2018-07-11 16:49:58,368 INFO success: createdb2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:58,369 INFO success: createdb3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:49:58,370 INFO success: createdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:01,856 INFO exited: createdb2 (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:01,857 INFO exited: createdb3 (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:01,858 INFO exited: createdb (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:02,863 INFO spawned: ‘createdb2’ with pid 95
pmm-server | 2018-07-11 16:50:02,867 INFO spawned: ‘createdb3’ with pid 96
pmm-server | 2018-07-11 16:50:02,872 INFO spawned: ‘createdb’ with pid 97
pmm-server | 2018-07-11 16:50:03,876 INFO success: createdb2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:03,876 INFO success: createdb3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:03,877 INFO success: createdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:07,941 INFO exited: createdb2 (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:07,980 INFO spawned: ‘createdb2’ with pid 106
pmm-server | 2018-07-11 16:50:07,985 INFO exited: createdb3 (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:08,017 INFO spawned: ‘createdb3’ with pid 108
pmm-server | 2018-07-11 16:50:08,019 INFO exited: createdb (exit status 1; not expected)
pmm-server | 2018-07-11 16:50:08,106 INFO spawned: ‘createdb’ with pid 111
pmm-server | 2018-07-11 16:50:09,689 INFO success: createdb2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:09,689 INFO success: createdb3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
pmm-server | 2018-07-11 16:50:09,690 INFO success: createdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)