I'm getting error, and i can't start the MySQL service. This server i have using since 3 years without any issue. Please see the below MySQL error log.
2019-05-21 14:41:39 6796 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO student (program_id, batch_id,counselor_id,center_id,
center_code,program_code,title, sex, full_name, first_name, last_name,
name_with_initials, name_to_be_appear,
contact_number_mobile, contact_number_home, contact_number_office,
email, fax, address, NIC_number, passport_number, nationality, religion, date_of_birth, photo,
status,registration_number, password,payment_option_id,discount,discount_reason,inquiry_id, added_date, added_by,module_exempted_status)
SELECT program_id, batch_id, counselor_id, center_id,
InnoDB: Error: trying to access page number 4294958335 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2019-05-21 14:41:39 1b2c InnoDB: Assertion failure in thread 6956 in file fil0fil.cc line 5591
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [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: [dev.mysql.com]
InnoDB: about forcing recovery.
2019-05-21 14:41:39 6796 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO student (program_id, batch_id,counselor_id,center_id,
center_code,program_code,title, sex, full_name, first_name, last_name,
name_with_initials, name_to_be_appear,
contact_number_mobile, contact_number_home, contact_number_office,
email, fax, address, NIC_number, passport_number, nationality, religion, date_of_birth, photo,
status,registration_number, password,payment_option_id,discount,discount_reason,inquiry_id, added_date, added_by,module_exempted_status)
SELECT program_id, batch_id, counselor_id, center_id,
InnoDB: Error: trying to access page number 4294958335 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2019-05-21 14:41:39 1b2c InnoDB: Assertion failure in thread 6956 in file fil0fil.cc line 5591
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [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: [dev.mysql.com]
InnoDB: about forcing recovery.