Mysql Crash

[Vegaz 3]

Hello.
I have uploaded files to a VPS server and MYSQL turns on and after 1-2 seconds it shuts down and does a Crash.

Someone can explain to me where the problem could be?
On VirtualBox it goes without any problem but when I moved the server to VPS it doesn't work.

 

vps15452.htvps.pl.err

230602 17:51:15 mysqld_safe Logging to '/var/db/mysql/vps15452.htvps.pl.err'.
230602 17:51:15 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
230602 17:51:15 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
230602 17:51:16 [Note] /usr/local/libexec/mysqld (mysqld 5.5.62) starting as process 724 ...
230602 17:51:16 InnoDB: The InnoDB memory heap is disabled
230602 17:51:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230602 17:51:16 InnoDB: Compressed tables use zlib 1.2.11
230602 17:51:16 InnoDB: Initializing buffer pool, size = 128.0M
230602 17:51:16 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
230602 17:51:16 [ERROR] Plugin 'InnoDB' init function returned error.
230602 17:51:16 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
230602 17:51:16 [ERROR] Unknown/unsupported storage engine: InnoDB
230602 17:51:16 [ERROR] Aborting

230602 17:51:16 [Note] /usr/local/libexec/mysqld: Shutdown complete

230602 17:51:16 mysqld_safe mysqld from pid file /var/db/mysql/vps15452.htvps.pl.pid ended
230602 17:53:02 mysqld_safe Logging to '/var/db/mysql/vps15452.htvps.pl.err'.
230602 17:53:02 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
230602 17:53:02 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
230602 17:53:02 [Note] /usr/local/libexec/mysqld (mysqld 5.5.62) starting as process 972 ...
230602 17:53:02 InnoDB: The InnoDB memory heap is disabled
230602 17:53:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230602 17:53:02 InnoDB: Compressed tables use zlib 1.2.11
230602 17:53:02 InnoDB: Initializing buffer pool, size = 128.0M
230602 17:53:02 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
230602 17:53:02 [ERROR] Plugin 'InnoDB' init function returned error.
230602 17:53:02 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
230602 17:53:02 [ERROR] Unknown/unsupported storage engine: InnoDB
230602 17:53:02 [ERROR] Aborting

230602 17:53:02 [Note] /usr/local/libexec/mysqld: Shutdown complete

230602 17:53:02 mysqld_safe mysqld from pid file /var/db/mysql/vps15452.htvps.pl.pid ended

 

[[TiTAN] 32]

This is the hidden content, please

• Sign In
• or
• Sign Up

 

ChatGPT Say :

Quote

The error message you mentioned, "Plugin 'InnoDB' registration as a STORAGE ENGINE failed," typically occurs in database systems that use the InnoDB storage engine. The InnoDB engine is widely used in database management systems like MySQL.

There are a few potential causes and solutions for this error:

Missing or disabled plugin: The InnoDB storage engine may not be installed or enabled in your database system. You can verify this by checking the list of installed plugins or running a command to enable the InnoDB plugin if it's already installed.

Incompatible version: The version of the InnoDB storage engine you have installed might be incompatible with your database management system. In such cases, you might need to upgrade or downgrade either the InnoDB plugin or the database system itself to ensure compatibility.

Configuration issues: There could be configuration problems related to the InnoDB storage engine. Check your database configuration files (e.g., my.cnf for MySQL) to ensure that the necessary settings for InnoDB are correctly specified.

File system or disk space issues: If the underlying file system where your database resides has issues or if there is insufficient disk space, it can cause problems with the InnoDB storage engine. Ensure that your file system is healthy and has enough free space for the database to operate.

Corrupted installation: It's also possible that your InnoDB installation is corrupted or damaged. In such cases, you may need to reinstall or repair the InnoDB storage engine.

To troubleshoot and resolve this error, it's recommended to consult the documentation specific to your database management system, such as MySQL, and follow the guidelines provided there. Additionally, searching for the exact error message along with the name of your database system can often lead to forum threads or articles where others have encountered and resolved similar issues.