pmm-server version : 1.1.2
docker logs id :
2017-04-06 14:47:10,962 CRIT Supervisor running as root (no user in config file)
2017-04-06 14:47:10,962 WARN Included extra file “/etc/supervisord.d/pmm.ini” during parsing
how can i fix this ?
don’t worry, these two lines are expected.
if you care about root user inside docker container - fill free to remap container root user to unprivileged user on host system via User Namespaces.
for technical details - https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-user-namespace-options
for implementation details - https://integratedcode.us/2015/10/13/user-namespaces-have-arrived-in-docker/
one more question,
how can i init ( remove) one of qan (query data) matrixs safely. currently i can see 3months data in web qan page.
ex, 1. delete performace_schema table , 2. docker rm pmm-data volume (this will clean all data : ( ) . 3. etc…
It is not recommended, not tested, but I think you can try to stop qan-api interface and truncate some tables in mysql database.
docker exec -it pmm-server supervisorctl stop qan-api
docker exec -it pmm-server mysqldump pmm > pmm-db-backup.sql
docker exec -it pmm-server mysql pmm -e '
truncate query_classes;
truncate query_class_metrics;
truncate query_examples;
'
docker exec -it pmm-server supervisorctl start qan-api
on some systems won’t work due to docker daemon configuration/nature
in case of any issues you can try to restore db.
docker exec -it pmm-server supervisorctl stop qan-api
cat pmm-db-backup.sql | docker exec -i pmm-server mysql pmm
docker exec -it pmm-server supervisorctl start qan-api
please be careful, it is not recommended and not tested
thanks advice,
i had try to truncate them , then
WARNING agent Lost connection to API
WARNING log Lost connection to API
WARNING agent-ws read tcp
WARNING log-ws read tcp
WARNING agent-ws websocket.Dial ws:
WARNING log-ws websocket.Dial ws://
WARNING agent-ws websocket.Dial ws:
WARNING log-ws websocket.Dial ws://
WARNING agent-ws bad status
WARNING log-ws bad status
set the sql back :S
it is expected, when qan-api is down -> qan-agent cannot connect to qan-api.
do you have any issues after qan-api start?
can you restart qan-agent on problematic servers? (may be it can help)
pmm-admin restart mysql:queries