I restarted the server and now I can't start MySQLd service

galal3336 Hi Use the ssh tool to execute the command and check the mysql error log: cat /www/server/data/*.err|grep -i -C 10 error

aaPanel_Kern mysqld: File './mysql-bin.000025' not found (OS errno 2 - No such file or directory) 2023-07-25T02:42:46.623943Z 0 [ERROR] [MY-010958] [Server] Could not open log file. 2023-07-25T02:42:46.625214Z 0 [ERROR] [MY-010041] [Server] Can't init tc log 2023-07-25T02:42:46.627527Z 0 [ERROR] [MY-010119] [Server] Aborting 2023-07-25T02:42:47.662117Z 0 [System] [MY-010910] [Server] /www/server/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.24) Source distribution.

aaPanel_Kern solved by deleting ./mysql-bin.000025 thanks again

I have the same problem This is the log /www/server/mysql/bin/mysqld(+0x66df6e)[0x558e0d302f6e] /www/server/mysql/bin/mysqld(+0x66e453)[0x558e0d303453] /www/server/mysql/bin/mysqld( Z20buf_page_io_completeP10buf_page_tb+0x2d6)[0x558e0df67b56] /www/server/mysql/bin/mysqld(+0x12fca0c)[0x558e0df91a0c] /www/server/mysql/bin/mysqld( Z13buf_read_pageRK9page_id_tRK11page_size_t+0x73)[0x558e0df921b3] /www/server/mysql/bin/mysqld( Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x46f)[0x558e0df65c9f] /www/server/mysql/bin/mysqld( Z31trx_rseg_get_n_undo_tablespacesPm+0x13d)[0x558e0df0063d] /www/server/mysql/bin/mysqld(+0x1238523)[0x558e0decd523] /www/server/mysql/bin/mysqld( Z34innobase_start_or_create_for_mysqlv+0x2bd4)[0x558e0ded0c14] /www/server/mysql/bin/mysqld(+0x110185e)[0x558e0dd9685e] /www/server/mysql/bin/mysqld( Z24ha_initialize_handlertonP13st_plugin_int+0x59)[0x558e0d3905c9] /www/server/mysql/bin/mysqld(+0xc7d656)[0x558e0d912656] /www/server/mysql/bin/mysqld( Z40plugin_register_builtin_and_init_core_sePiPPc+0x1ec)[0x558e0d914a8c] /www/server/mysql/bin/mysqld( Z11mysqld_mainiPPc+0xb90)[0x558e0d33c380] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x14fb0a658d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x14fb0a658e40] /www/server/mysql/bin/mysqld(_start+0x25)[0x558e0d3316f5]

Hello, use the ssh tool to execute the command to see if there is any error? cat /www/server/data/*.err|grep -i -C 10 error jaac

Hello, this is not the latest log, the time of your server is incorrect? jaac

aaPanel_Kern Im not sure I was just run the command you gave to me

I suggest you check whether you have modified the mysql log configuration? Check the mysql log for errors jaac

MySQLd service failed to start (after restarting server)

aaP_olaniyi

aaPanel_Kern

Hello, what is your mysql version? Do you want to configure automatic deletion of configuration? Do you want to restart mysql after configuration?

aaP_olaniyi

jaac

aaPanel_Kern got error again 🙁

2023-09-26T04:02:51.321754Z 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2023-09-26T04:02:51.321912Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2023-09-26T04:02:51.321915Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2023-09-26T04:02:51.321939Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2023-09-26T04:02:51.321963Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.43-log) starting as process 9222 ...
2023-09-26T04:02:51.332264Z 0 [Note] InnoDB: PUNCH HOLE support available
2023-09-26T04:02:51.332304Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-09-26T04:02:51.332307Z 0 [Note] InnoDB: Uses event mutexes
2023-09-26T04:02:51.332310Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-09-26T04:02:51.332313Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-09-26T04:02:51.332446Z 0 [Note] InnoDB: Number of pools: 1

2023-09-26T04:02:51.332517Z 0 [Note] InnoDB: Using CPU crc32 instructions

2023-09-26T04:02:51.412394Z 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB.
2023-09-26T04:02:51.413321Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2023-09-26T04:02:51.413333Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2023-09-26T04:02:51.413746Z 0 [Note] InnoDB: Waiting for purge to start
2023-09-26T04:02:51.463949Z 0 [Note] InnoDB: 5.7.43 started; log sequence number 1876267808
2023-09-26T04:02:51.463973Z 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2023-09-26T04:02:51.464187Z 0 [Note] InnoDB: Loading buffer pool(s) from /www/server/data/ib_buffer_pool
2023-09-26T04:02:51.464376Z 0 [Note] Plugin 'FEDERATED' is disabled.
2023-09-26T04:02:51.464452Z 0 [Note] InnoDB: Buffer pool(s) load completed at 230926 4:02:51
mysqld: File './mysql-bin.000188' not found (Errcode: 2 - No such file or directory)
2023-09-26T04:02:51.465220Z 0 [ERROR] Failed to open log (file './mysql-bin.000188', errno 2)
2023-09-26T04:02:51.465227Z 0 [ERROR] Could not open log file
2023-09-26T04:02:51.465237Z 0 [ERROR] Can't init tc log
2023-09-26T04:02:51.465242Z 0 [ERROR] Aborting

2023-09-26T04:02:51.465270Z 0 [Note] Binlog end
2023-09-26T04:02:51.465323Z 0 [Note] Shutting down plugin 'ngram'
2023-09-26T04:02:51.465329Z 0 [Note] Shutting down plugin 'partition'
2023-09-26T04:02:51.465334Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2023-09-26T04:02:51.465338Z 0 [Note] Shutting down plugin 'ARCHIVE'
2023-09-26T04:02:51.465343Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2023-09-26T04:02:51.465446Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
2023-09-26T04:02:51.465452Z 0 [Note] Shutting down plugin 'MyISAM'
2023-09-26T04:02:51.465467Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'

aaPanel_Kern

jaac
Try to delete ./mysql-bin.000188 from the content of this /www/server/data/mysql-bin.index file, and then restart mysql. Can it be solved?
It can be operated in the "File" interface of the panel
cp /www/server/data/mysql-bin.index /www/server/data/mysql-bin.index_ /etc/init.d/mysqld restart

Execute the command Check out what mysql-bin files are in your directory
ls /www/server/data/mysql-bin*

jaac

aaPanel_Kern

I cant find this ./mysql-bin.000188

jaac

Ahhh found it! Thanks again aaPanel_Kern

Hilmi

2023-12-05 8:13:08 0 [Note] InnoDB: Completed initialization of buffer pool
2023-12-05 8:13:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1210674,1210674
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring malformed log record at LSN 1210674
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring corrupted file-level record at LSN 1210674
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring corrupted page identifier at LSN 1210674
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring malformed log record at LSN 1210692
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring malformed log record at LSN 1210692
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring unknown log record at LSN 1210722
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring unknown log record at LSN 1210722
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring unknown log record at LSN 1210722
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring unknown log record at LSN 1210722
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring unknown log record at LSN 1210722
2023-12-05 8:13:08 0 [Warning] InnoDB: Ignoring malformed log record at LSN 1210722
2023-12-05 8:13:08 0 [Note] InnoDB: At LSN: 1270601: unable to open file ./larapanel/#sql-alter-591f-1d7.ibd for tablespace 108
2023-12-05 8:13:08 0 [Note] InnoDB: At LSN: 1283573: unable to open file ./larapanel/#sql-ib123.ibd for tablespace 106
2023-12-05 8:13:08 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT at 1210674 between the checkpoint 1210674 and the end 2729257.
2023-12-05 8:13:08 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-12-05 8:13:08 0 [Note] InnoDB: Starting shutdown...
2023-12-05 8:13:09 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-12-05 8:13:09 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-12-05 8:13:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-12-05 8:13:09 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-12-05 8:13:09 0 [ERROR] Aborting
231205 08:13:09 mysqld_safe mysqld from pid file /www/server/data/fdserv3.pid ended

Hilmi

I had the same problem, mariadb suddenly stopped and couldn't be started again. please help me regarding this error. Thanks

aaPanel_Kern

Hello, the table space is damaged. It is recommended that you ask a recovery company to help you deal with it.

Hilmi

aaPanel_Kern Is there any other way to retrieve the database in it?

Hilmi

Is there any other way to retrieve the database in it?

aaPanel_Kern

This is a table space that is damaged and needs to be restored.

Hilmi

mgm

Unable To Restart sql server

2024-01-14T18:59:12.187277Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 703514910, calculated checksums for field1: crc32 703514910/2587999978, innodb 3079112754, none 3735928559, stored checksum in field2 4250423963, calculated checksums for field2: crc32 703514910/2587999978, innodb 4070943958, none 3735928559, page LSN 349 1410401772, low 4 bytes of LSN at page end 1410401753, page number (if stored to page already) 5, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a transaction system page
2024-01-14T18:59:12.187343Z 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2024-01-14T18:59:12.187348Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or, there was a failure in tagging the tablespace as corrupt.
2024-01-15 00:29:12 0x2b5621f9b340 InnoDB: Assertion failure in thread 47648937194304 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:59:12 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=0
max_threads=400
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2168044 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x60000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xecd2dc]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x79a356]
/lib64/libpthread.so.0(+0xf630)[0x2b5622195630]
/lib64/libc.so.6(gsignal+0x37)[0x2b5623b12387]
/lib64/libc.so.6(abort+0x148)[0x2b5623b13a78]
/www/server/mysql/bin/mysqld[0x76acd4]
/www/server/mysql/bin/mysqld(ZN2ib5fatalD1Ev+0xee)[0x10997be]
/www/server/mysql/bin/mysqld(Z20buf_page_io_completeP10buf_page_tb+0x3df)[0x10db77f]
/www/server/mysql/bin/mysqld(Z13buf_read_pageRK9page_id_tRK11page_size_t+0x4b2)[0x1108452]
/www/server/mysql/bin/mysqld(Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x3fd)[0x10d876d]
/www/server/mysql/bin/mysqld(Z31trx_rseg_get_n_undo_tablespacesPm+0x14e)[0x10797ae]
/www/server/mysql/bin/mysqld[0x10423b8]
/www/server/mysql/bin/mysqld(Z34innobase_start_or_create_for_mysqlv+0x3883)[0x1046d33]
/www/server/mysql/bin/mysqld[0xf136f8]
/www/server/mysql/bin/mysqld(Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7eadd1]
/www/server/mysql/bin/mysqld[0xcbf916]
/www/server/mysql/bin/mysqld(Z40plugin_register_builtin_and_init_core_sePiPPc+0x2e0)[0xcc5830]
/www/server/mysql/bin/mysqld[0x792b15]
/www/server/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0xd51)[0x7965d1]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2b5623afe555]
/www/server/mysql/bin/mysqld[0x78a4a4]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-01-14T19:00:39.080928Z 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2024-01-14T19:00:39.081092Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-01-14T19:00:39.081098Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2024-01-14T19:00:39.081126Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-01-14T19:00:39.081177Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.37-log) starting as process 16984 ...
2024-01-14T19:00:39.140572Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-01-14T19:00:39.140640Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-01-14T19:00:39.140644Z 0 [Note] InnoDB: Uses event mutexes
2024-01-14T19:00:39.140647Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-01-14T19:00:39.140651Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-01-14T19:00:39.140654Z 0 [Note] InnoDB: Using Linux native AIO
2024-01-14T19:00:39.141115Z 0 [Note] InnoDB: Number of pools: 1
2024-01-14T19:00:39.141247Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-01-14T19:00:39.144779Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2024-01-14T19:00:39.224010Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-14T19:00:39.244664Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-01-14T19:00:39.257695Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=5]. You may have to recover from a backup.
2024-01-14T19:00:39.257753Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):

aaPanel_Kern

mgm
Hello, I suggest you refer to this tutorial to see if it can be solved?
https://www.aapanel.com/forum/d/13216-mysqlmariadb-innodb-storage-engine-damage-solution

mgm

done issue solved

kibetem24

With my issue I didn't restart the server, it's a new server installation, mysqld can't seem to start.

aaPanel_Kern

Hello, is it OK to start manually? If not, check the mysql error log

kibetem24

I run bt 12 it fixed the issue

iskiie

how to fix?

aaPanel_Kern

Hi, have you done anything? Or did the server lose power? Prompt mysql-bin.000584 file does not exist
Try to delete ./mysql-bin.000584 from the content of this /www/server/data/mysql-bin.index file, and then restart mysql. Can it be solved?
It can be operated in the "File" interface of the panel
cp /www/server/data/mysql-bin.index /www/server/data/mysql-bin.index
/etc/init.d/mysqld restart

iskiie

« Previous Page Next Page »