## TL;DR

For "Access denied; you need (at least one of) the RELOAD privilege(s) for this operation": it's interesting that 5.7.41 changelog doesn't list anything close to the FLUSH TABLES WITH READ LOCK or to default values.

```text
Access denied; you need (at least one of) the RELOAD privilege(s) for this operation
```

## When to use

You are seeing this: I faced the same issue couple of days ago. Use this skill when you run into "mysqldump for AWS RDS `flush tables` error on linux only".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: recent 5.7.41, 5.7.40. If you are on something much newer or older, the details may have shifted.

I faced the same issue couple of days ago. My mysqldump script had been working for years just fine until it started to give me the `Access denied; you need (at least one of) the RELOAD privilege(s) for this operation` error. My first instinct was to grant this privilege. But after that I started to get `Access denied for user 'user'@'%' (using password - YES) (1045)` error, which is documented in AWS docs. After couple hours of investigation it turned out to be a bug of the most recent 5.7.41 version of mysql (It was released 17th of January, exactly when we started to get errors). Downgrading to 5.7.40 solved the problem. It's interesting that 5.7.41 changelog doesn't list anything close to the FLUSH TABLES WITH READ LOCK or to default values.

Context: Stack Overflow #75183032 (accepted answer, 23 votes): I have a process that exports the data from an AWS RDS MariaDB using mysqldump which has been running succesfully in a docker-image on Concourse for years. Since two nights ago the process has started failing with the error: `mysqldump: Couldn't execute 'FLUSH TABLES WITH READ LOCK': Access denied for user 'admin'@'%' (using password - YES) (1045) ` The official AWS explanation seems to be that because they do not allow super privileges to the master user or GLOBAL READ LOCK the mysqldump fails if the --master-data option is set. I do not have that option set. I'm running with these flags:...