How do I fix database errors like "Too many connections", timeouts, or corruption?
Most database errors trace back to one of two things: how your plugins and apps handle connections, or an unclean shutdown. This article covers the three you'll see most — "Too many connections," timeouts, and corruption.
The usual causes
Connection-handling problems produce "too many connections" and timeout errors, while a forced or killed shutdown mid-write is what corrupts tables. Each has a straightforward fix.
Fixing common errors
- "Too many connections": a plugin or app is opening too many — check its pool settings, and don't run duplicate instances.
- Timeouts: keep queries light and ensure the app closes connections; reconnect logic helps.
- Corruption after a forced/kill shutdown: prefer a clean Stop over Kill, and restore from an export if a table is damaged.
Warning: Killing a server mid-write can corrupt both world files and database tables — use a graceful Stop whenever possible.
Frequently asked questions
"Too many connections" keeps coming back — what do I do? Reduce the plugin's connection pool size, or consolidate duplicate apps hitting the same database.
One of my tables is corrupted — can I recover it? Restore it from your latest database export. Keeping regular exports makes this painless.