Bug #90344 | MySQL 8.0 crashes after setting log_bin and relay_log to the same value | ||
---|---|---|---|
Submitted: | 9 Apr 2018 5:07 | Modified: | 9 Apr 2018 6:17 |
Reporter: | Hanzhi W | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.4 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[9 Apr 2018 5:07]
Hanzhi W
[9 Apr 2018 6:17]
MySQL Verification Team
Hello Hanzhi W, Thank you for the report. This is duplicate of Bug #90252, please see Bug #90252. ## 2018-04-09T06:09:38.249831Z 0 [System] [MY-010116] /export/umesh/server/binaries/Trunk/mysql-8.0.4/bin/mysqld (mysqld 8.0.4-rc-log) starting as process 1667 ... 2018-04-09T06:09:38.254486Z 0 [ERROR] [MY-010911] Cannot have same base name '/export/umesh/server/binaries/Trunk/mysql-8.0.4/90344/same_base_file_name' for both binary and relay logs. Pl/AUI▒▒L▒⾟*') options to ensure they do not conflict.n option is not used, default '--relay-log' if --log-bin option is used without argument) and hod03-relay-bin (default 'H▒L▒ 2018-04-09T06:09:38.254514Z 0 [ERROR] [MY-010119] Aborting 2018-04-09T06:09:38.254557Z 0 [Note] [MY-010120] Binlog end Thanks, Umesh