Home > database >  Illicit computer after shutdown, boot mysql won't start, prompt 1053 error.
Illicit computer after shutdown, boot mysql won't start, prompt 1053 error.

Time:10-25

Windows illegal shutdown, restart mysql, shows a 1053 error, modify the login permissions, too, has been an error,

The 2017-03-27 T05:35:43. 948253 z 0 [Warning] option 'max_allowed_packet: unsigned value 4 adjusted to 1024
The 2017-03-27 T05:35:43. 948253 z 0 [Warning] option 'max_allowed_packet: unsigned value 2097152000 adjusted to 1073741824
The 2017-03-27 T05:35:43. 948253 z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Do use - explicit_defaults_for_timestamp server option (see documentation for more details).
The 2017-03-27 T05:35:43. 948253 z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO SQL modes should be 2 with strict mode. They will be merged with strict mode in a future release.
The 2017-03-27 T05:35:43. 948253 z 0 [Note] mysqld. Exe (mysqld 5.7.9 - log) starting as the process of 692...
The 2017-03-27 T05:35:43. 963877 z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions provides
The 2017-03-27 T05:35:43. 979694 z 0 [Note] InnoDB: Uses the event mutexes
The 2017-03-27 T05:35:43. 979694 z 0 [Note] InnoDB: _mm_lfence () and _mm_sfence () are 2 for the memory barrier
The 2017-03-27 T05:35:43. 979694 z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
The 2017-03-27 T05:35:43. 979694 z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
The 2017-03-27 T05:35:43. 995146 z 0 [Note] InnoDB: Number of pools: 1
The 2017-03-27 T05:35:43. 995146 z 0 [Note] InnoDB: Not using CPU crc32 instructions
The 2017-03-27 T05:35:44. 167004 z 0 [Note] InnoDB: Initializing buffer pool, the total size=8 m, the instances=1, the chunk size=8 m
The 2017-03-27 T05:35:44. 167004 z 0 [Note] InnoDB: Completed initialization of buffer pool
The 2017-03-27 T05:35:44. 198253 z 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
The 2017-03-27 T05:35:44. 198253 z 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
The 2017-03-27 T05:35:44. 198253 z 0 [ERROR] InnoDB: Plugin initialization aborted with ERROR Generic ERROR
The 2017-03-27 T05:35:44. 323253 z 0 [ERROR] Plugin 'InnoDB init function returned ERROR.
The 2017-03-27 T05:35:44. 323253 z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
The 2017-03-27 T05:35:44. 338877 z 0 [ERROR] Failed to initialize the plugins.
The 2017-03-27 T05:35:44. 338877 z 0 [ERROR] Aborting

The 2017-03-27 T05:35:44. 370131 z 0 [Note] Binlog end
The 2017-03-27 T05:35:44. 401380 z 0 [Note] Shutting down the plugin 'CSV'
The 2017-03-27 T05:35:44. 463880 z 0 [Note] mysqld. Exe: Shutdown is complete

CodePudding user response:

Normal before, that is not usually ibdata1 permissions itself, can try to begin ib_logfile files (usually two) change a name, and then see if you can start up, if you can start,

CodePudding user response:

Name, please
  • Related