Restart MySQL
This page explains how to restart the MySQL/MariaDB database service in GoAdmio. The database server powers every hosted application that stores data — WordPress, Joomla, Drupal, e-commerce stores, CRMs, and custom apps.
Location: Admin Panel → Restart Services → MySQL Server
Overview
MySQL (or MariaDB, its drop-in replacement) runs as a system service on the server. It stores all databases and serves queries from PHP applications, scripts, and the panel itself.
Restarting MySQL:
- Reloads the database configuration (
my.cnf/mariadb.cnf) - Recovers from a crashed or hung database server
- Applies new settings (buffer sizes, connection limits, etc.)
- Clears stuck connections and locks
- Rebuilds InnoDB crash recovery if the server shut down uncleanly
When to Restart MySQL
Restart MySQL after:
| Change | Why |
|---|---|
| Editing my.cnf | Applies new database settings |
| Changing buffer pool size, max connections, etc. | Requires a restart (most settings do) |
| Installing or removing a database extension | Loads the new module |
| MySQL is not responding | Recovers a hung or crashed server |
| Too many connections | Clears stuck connections |
| A database is locked | Releases locks held by stuck queries |
| After restoring a large database | Applies the new data and clears the cache |
| After a server crash | InnoDB crash recovery runs on startup |
> Tip: For configuration changes, some settings support SET GLOBAL at runtime — no restart needed. But most buffer sizes and file locations require a restart. Check the MySQL documentation for the specific setting.
How to Restart MySQL via the Panel
- Log in to the GoAdmio Admin Panel.
- Navigate to Restart Services.
- Locate MySQL Server.
- Click Restart.
- Confirm if prompted.
- Wait for MySQL to come back up — typically 5–30 seconds.
Verify the restart
- Open Service Status — confirm MySQL is running. See Service Status.
- Visit a site that uses a database — confirm it loads.
- Open phpMyAdmin or Adminer — confirm you can connect.
- Check the MySQL error log: