proxysql | High-performance MySQL proxy with a GPL license | Proxy library

Execute Set mysql-verbose_query_error = true when you begin the database connection in your applications.

FYI:

How to change variables

Functionality regarding the variable: mysql-verbose_query_error

The answer is that mysql_query_rules_fast_routing rules don't get applied if the last mysql_query_rules rule has an apply of 1. You need to leave that as apply=0 and then the fast query rules will then get applied.

I think this may reflect some of the ambiguity in what "leak" means. Tools like Valgrind will traverse the pointer graph of the program at shutdown, and treat things as leaks if that traversal does not find some live allocation.

Other tools treat "leaks" as simply anything allocated but not freed. The profiling mode in jemalloc works more like this way. It reports an estimation of the live bytes attributable to various call stacks at program termination.

Looks like the issue is the host 'zerk2'@'2a02:4780:bad:f00d::7'. You maybe on the same machine but your php and node running from different servers and looks like your node is running via a proxy. php could be running from apache and nodejs from another http server. Not sure how you have set up the server. To fix this you have to modify or create a mysql user with host set to % to allow access from any host.

UPDATES:

It's failing to connect to mysql server Error: connect ECONNREFUSED 127.0.0.1:3306 for NodeJS. Try to use server's ip address or domain as host instead of localhost and see if that works for you. PHP looks like it connects but the user don't have access could be the password or the user can't access it from host 2a02:4780:bad:f00d::7 that's why you'll need a mysql user with host %. Also note it will not work if you have two users with that same name and one's host is not %.

There are two problems:

1. In the playbook, tasks are included in a loop that has the loop variable name item and the included task also has a loop and the default variable name is again item. This is why the warning messages and to solve that use loop_control.

2. my_var: item assignment needs to be in format my_var: "{{ item }}" for correct assignment.

After both the corrections, playbook would look like this.

Your perconaxtradbclusters yaml example mentions pvc resources, so you'll probably have to delete the associated pvc first, if you haven't already done so.

Can you edit the resources to remove the finalizer blocks, and try delete them again?

kubectl edit perconaxtradbclusters cluster1 -n pxc

and delete