CMSV6Help Center
/
839 DOCS · 211 VIDEOS中文

The MySQL service cannot be started normally when the server software is newly deployed.

Author daiweiqiangUpdated 2026-08-12 13:47:00Doc ID 2709404 words · 2 min readView original ↗

1. Functional Description

Solve the problem that some MySQL services cannot start normally

2. Operating Instructions

2.1 Problem Description

When the software installation wizard interface creates the database file, the MySQL service cannot be started and the next step cannot be performed.
- mysql error log shows:
2023- 10- 19T09:53:28.071961Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023- 10- 19T09:53:28.072087Z 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- 10- 19T09:53:28.072110Z 0 [Warning] Insecure configuration for -- secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non- empty path.
2023- 10- 19T09:53:28.072589Z 0 [Note] E:CMSServerV6mysql ingpsmysqld (mysqld 5.7.28) starting as process 11900...
2023- 10- 19T09:53:28.074301Z 0 [ERROR] Error message file 'E:CMSServerV6mysqlshareenglisherrmsg.sys' had only 1114 error messages
but it should contain at least 1119 error messages.
Check that the above file is the right version for this program!
2023- 10- 19T09:53:28.080970Z 0 [Warning] You need to use -- log- bin to make -- binlog-format work.
2023- 10- 19T09:53:28.106794Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023- 10- 19T09:53:28.107323Z 0 [Note] InnoDB: Uses event mutexes
2023- 10- 19T09:53:28.107640Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2023- 10- 19T09:53:28.108052Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023- 10- 19T09:53:28.109001Z 0 [Note] InnoDB: Number of pools: 1
2023- 10- 19T09:53:28.109556Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2023- 10- 19T09:53:28.112795Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2023- 10- 19T09:53:28.120309Z 0 [Note] InnoDB: Completed initialization of buffer pool
2023- 10- 19T09:53:28.138613Z 0 [Note] InnoDB: Setting log file .ib_logfile101 size to 48MB
2023- 10- 19T09:53:28.195609Z 0 [Note] InnoDB: Setting log file .ib_logfile1 size to 48MB
2023- 10- 19T09:53:28.313921Z 0 [ERROR] InnoDB: Operating system error number 87 in a file operation.
2023- 10- 19T09:53:28.314362Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating- system- error- codes.html
2023- 10- 19T09:53:28.315019Z 0 [ERROR] InnoDB: File .ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
2023- 10- 19T09:53:28.315522Z 0 [ERROR] InnoDB: Cannot continue operation.

2.2 processing method:

Edit the my.ini configuration file and add the following configuration items under [mysqld]. After saving, run the software installation wizard again to start normally.
'innodb_flush_method = normal'

Source help.cmsv7.com
839 documents · 211 videos · docs.alwaycare.com