A WordPress “Error establishing a database connection” message does not prove that MySQL crashed. First verify whether the mysqld process stopped, inspect the MySQL error log at the incident time, and only then choose a recovery path. Repeatedly rebooting or running a blanket table repair can destroy the evidence—or worsen data loss.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This runbook separates resource exhaustion, query-related failures, MyISAM corruption, InnoDB recovery failures, and WordPress code errors. Follow the branch that matches your logs.
As an Amazon Associate I earn from qualifying purchases.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallStart by proving what failed
MySQL’s official troubleshooting advice is to determine whether the mysqld server died or whether the problem is with the client connecting to it. A WordPress database error can also result from a bad credential, a socket or network problem, or a PHP/plugin failure while the database remains healthy.
Use a three-minute triage
- Record the time and symptom. Note the first failed request, HTTP status, WordPress message, and any monitoring alert. Do not restart the VPS yet unless it is completely unresponsive.
- Check the database service. On systemd distributions, run
sudo systemctl status mysql. Some systems use MariaDB or a different unit name, so trysudo systemctl status mariadbifmysqlis not found. - Check recent service events. Use
sudo journalctl -u mysql --since "30 minutes ago"(or the corresponding MariaDB unit). Capture the output before another restart. - Read the MySQL error log around the timestamp. Common locations include
/var/log/mysql/error.log, but the configured path differs by distribution and package. Look for the shutdown reason, InnoDB recovery messages, out-of-memory notices, disk or file errors, and stack traces. - Test again after evidence is captured. If the service is stopped, one controlled restart can show whether it starts cleanly. Record the exact result and any new log lines.
The error log is the most valuable first artifact. MySQL documents that it can reveal why mysqld exited and identifies corrupted data or index files as common causes of unexpected termination.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Capture evidence before changing anything
Make a dated copy of the relevant log lines and note your MySQL, Linux, PHP, and WordPress versions. Preserve the original files if possible; log rotation can remove the only record of a crash.
What to extract from the log
- The precise stop, restart, or startup-failure timestamp.
- “Out of memory,” “killed,” or allocation errors.
- “No space left on device,” read/write errors, filesystem errors, or permission failures.
- InnoDB crash-recovery or redo-log messages.
- MyISAM messages such as “Record file is crashed,” or references to a specific table.
- A repeatable query, assertion, or stack trace immediately before the process exits.
Save the complete error text when opening a support case. MySQL recommends preserving exact error output rather than paraphrasing it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check VPS resources and operating-system limits
Memory pressure, a full disk, exhausted file descriptors, and runaway processes are first-line checks in MySQL’s troubleshooting checklist. A small VPS can run WordPress normally and still fail during a backup, import, traffic spike, or plugin job.
Memory and processes
free -h
top
ps aux --sort=-%mem | head -n 20
ps aux --sort=-%cpu | head -n 20Look for almost no available memory, sustained swap activity, or one process consuming an unusual share of RAM or CPU. Correlate the time with the MySQL log. If the Linux kernel killed mysqld, the service may appear to have “randomly” restarted even though the operating system recorded the reason.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Disk capacity and inodes
df -h
df -iCheck the filesystem that contains the MySQL data directory, the error log, and temporary files—not only the root volume. A full filesystem can prevent writes to redo logs, temporary tables, binary logs, or the error log itself. Remove or rotate only files you have identified as safe; do not delete database files to make space.
File descriptors and runaway workers
ulimit -n
cat /proc/$(pidof mysqld)/limits | grep -i "open files"Compare the process limit with the workload and with any “too many open files” message. Also inspect queue workers, backup jobs, crawlers, and PHP processes that may be opening connections or files faster than they close them. Correct the underlying process or limit deliberately, then restart once during a maintenance window.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsMatch the log signature to the remedy
| Evidence | Most likely area | Data risk | Reversibility | First response |
|---|---|---|---|---|
| Kernel or MySQL out-of-memory message; memory exhausted | VPS capacity or runaway process | Usually low if no storage errors are present | High | Identify the memory consumer, reduce load, add capacity or swap according to your operating policy, then restart once |
| “No space left,” filesystem or write errors | Storage capacity, permissions, or filesystem health | Medium to high if writes were interrupted | Medium | Free verified-safe space, check the filesystem and permissions, and preserve logs |
| A repeatable statement immediately before each exit | Query behavior or a server bug triggered by that workload | Usually low, but the query may be damaging under load | High | Capture the query, enable query logging briefly on a controlled instance, and analyze it |
| MyISAM table or index corruption | Table files | High if repair is attempted without a backup | Medium to low | Back up first, identify affected tables, then check or repair only those tables |
| InnoDB recovery failure during startup | InnoDB files or recovery state | Very high | Low | Make a copy, follow the recovery-specific MySQL procedure, and avoid destructive experiments |
mysqld remains healthy but WordPress throws a fatal error |
Plugin, theme, PHP, or WordPress code | Usually low at the database layer | High | Use WordPress Recovery Mode and isolate the failing extension |
Branch 1: recover from memory, disk, or process exhaustion
When memory is the cause
Stop or reschedule the identified runaway job, reduce concurrent work, and verify that the VPS has enough headroom for MySQL, PHP workers, the web server, and the operating system together. If the log shows the kernel killed MySQL, correcting the memory pressure is more important than changing a MySQL setting. After the change, start the service and watch the log and memory use during the same workload that previously triggered the crash.
When the disk is full
Find the largest safe-to-remove logs, caches, or old backups outside the MySQL data directory. Rotate logs according to your distribution’s mechanism, then confirm free space with df -h. Check ownership and write permissions if the log shows a permission error. Never delete ibdata, redo logs, table files, or other files in the MySQL data directory simply to recover space.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
When a process or descriptor limit is exhausted
Fix the process that is leaking connections or files and review the service’s configured limits. A temporary restart can clear leaked resources, but it does not fix the cause. Record the before-and-after limits and keep the change reversible.
Branch 2: investigate a query that precedes every crash
If the same statement appears immediately before each exit, treat it as a query investigation rather than a table-repair problem. MySQL documents enabling the general query log when a repeatable query appears to kill the server and examining the final query before the restart.
Capture the statement safely
- Use a maintenance or otherwise controlled instance if possible.
- Enable the general query log only for the shortest period needed; it can generate substantial I/O and expose query contents.
- Reproduce the failure or wait for the known job, then save the final statements and disable the general log.
- Use the slow query log and
EXPLAINto analyze expensive statements when the evidence points to load rather than corruption.
Do not leave verbose query logging enabled indefinitely on a busy production VPS. If the statement is generated by a plugin, import, report, or scheduled task, pause that workload while you test a corrected query or update.
Branch 3: handle MyISAM corruption cautiously
Repair is appropriate only when the error log or table check points to affected MyISAM tables. A WordPress database-connection message alone is not evidence of MyISAM corruption.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Back up and identify the table
- Verify that a current, restorable database backup exists. If possible, take another backup before modifying the table.
- Record the database and table named in the error log.
- Check only the suspected table with the appropriate MySQL tooling. In SQL, that commonly means
CHECK TABLE table_name;; replacetable_namewith the identified table.
In phpMyAdmin, select the WordPress database, select the affected table, choose the maintenance or operations view, and use the check function before choosing repair. The exact labels vary by phpMyAdmin version.
Recommended Free Tools
Repair only confirmed corruption
Use REPAIR TABLE table_name; only for a confirmed MyISAM problem and only after the backup check. Review the result and the error log, then test the site. A blanket repair across every WordPress table can alter healthy data and will not fix an out-of-memory failure, an InnoDB recovery failure, or a stopped service.
Branch 4: treat InnoDB startup recovery as a separate incident
InnoDB recovery failures require the recovery-specific procedure in the MySQL manual, not a MyISAM repair. The priority is preserving the original files and creating a copy before attempting recovery.
- Stop repeated start attempts if each attempt changes the recovery state or overwrites useful log context.
- Make a filesystem-level copy or snapshot of the MySQL data directory according to your backup procedure.
- Keep the original copy untouched and work on a duplicate whenever possible.
- Do not delete InnoDB data files, redo logs, or tablespaces to force startup.
- Do not enable increasingly aggressive recovery modes without understanding their read-only and data-loss implications and having a rollback plan.
If the database contains irreplaceable data, involve an administrator experienced with InnoDB recovery before making changes. A successful start after a risky option is not proof that all data is intact; validate tables and restore from a known-good backup when necessary.
When MySQL is healthy but WordPress still fails
Once mysqld stays running and its logs are clean, stop treating the incident as a database crash. A plugin, theme, PHP fatal, or other WordPress code path may be failing while database connections remain available.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use Recovery Mode for a safe login
WordPress Recovery Mode is a temporary safe path intended to make the site accessible for troubleshooting a fatal error. Use the recovery link WordPress sends to an administrator, inspect the reported plugin or theme, and deactivate or isolate the component. Recovery Mode does not restart a stopped database service and should not be used as a substitute for fixing MySQL.
Correlate PHP and WordPress logs
On a controlled or maintenance instance, enable WordPress debugging in wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reproduce the failure, compare the WordPress/PHP timestamps with the MySQL error log, and save the relevant entries. Turn verbose debugging back off on public production after collecting the evidence; debug output can disclose paths, queries, and other sensitive details.
Verify the fix without losing the timeline
- Confirm the database service remains active through the workload that caused the failure.
- Check the error log for new shutdown, recovery, storage, or memory messages.
- Load the WordPress front end, administration area, and a database-backed action such as saving a post.
- Review PHP and WordPress logs for a separate fatal error.
- Keep the captured logs, commands, configuration changes, and exact timestamps with the incident record.
Prevent another VPS crash
- Maintain current backups. WordPress advises keeping a current database backup; test restoration rather than assuming a backup is usable.
- Monitor memory and disk. Alert before either reaches exhaustion, and include the filesystem containing MySQL data and logs.
- Review logs after updates. Check MySQL, PHP, and WordPress logs after changing plugins, themes, PHP, MySQL, or the operating system.
- Document versions. Record exact MySQL or MariaDB, Linux, PHP, and WordPress versions so a crash can be reproduced and reported accurately.
- Control expensive jobs. Schedule imports, backups, reports, and crawlers so they do not collide on a small VPS; investigate recurring queries instead of masking them with repeated restarts.
- Keep a recovery plan. Know where the error log and data directory are, which service unit starts the database, who can approve a repair, and how to restore the last known-good backup.
A practical decision checklist
Use this order when the site reports a database connection failure:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
- Is
mysqldrunning? If not, capture status, journal, and error-log output. - Does the log name memory, disk, descriptors, or a runaway process? Correct that condition first.
- Does the same query precede each exit? Capture it with temporary query logging and analyze it.
- Does the log identify MyISAM corruption? Back up, check the named table, and repair only that table.
- Does startup fail during InnoDB recovery? Preserve a copy and use the recovery-specific procedure; do not delete files.
- Is MySQL stable but WordPress still fatal? Use Recovery Mode, isolate the plugin or theme, and correlate WP/PHP logs.
- After recovery, test under the original workload and document what changed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
