Skip to content

Instantly share code, notes, and snippets.

@CodeNinjaUG
Created January 22, 2024 14:09
Show Gist options
  • Save CodeNinjaUG/388db97205905d9004c83a5b5a554e10 to your computer and use it in GitHub Desktop.
Save CodeNinjaUG/388db97205905d9004c83a5b5a554e10 to your computer and use it in GitHub Desktop.
Setting the Mysql For Hostinger VPS
```It seems like there are issues with the InnoDB storage engine and the inability to lock the `ibdata1` file. This can be a common problem when the MySQL server is not shut down properly, or there are permission issues.
Here are some steps you can take to resolve this issue:
1. **Stop MySQL Service:**
```
sudo service mysql stop
```
2. **Backup Existing Data:**
Before making any changes, it's a good idea to back up your existing MySQL data.
3. **Check and Correct Ownership and Permissions:**
Ensure that the MySQL data directory and files have the correct ownership and permissions. The MySQL data directory is typically `/var/lib/mysql`. The owner should be the MySQL user, and the permissions should allow the MySQL user to read and write.
```
sudo chown -R mysql:mysql /var/lib/mysql
```
4. **Remove `ibdata1` and `ib_logfile*` Files:**
```
sudo rm /var/lib/mysql/ibdata1
sudo rm /var/lib/mysql/ib_logfile*
```
5. **Start MySQL in Recovery Mode:**
Start MySQL in recovery mode to recreate the necessary files.
```
sudo mysqld --innodb_force_recovery=1
```
6. **Stop MySQL:**
```
sudo service mysql stop
```
7. **Remove `ibdata1` and `ib_logfile*` Again:**
```
sudo rm /var/lib/mysql/ibdata1
sudo rm /var/lib/mysql/ib_logfile*
```
8. **Start MySQL:**
```
sudo service mysql start
```
9. **Check MySQL Error Log:**
Examine the MySQL error log to see if there are any further issues.
```
sudo tail -n 50 /var/log/mysql/error.log
```
If the issue persists, you may need to consider more advanced recovery options or restoring from a backup. Please be cautious when performing these steps, and if possible, consult MySQL documentation or seek the assistance of a database administrator.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment