-
problemHello, I am using an environment with 2 management servers, using MariaDB Galera as the database server. A few minutes after starting the management server service, the connection to the database is dropped, and the management server logs show the following record:
My current MariaDB server configuration is as follows:
And the configuration of access to the management servers database (db.properties) are these:
PS: I changed some parameters of both the database server (max_connections, max_allowed_packet and timeout parameters) and the connection pools in the db.properties file (db.cloud.maxActive, db.cloud.connectionTimeout, db.cloud.minIdleConnections), but none of them seem to have solved it, it just takes a little longer to interrupt. When I check the database server logs I can only get the following error records:
PS: I noticed that this started happening after installing cloudstack-usage, this same problem already occurred in a Standalone installation (without HA) of Cloudstack and it occurred precisely after installing cloudstack-usage, but I'm still debugging to find out if it is really related to the current problem. versionsCloudstack: 4.20 The steps to reproduce the bug
What to do about it?No response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
@Luskan777 , since mariadb 10 is mysql 5 compatible and ACS specifies mysql 8.0, this might be your issue. I am not sure if this true but worth a shot. |
Beta Was this translation helpful? Give feedback.
@weizhouapache and @DaanHoogland , it seems that the problem is in my HAproxy configuration. Since it is a MariaDB Galera, I use HAproxy to do load balancing between the database servers, which is common when using MariaDB Galera. It seems that HAproxy was closing the connections unexpectedly, which is why the MariaDB logs recorded the error (Got an error reading communication packets).
So, to solve the problem, I changed some HAproxy configuration parameters, such as maxconn and timeout.
In case someone else has the same problem one day, I will leave my current HAproxy configuration below.