Skip to content
Update MySQL Errors authored by Ruan's avatar Ruan
...@@ -76,7 +76,7 @@ _Cause: Connection timed out: connect_ / _Cause: connect timed out_ ...@@ -76,7 +76,7 @@ _Cause: Connection timed out: connect_ / _Cause: connect timed out_
_Can't connect to MySQL server on ... (110)_ _Can't connect to MySQL server on ... (110)_
If the Minecraft server and the MySQL database are running on two separate servers, make sure that port 3306 is allowed in the firewall of the database server, and make sure that the MySQL server is bound to 0.0.0.0 or its external IP (not to localhost) If the backend/proxy server and the MySQL database are running on two separate servers, make sure that port 3306 is allowed in the firewall of the database server, and make sure that the MySQL server is bound to 0.0.0.0 or its external IP (not to localhost)
See [#How to enable remote connections?](https://gitlab.com/ruany/LiteBans/-/wikis/MySQL-Errors#how-to-enable-remote-connections) See [#How to enable remote connections?](https://gitlab.com/ruany/LiteBans/-/wikis/MySQL-Errors#how-to-enable-remote-connections)
...@@ -270,7 +270,7 @@ If this is caused by hardware, you will need to replace the device that causes t ...@@ -270,7 +270,7 @@ If this is caused by hardware, you will need to replace the device that causes t
### Connection pool exhaustion detected: ### Connection pool exhaustion detected:
This generally indicates that the Minecraft server or the database server is overloaded and doesn't have enough CPU power available to serve the active requests. This generally indicates that the backend server or the database server is overloaded and doesn't have enough CPU power available to serve the active requests.
LiteBans is multithreaded and can use a configurable amount of CPU cores - the option `max_connections` decides the upper limit (10 by default). If the database server has free CPU available, it is recommended to increase `max_connections` to `((physical CPU cores)*2)+2`, while `+2` can be increased up to `+10` depending on network and disk latency (higher latency = more connections). LiteBans is multithreaded and can use a configurable amount of CPU cores - the option `max_connections` decides the upper limit (10 by default). If the database server has free CPU available, it is recommended to increase `max_connections` to `((physical CPU cores)*2)+2`, while `+2` can be increased up to `+10` depending on network and disk latency (higher latency = more connections).
... ...
......