|
Start fresh server with --log-bin --version=10
...
|
2016-10-23 19:44:44 139772263688064 [Note] InnoDB: Tablespace ID 7 name innodb_temporary:Default tablespace encryption mode scheme unencrypted
|
2016-10-23 19:44:44 139772263688064 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
|
2016-10-23 19:44:44 139772263688064 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
|
2016-10-23 19:44:44 139772263688064 [Note] InnoDB: Waiting for purge to start
|
2016-10-23 19:44:45 139772263688064 [Note] InnoDB: 5.7.14 started; log sequence number 1226634
|
2016-10-23 19:44:45 139771116517120 [Note] InnoDB: Loading buffer pool(s) from /data/bld/10.2/data/ib_buffer_pool
|
2016-10-23 19:44:45 139772263688064 [Note] Plugin 'FEEDBACK' is disabled.
|
2016-10-23 19:44:45 139771116517120 [Note] InnoDB: Buffer pool(s) load completed at 161023 19:44:45
|
2016-10-23 19:44:45 139772263688064 [ERROR] Could not use jessie-bin for logging (error 0). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
|
2016-10-23 19:44:45 139772263688064 [ERROR] Aborting
|
If a certain format is expected (experiments show it should be X.Y, where X is a number), it needs to be documented, and the error log should be clearer about it.
If the server was previously (normally) started with binary log and shut down, and then started with a bad fake version, the error is different, but equally vague:
2016-10-23 19:55:00 140503370692352 [Note] InnoDB: Loading buffer pool(s) from /data/bld/10.2/data/ib_buffer_pool
|
2016-10-23 19:55:00 140504515164032 [Note] Plugin 'FEEDBACK' is disabled.
|
2016-10-23 19:55:00 140504515164032 [ERROR] Can't init tc log
|
2016-10-23 19:55:00 140504515164032 [ERROR] Aborting
|
|