Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug report: MySQL Too Many Connections #118

Open
nicholasveronico opened this issue Feb 12, 2023 · 2 comments
Open

Bug report: MySQL Too Many Connections #118

nicholasveronico opened this issue Feb 12, 2023 · 2 comments
Labels
bug Unintended functionality that requires an update to fix resolved-in-dev-branch Issues that have been corrected in the dev branch but that are not released

Comments

@nicholasveronico
Copy link

Bug description:

Upon executing /irp forcebackup all, the console spams with a SQL error stating that too many connections are open.

Server details:

  • Server type & version: Purpur 1.19.3
  • InventoryRollbackPlus version: v1.6.8

How to reproduce:

  1. Run /irp forcebackup all (May require you to run twice a few seconds apart for it to trigger)

What was expected:

It is expected that the backups will be completed without opening too many connections.

Screenshots, logs & other:

https://pastebin.com/9gYFfvWB

Additional info:

I don't know if this will be easily reproducible. This occurs on a network where there are 100+ players that are being force-backed up.

@nicholasveronico nicholasveronico added the bug Unintended functionality that requires an update to fix label Feb 12, 2023
@nicholasveronico
Copy link
Author

Hello. I was wondering if there are any updates on this issue.

Thank you.

@TechnicallyCoded
Copy link
Owner

Current structure would not allow these changes for a fix without crazy changes
I am going to re-write the plugin soon(tm) which will allow much better version support and fine-grain control over this stuff.

@TechnicallyCoded TechnicallyCoded added the resolved-in-dev-branch Issues that have been corrected in the dev branch but that are not released label Dec 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended functionality that requires an update to fix resolved-in-dev-branch Issues that have been corrected in the dev branch but that are not released
Projects
None yet
Development

No branches or pull requests

2 participants