# critical bug: pmm-client 1.1.3 mysql:queries exit with status 1

**URL:** <https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606>\
**Category:** PMM 1.x\
**Created:** [May 16, 2017, 6:48am UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606 "2017-05-16T06:48:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoyG](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@JoyG](https://forums.percona.com/u/JoyG)\
**Post date:** [May 16, 2017, 6:48am UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606/1 "2017-05-16T06:48:55Z")

</div>

I’m facing trouble while upgrading

pmm-admin add mysql --user root --password password

[linux:metrics] OK, already monitoring this system.  
[mysql:metrics] OK, now monitoring MySQL metrics using DSN root:\*\*\*@unix(/data/mysql/mysql.sock)  
[mysql:queries] Error adding MySQL queries: problem with agent registration on QAN API: exit status 1

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [May 19, 2017, 10:58am UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606/2 "2017-05-19T10:58:08Z")

</div>

Hi [JoyG](https://percona.vanillacommunities.com/profile/x/x/38018) , my apologies for not answering your post sooner. May I suggest you remove the instance, and then re-add with --verbose so we can get greater detail for why the QAN part is failing?

```auto
pmm-admin remove mysql
pmm-admin add mysql --verbose

```

---

<div class="post-metadata">

**Author:** ![pimoens](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@pimoens](https://forums.percona.com/u/pimoens)\
**Post date:** [July 6, 2017, 9:53am UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606/3 "2017-07-06T09:53:18Z")

</div>

I am currently experiencing the same output when attempting to add the mysql:queries service to a fresh pmm-client installation.  
Thus far I have not found a clear solution to the problem.

My verbose output is given in the txt file.

[qan\_api\_error.txt](https://forums.percona.com/uploads/short-url/nqWrc2NEWrt8pxHxb1OVRFXB3S4.txt) (11.4 KB)

---

<div class="post-metadata">

**Author:** ![Mykola](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mykola/32/30_2.png) [@Mykola](https://forums.percona.com/u/Mykola)\
**Post date:** [July 6, 2017, 12:16pm UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606/4 "2017-07-06T12:16:02Z")

</div>

Hi Pomoens,

can you give me the version of your PMM Server and PMM Client?  
Do you have enough free space inside PMM Server container?  
Is pmm-admin tool has been run from root rights?

according to logs your application failed during run  
see [url][pmm-client/queries.go at master · percona/pmm-client · GitHub](https://github.com/percona/pmm-client/blob/master/pmm/queries.go#L149-L164%5B/url%5D) for details  
tool has debug flag.

can you run in debug mode and share output?  
theoretically, needed command can look like this:

```auto
/usr/local/percona/qan-agent/bin/percona-qan-agent-installer -debug -mysql=false -server-user=USER -server-pass=PASSWORD PMM-IP

```

please use the following command if you are working via SSL

```auto
/usr/local/percona/ qan -agent/bin/percona- qan -agent-installer -debug -mysql=false -server-user=USER -server-pass=PASSWORD -use-insecure-ssl PMM-IP:443

```

---

<div class="post-metadata">

**Author:** ![bckim](https://avatars.discourse-cdn.com/v4/letter/b/67e7ee/32.png) [@bckim](https://forums.percona.com/u/bckim)\
**Post date:** [January 16, 2018, 1:55am UTC](https://forums.percona.com/t/critical-bug-pmm-client-1-1-3-mysql-queries-exit-with-status-1/5606/5 "2018-01-16T01:55:00Z")

</div>

I had same issue.

In my case, my docker mysql database was not up in docker.

so QAN was not ready to receive from client.

thanks.