[MDEV-24006] mysqlbinlog command does not work on new MariaDB 10.5.6 install Created: 2020-10-21 Updated: 2020-10-26 Resolved: 2020-10-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.5.6 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Justin Swanhart | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 1 |
| Labels: | None | ||
| Environment: |
Ubuntu 20 LTS |
||
| Issue Links: |
|
||||||||
| Description |
|
The installed /etc/mysql/mariadb.conf.d/50-client.cnf file contains: The mysqlbinlog client does not support the --default-character-set command line option, and thus it returns error: It is not possible to use mysqlbinlog without commenting out that option. |
| Comments |
| Comment by Justin Swanhart [ 2020-10-21 ] |
|
Also it exits with 0 instead of a non-zero error code and it doesn't prefix the output with ERROR: like other errors |
| Comment by Sergei Golubchik [ 2020-10-23 ] |
|
This looks like Could it be that your /etc/mysql/mariadb.conf.d/50-client.cnf came from before 10.5.4 and then you upgraded the server while the config file stayed old? |
| Comment by Justin Swanhart [ 2020-10-23 ] |
|
Oh. This is kind of weird. I spun up two EC2 machines, installed the repo in the same manner (using the script provided by mariadb) and used 'apt-get install mariadb-server' on both machines. One ended up with 10.5.6, but the other machine ended up with 10.3.22. I don't know why the older version ended up on the second machine, but that was the machine I was using mysqlbinlog on. So this is not a bug. Any idea why 10.3 would end up being installed from the repo on one machine when I followed the same steps on both? |
| Comment by Justin Swanhart [ 2020-10-26 ] |
|
You can close this. Sorry for the non-bug bug report. |