# QAN API error: "agent not connected" Check whether percona-qan-agent is started.

**URL:** <https://forums.percona.com/t/qan-api-error-agent-not-connected-check-whether-percona-qan-agent-is-started/5265>\
**Category:** PMM 1.x\
**Created:** [December 6, 2016, 4:55pm UTC](https://forums.percona.com/t/qan-api-error-agent-not-connected-check-whether-percona-qan-agent-is-started/5265 "2016-12-06T16:55:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![soniah](https://avatars.discourse-cdn.com/v4/letter/s/838e76/32.png) [@soniah](https://forums.percona.com/u/soniah)\
**Post date:** [December 6, 2016, 4:55pm UTC](https://forums.percona.com/t/qan-api-error-agent-not-connected-check-whether-percona-qan-agent-is-started/5265/1 "2016-12-06T16:55:48Z")

</div>

I have the PMM server running, and the docker containers are up. But I’m getting the following error message in the web interface, and the init script referred to doesn’t exist. I get it when I click on the settings wheel under a database; also there’s no data for the database.

[COLOR=#0000FF][https://4.5.6.7/qan/#/management/mysql/deadbeefdeadbeef](https://4.5.6.7/qan/#/management/mysql/deadbeefdeadbeef)

QAN API error: “agent not connected”.  
Check whether percona-qan-agent is started.  
sudo /etc/init.d/percona-qan-agent start|stop|restart|status

$ ls -1 /etc/init.d | grep perc # nothing

$ cat /etc/redhat-release  
CentOS Linux release 7.2.1511 (Core)

$ s netstat -tanp  
Active Internet connections (servers and established)  
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name  
tcp 0 0 5.6.7.8:53 5.6.7.8:\* LISTEN 1095/named  
tcp 0 0 5.6.7.8:3030 5.6.7.8:\* LISTEN 2204/ruby  
tcp 0 0 5.6.7.8:22 5.6.7.8:\* LISTEN 1001/sshd  
tcp 0 0 5.6.7.8:25 5.6.7.8:\* LISTEN 1629/master  
tcp 0 0 5.6.7.8:953 5.6.7.8:\* LISTEN 1095/named  
tcp 0 0 5.6.7.8:56696 5.6.7.8:5672 ESTABLISHED 2204/ruby  
tcp 0 0 5.6.7.8:22 5.6.7.8:56391 ESTABLISHED 11230/sshd: sonia [  
tcp 0 36 5.6.7.8:22 5.6.7.8:12441 ESTABLISHED 27318/sshd: sonia [  
tcp 0 0 5.6.7.8:43176 5.6.7.8:4505 ESTABLISHED 12783/python  
tcp6 0 0 :::8080 :::\* LISTEN 2966/docker-proxy  
tcp6 0 0 :::80 :::\* LISTEN 2863/docker-proxy  
tcp6 0 0 ::1:53 :::\* LISTEN 1095/named  
tcp6 0 0 :::22 :::\* LISTEN 1001/sshd  
tcp6 0 0 ::1:25 :::\* LISTEN 1629/master  
tcp6 0 0 ::1:953 :::\* LISTEN 1095/named  
tcp6 0 0 :::443 :::\* LISTEN 2849/docker-proxy

---

<div class="post-metadata">

**Author:** ![weber](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@weber](https://forums.percona.com/u/weber)\
**Post date:** [December 7, 2016, 5:21am UTC](https://forums.percona.com/t/qan-api-error-agent-not-connected-check-whether-percona-qan-agent-is-started/5265/2 "2016-12-07T05:21:16Z")

</div>

Looks like this is a broken installation of the old version 1.0.3.  
Please see the reply here [url][https://www.percona.com/forums/questions-discussions/percona-monitoring-and-management/46588-how-do-i-do-a-clean-reinstallation-of-the-pmm-client?p=46599#post46599[/url]](https://www.percona.com/forums/questions-discussions/percona-monitoring-and-management/46588-how-do-i-do-a-clean-reinstallation-of-the-pmm-client?p=46599#post46599%5B/url%5D)