Issues with connection to mysql databases
Hi all, I run a pvp server which averages around ~20 or so players with about 55 plugins on a pretty powerful computer with 20gb of ram and 4 7950x threads, we recently (about 6 months ago) migrated out databases from the ones provided by our host to our own virtual machine with OVH with 2gb of ram, and 40gb of storage which seemed to work fine 6 months ago, however now we constantly get connection closed database errors from our plugins Strike practice, Luckperms, Litebans and PVP stats (PVP stats had to completely remove as occasionally when someone joined it would completely crash the server attempting to make a connection with the database). We usually have about 30 connections to the mysql database with average traffic of about 6KB/s and our VPS never has cpu spikes with the ram always sitting at 700mb used of 2gb (700 being the size of all our databases combined) just wanted to check if anyone else had run into similar issues with their mysql databases and if they had any solves, thanks!
13 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by what11.#0
genuinely curious why you migrated your databases off the host's
just seems like you're asking for issues
We originally used databases provided by sparked host which were causing issues back then as well (constant connections issues which would bring the server to a halt) and we assumed it was an issue on their end as their myphpadmin was incredibly slow (didnt really have any other way of benchmarking) we then moved to our own vps so we would have significantly more head room and control which seemed to fix the problem at the time, pretty much getting no connections errors / issues but for some reason in the last month or so the errors have come back even worse than before
seems like ur either, using a poor host, or ur plugins are causing the issues. so doesnt matter if u use ur own db, or sparkeds db
ur also routing non-minecraft specific traffic outside of sparkeds network which can potentially cause issues
This is why you use DuckDB
Also on this after looking back on some messages I remembered that they would just have complete outages that wouldn't be resolved from hours to days so we wanted something that we could completely control (we have had no complete outages on our own vps)
Sorry, you have been blocked
You are unable to access sparkedhost.comSeems like they don't like Proton š
Oh interesting, I didnt realise that was a potential issue, it's still strange that when we intially migrated it wasnt causing issues and now it seems to have flamed up again
What MySQL server are you using
Pure MySQL or just something like Maria
pure mysql I believe
is there a command I could use to verify this?
mysql -v iirc
if it doesn't work try --version
oh nvm, it's mysql -V (capital V)
