Open kashak88 opened 5 years ago
I've adjusted some timeout values on all servers and decided to monitor for growing CPU usage and VIRT overnight. One server had a particularly high values so I decided to investigate:
2019-09-07 15:27:04 [INFO] Received command set mysql-monitor_connect_timeout=1500
2019-09-07 15:27:04 [INFO] Received command set mysql-monitor_ping_timeout=1500
2019-09-07 15:27:04 [INFO] Received command set mysql-monitor_replication_lag_timeout=1500
2019-09-07 15:27:04 [INFO] Received command set mysql-monitor_query_timeout=300
2019-09-07 15:27:04 [INFO] Received command set mysql-monitor_read_only_timeout=1500
2019-09-07 15:27:04 [INFO] Received LOAD MYSQL VARIABLES TO RUNTIME command
2019-09-07 15:27:04 [INFO] Received SAVE MYSQL VARIABLES TO DISK command
2019-09-07 15:39:17 [INFO] Received command set mysql-monitor_replication_lag_interval=10000
2019-09-07 15:39:17 [INFO] Received LOAD MYSQL VARIABLES TO RUNTIME command
2019-09-07 15:39:17 [INFO] Received SAVE MYSQL VARIABLES TO DISK command
2019-09-08 05:25:45 MySQL_Monitor.cpp:978:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.34.1.40:3306 after 1500ms. If the server is overload, increase mysql-monitor_read_only_timeout.
2019-09-08 05:25:45 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7fad3d8e4780 , MYSQL 0x7fad3f6de100 , FD 20 : timeout check
2019-09-08 06:56:20 MySQL_Monitor.cpp:978:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.34.1.40:3306 after 1504ms. If the server is overload, increase mysql-monitor_read_only_timeout.
2019-09-08 06:56:20 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7fad3d8e8600 , MYSQL 0x7fad3f619200 , FD 21 : timeout check
2019-09-08 06:57:32 MySQL_Monitor.cpp:978:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.34.1.40:3306 after 1501ms. If the server is overload, increase mysql-monitor_read_only_timeout.
2019-09-08 06:57:32 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7fad3d8a1980 , MYSQL 0x7fad40ed3d00 , FD 24 : timeout check
5:25 is around the time Veeam backs up our backend DB servers. Maybe related? EDIT: Just checked other web servers that use the same backend servers, all of them got the same error, so this must be due to Veeam(at least the errors).
@kashak88 : maybe related to #2244 ?
@renecannao perhaps, but our frontend connection no longer has SSL. We've had an issue with some(not all) simple PDO SELECT queries getting stuck when sending them via proxysql(2.0.5, 2.0.6). The load average on the server would always jump after executing them and I could see them get stuck in proxysql processlist until daemon restart. Once in a blue the query would execute successfully, maybe 1 out of 20 times, completely random. Slightly modifying the queries to produce less results made them execute without issues, which was weird. Couldn't figure it out until we tried to disable these options:
$sslOptionKeys = [
PDO::MYSQL_ATTR_SSL_KEY,
PDO::MYSQL_ATTR_SSL_CERT,
PDO::MYSQL_ATTR_SSL_CA,
PDO::MYSQL_ATTR_SSL_CIPHER
];
After doing so, everything executed without issues. Backend SSL still enabled. So something was causing issues when frontend SSL connection was enabled.
Regarding the issue in this ticket, after adjusting mysql-monitor_read_only_timeout=10000 (and other timeout values which were showing errors in the log) the VIRT on all (40+ that were affected) servers hasn't grown over 250,000 and load average is very low after 3 days, even where proxysql is active. Usually the issue would start in less than a day after restarting proxysql daemon.
Well, I spoke too soon. Another timeout error appeared in the log about 3 hours ago, on a server that is not using proxysql yet (idle):
2019-09-09 19:02:30 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 5 second
2019-09-09 19:02:40 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-09 19:04:10 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 2 second
2019-09-09 19:04:20 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-09 19:04:30 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 4 second
2019-09-09 19:04:40 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-09 19:06:40 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 7 second
2019-09-09 19:06:50 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-09 19:08:20 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 7 second
2019-09-09 19:08:51 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-09 19:09:50 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 5 second
2019-09-09 19:10:00 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-10 11:35:33 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f0004208d60 , MYSQL 0x7f0003403700 , FD 20 : Lost connection to MySQL server during query
2019-09-10 11:37:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f0004209ee0 , MYSQL 0x7f000391a000 , FD 22 : Lost connection to MySQL server during query
2019-09-10 11:39:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f00042356c0 , MYSQL 0x7efffd631300 , FD 20 : Lost connection to MySQL server during query
2019-09-10 11:41:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f000421d840 , MYSQL 0x7efffe29ef00 , FD 21 : Lost connection to MySQL server during query
2019-09-10 11:43:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f0004223b20 , MYSQL 0x7efffd232700 , FD 20 : Lost connection to MySQL server during query
2019-09-10 11:45:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f00042234e0 , MYSQL 0x7f0000c30e00 , FD 21 : Lost connection to MySQL server during query
2019-09-10 12:52:33 MySQL_Monitor.cpp:955:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.30.1.45:3306 after 1001ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to MySQL server on '10.30.1.45' (110).
2019-09-10 12:55:31 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 2 second
2019-09-10 12:55:41 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 1 second
2019-09-10 12:55:51 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 2 second
2019-09-10 12:56:16 MySQL_Monitor.cpp:955:monitor_read_only_thread(): [ERROR] Timeout on read_only check for 10.30.1.45:3306 after 1001ms. Unable to create a connection. If the server is overload, increase mysql-monitor_connect_timeout. Error: timeout on creating new connection: Can't connect to MySQL server on '10.30.1.45' (110).
2019-09-10 12:56:31 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 0 second
2019-09-10 12:57:11 MySQL_HostGroups_Manager.cpp:2807:replication_lag_action(): [WARNING] Shunning server 10.30.1.46:3306 from HG 1 with replication lag of 2 second
2019-09-10 12:58:01 MySQL_HostGroups_Manager.cpp:2818:replication_lag_action(): [WARNING] Re-enabling server 10.30.1.46:3306 from HG 1 with replication lag of 1 second
VIRT became 4332448 and CPU usage is at 100% by proxysql:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
43548 proxysql 20 0 4332448 269220 8680 S 100.3 3.3 184:22.21 proxysql -c /etc/proxysql.cnf -D /var/lib/proxysql
Other servers seem fine for now... Interestingly enough, the read_only check failed after 1001ms yet here are the runtime settings:
mysql> select * from runtime_global_variables where variable_name like 'mysql-monitor%timeout';
+----------------------------------------------------+----------------+
| variable_name | variable_value |
+----------------------------------------------------+----------------+
| mysql-monitor_connect_timeout | 1500 |
| mysql-monitor_ping_timeout | 1500 |
| mysql-monitor_read_only_timeout | 10000 |
| mysql-monitor_replication_lag_timeout | 1500 |
| mysql-monitor_groupreplication_healthcheck_timeout | 800 |
| mysql-monitor_galera_healthcheck_timeout | 800 |
| mysql-monitor_query_timeout | 300 |
| mysql-monitor_wait_timeout | true |
+----------------------------------------------------+----------------+
Another single server occurrence:
2019-09-12 07:34:49 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d6640 , MYSQL 0x7f9eac8c7900 , FD 27 : Lost connection to MySQL server during query
2019-09-12 07:36:30 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d6820 , MYSQL 0x7f9eb2b33900 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:38:10 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d9520 , MYSQL 0x7f9eac898100 , FD 21 : Lost connection to MySQL server during query
2019-09-12 07:39:51 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f4ae0 , MYSQL 0x7f9eac898b00 , FD 23 : Lost connection to MySQL server during query
2019-09-12 07:41:31 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d7ae0 , MYSQL 0x7f9eac895400 , FD 20 : Lost connection to MySQL server during query
2019-09-12 07:43:12 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f4e00 , MYSQL 0x7f9eb2ad4700 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:44:52 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78da740 , MYSQL 0x7f9eb2a16e00 , FD 21 : Lost connection to MySQL server during query
2019-09-12 07:44:53 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d7ea0 , MYSQL 0x7f9eb2a18700 , FD 20 : Unknown MySQL error
2019-09-12 07:46:34 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d8080 , MYSQL 0x7f9eb2ad3d00 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:48:15 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f5800 , MYSQL 0x7f9eb2b36600 , FD 21 : Lost connection to MySQL server during query
2019-09-12 07:49:55 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78da880 , MYSQL 0x7f9eac896300 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:51:36 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d8580 , MYSQL 0x7f9eac894a00 , FD 20 : Lost connection to MySQL server during query
2019-09-12 07:53:16 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f47c0 , MYSQL 0x7f9eb2b36100 , FD 21 : Lost connection to MySQL server during query
2019-09-12 07:54:57 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d9e80 , MYSQL 0x7f9eb2bad800 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:56:37 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d9200 , MYSQL 0x7f9eb2ad4200 , FD 21 : Lost connection to MySQL server during query
2019-09-12 07:58:18 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d6320 , MYSQL 0x7f9eb2a18700 , FD 19 : Lost connection to MySQL server during query
2019-09-12 07:59:58 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d8da0 , MYSQL 0x7f9eb2b34800 , FD 21 : Lost connection to MySQL server during query
2019-09-12 08:01:39 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78dab00 , MYSQL 0x7f9eb2a16400 , FD 19 : Lost connection to MySQL server during query
2019-09-12 08:03:20 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d70e0 , MYSQL 0x7f9eb2baec00 , FD 20 : Lost connection to MySQL server during query
2019-09-12 08:05:00 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f4540 , MYSQL 0x7f9eac894000 , FD 19 : Lost connection to MySQL server during query
2019-09-12 08:06:41 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d8300 , MYSQL 0x7f9eb2b33400 , FD 29 : Lost connection to MySQL server during query
2019-09-12 08:08:21 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f53a0 , MYSQL 0x7f9eb2b33e00 , FD 19 : Lost connection to MySQL server during query
2019-09-12 08:10:02 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d9a20 , MYSQL 0x7f9eb2baf600 , FD 21 : Lost connection to MySQL server during query
2019-09-12 08:11:42 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d8b20 , MYSQL 0x7f9eb2babf00 , FD 19 : Lost connection to MySQL server during query
2019-09-12 08:13:23 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f3be0 , MYSQL 0x7f9eb2a19100 , FD 21 : Lost connection to MySQL server during query
2019-09-12 08:15:03 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d9ca0 , MYSQL 0x7f9eb2b35700 , FD 20 : Lost connection to MySQL server during query
2019-09-12 08:16:44 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d7f40 , MYSQL 0x7f9eb2ad2e00 , FD 19 : Lost connection to MySQL server during query
2019-09-12 08:18:24 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f3000 , MYSQL 0x7f9eb2ad3800 , FD 20 : Lost connection to MySQL server during query
2019-09-12 08:20:05 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb78d6c80 , MYSQL 0x7f9eb2b35200 , FD 21 : Lost connection to MySQL server during query
2019-09-12 08:20:05 MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f9eb60f3f00 , MYSQL 0x7f9eb2b34800 , FD 19 : Unknown MySQL error
VIRT grew to 13G, CPU usage was OK. 2nd Web server in the cluster with identical resources, proxysql configuration, identical code and identical backend connections did not produce any errors. Setting variables on all servers to this, increasing mysql-monitor_read_only_interval:
+-----------------------------------------------------+-------+
| Variable_name | Value |
+-----------------------------------------------------+-------+
| mysql-monitor_connect_timeout | 10000 |
| mysql-monitor_ping_timeout | 3000 |
| mysql-monitor_replication_lag_timeout | 1500 |
| mysql-monitor_groupreplication_healthcheck_interval | 5000 |
| mysql-monitor_groupreplication_healthcheck_timeout | 800 |
| mysql-monitor_galera_healthcheck_interval | 5000 |
| mysql-monitor_galera_healthcheck_timeout | 800 |
| mysql-monitor_query_interval | 60000 |
| mysql-monitor_query_timeout | 300 |
| mysql-monitor_wait_timeout | true |
| mysql-monitor_connect_interval | 60000 |
| mysql-monitor_ping_interval | 10000 |
| mysql-monitor_read_only_interval | 10000 |
| mysql-monitor_read_only_timeout | 10000 |
| mysql-monitor_replication_lag_interval | 10000 |
+-----------------------------------------------------+-------+
Will report if we get any errors again...
Got a few of these again on 2 servers (out of total 3):
MySQL_Monitor.cpp:1123:monitor_read_only_thread(): [ERROR] Got error: mmsd 0x7f42dd807320 , MYSQL 0x7f42da70b900 , FD 24 : Lost connection to MySQL server during query
Server load is fine, but VIRT is at 13-15G Hopefully this is indeed related to #2244 ...
VIRT has not grown to larger than 280K on any of our servers since we've upgraded to 2.0.7, so I am guessing this was related to openssl issue outlined in #2244 .
Thanks, closing this
Same issue for proxysql 2.0.12 After a couple of days, proxysql starts to eat CPU (no high load, no client's connection). OS debian 10, hosted on KVM hypervisor Proxysql variables https://gist.github.com/jurim76/c7a2b40074efa4db36a13c2cac3e44bd
Hi @jurim76 , you aren't showing the problem.
Some output from top
(or similar), several outputs of status variables, AND output of perf top
and perf report
would be a great way to start pointing to an issue
Hello, here are some samples.
Hi @jurim76 . Thank you for the output. Can you provide new output of status variables?
You claim that "no client's connection", while ProxySQL says there are 132 clients connected: can you confirm them? I also see that are perhaps relevant:
| Client_Connections_aborted | 40 |
| Client_Connections_connected | 132 |
| Client_Connections_created | 3872 |
| Queries_frontends_bytes_recv | 153675 |
| Queries_frontends_bytes_sent | 308583 |
| Questions | 0 |
Please also send the full error log. Re-opening this issue.
Looks like connections from openvas security scanner. I will report later, when security scan will be disabled.
What "similar" means? #1846 is about a crash
In my case, openvas is a troublemaker, so it's the openvas issue. When openvas finished scan, proxysql doesn't crashed, but eat CPU with a bunch of connections in CLOSE_WAIT state.
Ok, so I wouldn't consider it "similar".
Please run this in Admin, and attach the file /tmp/log2240.txt
tee /tmp/log2240.txt
SET mysql-show_processlist_extended=1;
LOAD MYSQL VARIABLES TO RUNTIME;
SELECT * FROM stats_mysql_processlist\G
SET mysql-show_processlist_extended=2;
LOAD MYSQL VARIABLES TO RUNTIME;
SELECT * FROM stats_mysql_processlist\G
Thanks
Sorry, unable to execute commands
mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 122964 Server version: 10.3.23 (ProxySQL Admin Module)
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Admin> tee /tmp/log2240.txt Logging to file '/tmp/log2240.txt' Admin> SET mysql-show_processlist_extended=1; Query OK, 1 row affected (0.006 sec)
Admin> LOAD MYSQL VARIABLES TO RUNTIME; Query OK, 0 rows affected (0.002 sec)
Admin> SELECT * FROM stats_mysql_processlist\G ERROR 2013 (HY000): Lost connection to MySQL server during query
After that, hunged connections disappeared and proxysql returned to normal state (no cpu consumption)
It means proxysql crashed while trying to collect metrics (probably a known bug fixed in 2.0.13). Do you have a core dump?
I also encountered the same problem. When the CPU usage is high on an idle proxysql, the log looks like this:
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Received malformed line (no colon). Closing connection.
Error processing request (HTTP response code is 400 (<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection. Failed to send data in request for
/tunnel'.
Received malformed line (no colon). Closing connection.
Error processing request (HTTP response code is 400 (<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection. Failed to send data in request for
/tunnel'.
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Error: received handshake message out of context
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Received HTTP 1.1 request without Host' header. Received HTTP 1.1 request without
Host' header.
Error: received handshake message out of context
Error: received handshake message out of context
2020-06-17 23:53:01 MySQL_Session.cpp:4589:handler_status_CONNECTINGCLIENTSTATE_SERVER_HANDSHAKE(): [ERROR] ProxySQL Error: Access denied for user 'htr'@'172.21.0.35' (using password: YES)
2020-06-17 23:53:02 MySQL_Session.cpp:4589:handler_status_CONNECTINGCLIENTSTATE_SERVER_HANDSHAKE(): [ERROR] ProxySQL Error: Access denied for user 'htr'@'172.21.0.35' (using password: YES)
Received malformed line (no colon). Closing connection.
Error processing request (HTTP response code is 400 (<html><head><title>Request malformed</title></head><body>Your HTTP request was syntactically incorrect.</body></html>')). Closing connection. Received malformed line (no colon). Closing connection. Error processing request (HTTP response code is 400 (
@DBA-Ray: from the input you provided, there is no evidence that proxysql is idle, actually the opposite. Seems more like someone is attacking proxysql on multiple ports, including webui
@renecannao Thanks a lot.Someone is indeed scanning my server.I was just notified.
Hi @renecannao
Proxysql has been updated to 2.0.13, but the issue still persists. However, I'm able to produce extended processlist now. Here is proxysql stats. Hope it helps.
Ubuntu 16.04 LTS, proxysql 2.0.6, percona 5.7.26-29-1.xenial
The proxysql instance is installed on the web servers and is not currently in use - It's monitoring 2 databases, master and slave, but nothing is being sent through it. Load average is around 16-18 according to top, CPU usage is at 150% and VIRT is 4100008 and growing. The other web server has VIRT at 5107620 and growing. Both servers have 2 CPUs and 4Gb of RAM. Similar errors in logs on both servers:
Followed by:
There are lots of monitor users connected to the replica database, around 15 for each web server, which is unusual. Only 2 users per server on master.
Config:
Restarting proxysql daemon brings servers back to under 1 LA. Another set of servers that we have are doing just fine and they are actually routing via proxysql. Low CPU usage but VIRT is at 15.762g. On UAT, proxysql has non-existant CPU usage and only 174948 VIRT. All of these servers and their backends are virtually identical. Proxysql is deployed via ansible and the settings are also identical across the board. Please let me know if I've missed something.