# check docker logs
**URL:** https://forums.percona.com/t/check-docker-logs/5530
**Category:** PMM 1.x
**Created:** [April 6, 2017, 9:23pm UTC](https://forums.percona.com/t/check-docker-logs/5530 "2017-04-06T21:23:28Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@scar2yjs](https://forums.percona.com/u/scar2yjs)
#### Post date: [April 6, 2017, 9:23pm UTC](https://forums.percona.com/t/check-docker-logs/5530/1 "2017-04-06T21:23:28Z")
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 ?
---
### Author:  [@Mykola](https://forums.percona.com/u/Mykola)
#### Post date: [April 6, 2017, 11:49pm UTC](https://forums.percona.com/t/check-docker-logs/5530/2 "2017-04-06T23:49:17Z")
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 - [url][dockerd | Docker Documentation](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-user-namespace-options%5B/url%5D)
for implementation details - [url][https://integratedcode.us/2015/10/13/user-namespaces-have-arrived-in-docker/[/url]](https://integratedcode.us/2015/10/13/user-namespaces-have-arrived-in-docker/%5B/url%5D)
---
### Author:  [@scar2yjs](https://forums.percona.com/u/scar2yjs)
#### Post date: [April 7, 2017, 12:06am UTC](https://forums.percona.com/t/check-docker-logs/5530/3 "2017-04-07T00:06:30Z")
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…
---
### Author:  [@Mykola](https://forums.percona.com/u/Mykola)
#### Post date: [April 7, 2017, 12:27am UTC](https://forums.percona.com/t/check-docker-logs/5530/4 "2017-04-07T00:27:31Z")
It is not recommended, not tested, but I think you can try to stop qan-api interface and truncate some tables in mysql database.
```auto
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.
```auto
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
---
### Author:  [@scar2yjs](https://forums.percona.com/u/scar2yjs)
#### Post date: [April 9, 2017, 9:42pm UTC](https://forums.percona.com/t/check-docker-logs/5530/5 "2017-04-09T21:42:16Z")
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
---
### Author:  [@Mykola](https://forums.percona.com/u/Mykola)
#### Post date: [April 10, 2017, 1:01am UTC](https://forums.percona.com/t/check-docker-logs/5530/6 "2017-04-10T01:01:34Z")
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)
```auto
pmm-admin restart mysql:queries
```