Added CONFIG_mysql_dump_tablespaces option to handle breaking change in MySQL 5.7.31 and 8.0.21

[SLiV9]

Added CONFIG_mysql_dump_tablespaces (default 'yes'). When set to 'no' it adds the option --no-tablespaces to the invocation of mysqldump. The default behaviour remains unchanged.

As a breaking change in MySQL 5.7.31 and 8.0.21, mysqldump now requires the PROCESS privilege to access tablespace information. If no tablespace information is needed, --no-tablespaces can be added to the mysqldump invocation to lower the privileges required by the mysqldump user.

[kimonostereo]

Thanks for adding this! I've added these changes but I'm still seeing the error mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces

What is interesting is if I set CONFIG_mysql_dump_tablespaces to yes, I get two instances of the error instead of one. Not sure why that is happening. Maybe there is another place in the script where this needs to be applied?

[nathanhoeller]

Hey @kimonostereo, I'm seeing the two instances of the error as well. Were you able to find a solution?

[kimonostereo]

Hey @kimonostereo, I'm seeing the two instances of the error as well. Were you able to find a solution?

Hey there @nathanhoeller! No I did not. I've taken to just living with this error. If you ever figure it out, please let me know!

[solaceten]

Hello

I also see this error:

mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces

I am running #version=3.0_rc2

Any one have a clue how to resolve it? The DBs are still actually being dumped, so perhaps we have to simply ignore this error ?

SOLVED: see my note in post below #51 (comment)

[kimonostereo]

Hello

I also see this error:

mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces

I am running #version=3.0_rc2

Any one have a clue how to resolve it? The DBs are still actually being dumped, so perhaps we have to simply ignore this error ?

Hi @solaceten! I run into the exact same issue, but I have no clue on how to resolve it. I've been ignoring it for a long time.

[solaceten]

You might want to look into this repository which I believe is an updated version. I did a complete reinstall and had to tweak the settings here and there, but it is more up to date script and it works with MySql V8

https://github.com/belgotux/automysqlbackup

Credit to @belgotux