MySQL error spam
RhythmicSys opened this issue ยท 6 comments
There has been a consistent issue on my server that I'm getting, where CoreProtect seems to be having an issue with MySQL
The previous issues with this that I've seen on the discord, seem to be related to trying to purge large amounts of information, but these errors have not seemed to coincide with any events that I can tell.
Latest startup log
Errors specifically (the file was too large for pastebin)
/co status:
----- CoreProtect -----
Version: CoreProtect v21.3.
License: Invalid donation key. (Please check config.yml)
Database: Using MySQL. (Initial DB: 21.3)
WorldEdit: Integration enabled.
Consumer: 2 items in queue.
Discord: www.coreprotect.net/discord/
Patreon: www.patreon.com/coreprotect/
Server version: git-Purpur-1888 (MC: 1.19.3)
This is unfortunately continuing to be a major issue, and although I would like to just switch off MySQL, that's a lot of data I don't really want to lose.
Logs from Jan 9, 2023
Logs from Jan 10, 2023
Logs from Jan 12, 2023
Logs from Jan 16, 2023
Logs from Jan 18, 2023
Logs from Jan 21, 2023
Logs from Jan 24, 2023
Logs from Jan 26, 2023
There are no options for someone who uses a hosting site to modify how much the database can take in at once, and unless I'm mistaken, there's no options in the config either.
These are the database options on bloom host, that I have
The only modifiable option is the Allowed Connections tab. There is nowhere for me to edit anything more advanced than that.
If this issue is already being addressed I apologize for pushing it, but it currently seems to be dismissed, and this seems like something that could be addressed within the plugin
I advise you contact your host for support regarding their services.
You're correct that this is abnormal, but the issue here isn't on CoreProtects end.
The total number of locks exceeds the lock table size
https://major.io/2010/02/16/mysql-the-total-number-of-locks-exceeds-the-lock-table-size-2/
Okay yeah I read that when I looked up the question on the discord.
But I don't have access to the internals of the database, and to my knowledge, nothing should be removing or deleting a ton of information from there. The only connection on that database is CoreProtect, and I have around 4 concurrent players, the entire DB is 2.5GB in size.
There should be no operations that are clogging it, and yet it's giving me this wall of errors daily.
Is there a setting in the CP config that I've missed that limits how much info can be sent/removed to/from the database at a time? Because that's not something I have control over from the database side.
I would at least like to know what's causing the issue- other than "too much information is being sent/removed at once" - because yeah, I got that. But I don't know why, and considering my server is very small, with very few players, it doesn't seem like it should be happening by normal use.
