Why is my MariaDB server in the wrong location?
If errors like this occur, then critical system tables are either missing or are in the wrong location. The above error is quite common after an upgrade if the option files set the basedir or datadir to a non-standard location, but the new server is using the default location.
Why does the option file stop working in MariaDB?
However, occasionally, options are removed in new versions of MariaDB, or the valid values for options are changed in new versions of MariaDB. Therefore, it’s possible for an option file to stop working after an upgrade. Also remember that option names are case sensitive.
What to do if InnoDB crashes the server?
If InnoDB crashes the server after detecting data corruption, it writes a detailed message in the error log. The first lines are similar to the following: InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 7. InnoDB: You may have to recover from a backup.
What happens if InnoDB cannot allocate memory?
If it cannot allocate memory, InnoDB will use the disk’s swap area, which is very bad for performance. If swapping is disabled or the swap area is not big enough, InnoDB will crash. In this case, MariaDB will probably try to restart several times, and each time it will log a message like this:
Why does InnoDB crash when it detects table corruption?
The operating system also needs memory. By default, InnoDB deliberately crashes the server when it detects table corruption. The reason for this behavior is preventing corruption propagation. However, in some situations, server availability is more important than data integrity.
What to do if InnoDB doesn’t start?
But be very careful: don’t assign to the buffer pool more memory than it can allocate. If it cannot allocate memory, InnoDB will use the disk’s swap area, which is very bad for performance. If swapping is disabled or the swap area is not big enough, InnoDB will crash.