My SQL Service not starting

rndsolutions

When I start the Service, it fails.

I have run folowing

root@WD180188231140rndsolutionsingmailcom7m2xO:~# systemctl status mysqld.servic e
× mysqld.service - LSB: start and stop MariaDB
Loaded: loaded (/etc/init.d/mysqld; generated)
Active: failed (Result: exit-code) since Fri 2025-11-28 07:49:14 +01; 1min>
Docs: man:systemd-sysv-generator(8)
Process: 15570 ExecStart=/etc/init.d/mysqld start (code=exited, status=1/FA>
CPU: 1.296s

Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: Starting >
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: Starti>
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15691]: 251128>
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15691]: 251128>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: ./etc/>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: ERROR!
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.se>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.se>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: Failed to>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.se>
lines 1-17/17 (END)

Please resolve the issue

rndsolutions

root@WD180188231140rndsolutionsingmailcom7m2xO:~# sudo systemctl status mysql
× mysqld.service - LSB: start and stop MariaDB
Loaded: loaded (/etc/init.d/mysqld; generated)
Active: failed (Result: exit-code) since Fri 2025-11-28 07:49:14 +01; 7min ago
Docs: man:systemd-sysv-generator(8)
Process: 15570 ExecStart=/etc/init.d/mysqld start (code=exited, status=1/FAILURE)
CPU: 1.296s

Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: Starting LSB: start and stop MariaDB...
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: Starting MariaDB.
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15691]: 251128 07:49:12 mysqld_safe Logging to '/www/server/data/WD18>
Nov 28 07:49:12 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15691]: 251128 07:49:12 mysqld_safe Starting mariadbd daemon with dat>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: ./etc/init.d/mysqld: line 264: kill: (15691) - No such process
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO mysqld[15570]: ERROR!
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.service: Control process exited, code=exited, status=1/FA>
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.service: Failed with result 'exit-code'.
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: Failed to start LSB: start and stop MariaDB.
Nov 28 07:49:14 WD180188231140rndsolutionsingmailcom7m2xO systemd[1]: mysqld.service: Consumed 1.296s CPU time.
lines 1-17/17 (END)

aaPanel_Kern

Hello, I suggest you check the mysql log, what is the reason
You can also use this command to check: curl -k https://www.aapanel.com/script/mysql_check.sh | bash

rndsolutions

Can I give you SSH access?

rndsolutions

2025-11-28 9:09:04 0 [Warning] You need to use --log-bin to make --binlog-format work.
2025-11-28 9:09:04 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2025-11-28 9:09:04 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-11-28 9:09:04 0 [Note] InnoDB: Number of transaction pools: 1
2025-11-28 9:09:04 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-11-28 9:09:04 0 [Note] InnoDB: Initializing buffer pool, total size = 512.000MiB, chunk size = 8.000MiB
2025-11-28 9:09:04 0 [Note] InnoDB: Completed initialization of buffer pool
2025-11-28 9:09:04 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2025-11-28 9:09:05 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1415295835
2025-11-28 9:09:06 0 [Note] InnoDB: End of log at LSN=1524147506
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1609 was not found at ./sql_camongo_in/wp_comments.ibd.
2025-11-28 9:09:06 0 [Note] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1628 was not found at ./sql_camongo_in/wp_options.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1629 was not found at ./sql_camongo_in/wp_postmeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1630 was not found at ./sql_camongo_in/wp_posts.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1640 was not found at ./sql_camongo_in/wp_usermeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1641 was not found at ./sql_camongo_in/wp_users.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1764 was not found at ./sql_radiumgroup_in/wp_comments.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1775 was not found at ./sql_radiumgroup_in/wp_options.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1776 was not found at ./sql_radiumgroup_in/wp_postmeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1777 was not found at ./sql_radiumgroup_in/wp_posts.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1801 was not found at ./sql_radiumgroup_in/wp_usermeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1849 was not found at ./sql_theprofilepick_com/wp_options.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1850 was not found at ./sql_theprofilepick_com/wp_postmeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1851 was not found at ./sql_theprofilepick_com/wp_posts.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1852 was not found at ./sql_theprofilepick_com/wp_term_relationships.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1853 was not found at ./sql_theprofilepick_com/wp_term_taxonomy.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1856 was not found at ./sql_theprofilepick_com/wp_usermeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1913 was not found at ./sql_radiumgaming_in/wp_options.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1914 was not found at ./sql_radiumgaming_in/wp_postmeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1915 was not found at ./sql_radiumgaming_in/wp_posts.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1928 was not found at ./sql_radiumgaming_in/wp_usermeta.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Tablespace 1929 was not found at ./sql_radiumgaming_in/wp_users.ibd.
2025-11-28 9:09:06 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found
2025-11-28 9:09:06 0 [Note] InnoDB: Starting shutdown...
2025-11-28 9:09:06 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2025-11-28 9:09:06 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-11-28 9:09:06 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2025-11-28 9:09:06 0 [ERROR] Aborting
251128 09:09:06 mysqld_safe mysqld from pid file /www/server/data/WD180188231140rndsolutionsingmailcom7m2xO.pid ended

It's a long Log. From there, I am giving the last portion

aaPanel_Kern

Hello, after making a snapshot backup of the server, refer to the documentation to try to repair it.
https://www.aapanel.com/docs/Function/Tutorial/Mysql_Mariadb_Innodb_Storage_Engine_Damage_Solution.html

rndsolutions

If you want SSH access, then I can provide it. You just give me the Database backup, and I will reinstall the server.

rndsolutions

How to take snapshot backup?

rndsolutions

Can I take a backup from Settings ?

aaPanel_Kern

Create snapshot backup in server provider

rndsolutions