Description

Hello, I have a problem, it has not occurred before. Today I bought a second dedicated server, and installed a proxy (velocity) on it. After installation, the server began to hang and cause this error in the proxy console.

I set these values in the MariaDB config:
set global max_connections = 99999;
SET GLOBAL wait_timeout = 57600;
SET SESSION wait_timeout = 57600;

Console error:
'''
luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mariadb.MariaDbConnection@14403e2a ((conn=1019) Connection.setNetworkTimeout cannot be called on a closed connection). Possibly consider using a shorter maxLifetime value.
'''

Reproduction Steps

1. Buy 2 dedicated servers.
2. Create servers with Spigot on the first dedicated server
3. Create a server with a Proxy (velocity) on the second dedicated server
4. Connect everything to MariaDB, which will be located on the first dedicated server (server with Spigot)
5. Let players into the server and wait 5 minutes

Expected Behaviour

The server is lag-free, because of this error, the server is constantly pinging (players have 3-5 thousand pings during the error playback)

Server Details

Velocity 3.1.2

LuckPerms Version

5.4.54

Logs and Configs

https://pastes.dev/Iifp4saEea

Extra Details

No response

LP's Discord is one of the most active I'm in. We aren't intentionally ignoring you, most likely your question simply got buried and needed to be resent for us to see it.

And yes, you're correct, Luck does only respond to issues every now and then. The issue tracker isn't intended to be a support channel, it's intended for tracking issues and feature requests, which are more reasonable to have a longer turnaround time for,

Can you help me? I beg
What I just didn't do, and deleted the drivers from the vehicle, and changed the value of "maxlifetime" to 1800. Nothing helps me, the error is the same

I just don't know what to do. I've been suffering with this bug for a week, and the server should already be open...

@lucko

Please don't just ping Luck. You can find our documentation for this error here.

If you would like faster support, try our Discord.

Please don't just ping Luck. You can find our documentation for this error here.

If you would like faster support, try our Discord.

No one answers me, and according to the history in the github, it is clear that the developer rarely comes here

LP's Discord is one of the most active I'm in. We aren't intentionally ignoring you, most likely your question simply got buried and needed to be resent for us to see it.

And yes, you're correct, Luck does only respond to issues every now and then. The issue tracker isn't intended to be a support channel, it's intended for tracking issues and feature requests, which are more reasonable to have a longer turnaround time for,

I have solved the problem! It turns out that there was not enough power on the server with the database! The processor could not withstand the load and as a result, the database turned on and off.