# Bug in ProxySQL dashboard **URL:** \ **Category:** PMM 1.x\ **Created:** [June 2, 2017, 8:20am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654 "2017-06-02T08:20:57Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 2, 2017, 8:20am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/1 "2017-06-02T08:20:57Z")
I think the bugfix included in 1.1.4 was not 100%. I still have some graphs with malfunctions. At first the server status is always showing the same state. On my test system it alwas says 1, 1, 1 and on production 1, 1 ,2. Have a look at the screenshots. I deliberately shut down one server. The hostgroup size is also wrong. But I think those graphs use the same datasource. The second issue is the latency graph. It used to work but isn’t anymore. → See screenshot ![photoid=48638](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/1/170cc333723a7315bc0a613004f756c26d3c9ade.png) ![photoid=48639](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/d/d014508317bee5449c73c207d01174a313b27cee.png) ![photoid=48640](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/d/d17f72167b360524ed78c7de66c4e6e1c134b81b.png) ---
**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:** [June 6, 2017, 11:06pm UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/2 "2017-06-06T23:06:16Z")
Hi [mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342), can you share versions of pmm-client, PMM Server, ProxySQL and OS? ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 19, 2017, 5:02pm UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/3 "2017-06-19T17:02:20Z")
Hi! OS: Ubuntu 16.04 ProxySQL: 1.3.6-1.1.xenial PMM Server: 1.1.4 on Docker PMM Client: 1.1.4-1.xenial ---
**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:** [June 20, 2017, 1:56am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/4 "2017-06-20T01:56:40Z")
can you share the output of the following command? ```auto curl -s http://pmm-client-ip:42004/metrics | grep latency ``` ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 23, 2017, 7:29am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/5 "2017-06-23T07:29:02Z")
I had to change your command a little bit: ```auto curl -s --insecure https://ip:42004/metrics | grep latency ``` Here’s the output: ```auto # HELP proxysql_connection_pool_latency_us Connection pool usage statistic. # TYPE proxysql_connection_pool_latency_us gauge proxysql_connection_pool_latency_us{endpoint="xtradb1:3306",hostgroup="10"} 578 proxysql_connection_pool_latency_us{endpoint="xtradb1:3306",hostgroup="20"} 578 proxysql_connection_pool_latency_us{endpoint="xtradb2:3306",hostgroup="10"} 692 proxysql_connection_pool_latency_us{endpoint="xtradb2:3306",hostgroup="20"} 692 proxysql_connection_pool_latency_us{endpoint="xtradb3:3306",hostgroup="10"} 584 proxysql_connection_pool_latency_us{endpoint="xtradb3:3306",hostgroup="20"} 584 ``` ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 23, 2017, 7:40am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/6 "2017-06-23T07:40:04Z")
I just upgraded to 1.1.5. The latency graph is back but the node status is still not right. (See screenshots) ![photoid=48826](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/4/49d919d0f69ec35efe67b803970d63d204523329.png) ![photoid=48827](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/3/325c502d1fffdb8d687d11c4302a377bf8bd558c.png) ---
**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:** [June 26, 2017, 7:31am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/7 "2017-06-26T07:31:03Z")
Hi [mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342), what specifically isn’t right about your node status? Could you share: ```auto curl -s --insecure https://ip:42004/metrics | grep "proxysql_connection_pool_status" ``` output of ProxySQL admin information: ```auto select * from mysql_servers; ``` ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 26, 2017, 7:58am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/8 "2017-06-26T07:58:46Z")
Please look at the screenshots in my post before. Grafana says 1,1,3 but it’s 1,1,1. Here is what you wanted: ```auto +--------------+----------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ | hostgroup_id | hostname | port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment | +--------------+----------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ | 10 | xtradb1 | 3306 | ONLINE | 1000 | 0 | 1000 | 0 | 0 | 0 | | | 10 | xtradb2 | 3306 | ONLINE | 1000 | 0 | 1000 | 0 | 0 | 0 | | | 10 | xtradb3 | 3306 | ONLINE | 1000 | 0 | 1000 | 0 | 0 | 0 | | | 20 | xtradb3 | 3306 | OFFLINE_SOFT | 1000 | 0 | 1000 | 0 | 0 | 0 | | | 20 | xtradb2 | 3306 | OFFLINE_SOFT | 1000 | 0 | 1000 | 0 | 0 | 0 | | | 20 | xtradb1 | 3306 | ONLINE | 1000 | 0 | 1000 | 0 | 0 | 0 | | +--------------+----------+------+--------------+--------+-------------+-----------------+---------------------+---------+----------------+---------+ # HELP proxysql_connection_pool_status Connection pool usage statistic. # TYPE proxysql_connection_pool_status gauge proxysql_connection_pool_status{endpoint="xtradb1:3306",hostgroup="10"} 1 proxysql_connection_pool_status{endpoint="xtradb1:3306",hostgroup="20"} 1 proxysql_connection_pool_status{endpoint="xtradb2:3306",hostgroup="10"} 3 proxysql_connection_pool_status{endpoint="xtradb2:3306",hostgroup="20"} 3 proxysql_connection_pool_status{endpoint="xtradb3:3306",hostgroup="10"} 1 proxysql_connection_pool_status{endpoint="xtradb3:3306",hostgroup="20"} 3 ``` As you can see the outputs don’t match. ---
**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:** [June 28, 2017, 12:28pm UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/9 "2017-06-28T12:28:30Z")
[mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , thanks for sharing the output. Agreed this is suspicious, and we (PMM Dev team) are discussing this internally and attempting to reproduce. We’ll update this thread shortly. ---
**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:** [June 28, 2017, 1:11pm UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/10 "2017-06-28T13:11:29Z")
Hi [mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , one of our Engineers has requested the full /metrics output. You may want to DM or email it to me if you prefer [michael.coburn@percona.com](mailto:michael.coburn@percona.com) ```auto ``` ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [June 30, 2017, 10:21am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/11 "2017-06-30T10:21:41Z")
I emailed it to you because the PM feature somehow doesn’t work. ---
**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:** [July 11, 2017, 9:22am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/12 "2017-07-11T09:22:22Z")
Hi [mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , my apologies for the delay on this topic. Our Developers want to confirm that you are collecting data at the same point in time, that there isn’t any potential for drift between what ProxySQL vs proxysql\_exporter reports. Can you please run the commands below, and replace IP with the address of the instance where proxysql\_exporter is running: ```auto date curl -s --insecure https://IP:42004/metrics | grep proxysql_connection_pool_status date mysql -uadmin -padmin -S/tmp/proxysql_admin.sock -e "select * from stats_mysql_connection_pool ORDER BY hostgroup, srv_host, srv_port;" date mysql -uadmin -padmin -S/tmp/proxysql_admin.sock -e "select * from runtime_mysql_servers" ``` Thanks [mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , ---
**Author:** ![Ralph\_Moser](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ralph_moser/32/7966_2.png) [@Ralph\_Moser](https://forums.percona.com/u/Ralph_Moser)\ **Post date:** [July 12, 2017, 7:00am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/13 "2017-07-12T07:00:12Z")
Hi, on Sunday I did my usual reboot cycle and the monitor worked correctly. Now I tried to reproduce the issue on our test system to collect the logs you requested. No chance. Everything works fine now. The question is why. The only updated which got in was a proxysql update. ---
**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:** [July 12, 2017, 8:49am UTC](https://forums.percona.com/t/bug-in-proxysql-dashboard/5654/14 "2017-07-12T08:49:26Z")
[mosi0815](https://percona.vanillacommunities.com/profile/x/x/27342) , well on one hand I am delighted that your environment is again working! But on the other hand I fear that your experience may be the first of several to occur related to discrepancies between status in ProxySQL vs exporter. In my own exploratory testing I was using latest releases: [LIST] [_]ProxySQL 1.3.7 (Percona build) [_]proxysql\_exporter from pmm-client 1.1.5 [/LIST] I’m going to close this thread, but if you happen to see this issue reoccur please start a new thread and we’ll take action. Thanks again for your cooperation while we diagnosed this!