[MDEV-9436] When using xtrabackup-v2 SST, built-in xtrabackup SSL fails on CentOS/RHEL 6 Created: 2016-01-20 Updated: 2019-05-20 Resolved: 2019-05-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera SST, Scripts & Clients |
| Affects Version/s: | 10.1.10, 10.0.23-galera |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Seppo Jaakola |
| Resolution: | Cannot Reproduce | Votes: | 2 |
| Labels: | galera, need_feedback, sst, wsrep | ||
| Issue Links: |
|
||||||||||||
| Description |
|
The wsrep_sst_xtrabackup-v2 script supports 3 different types of encryption. An encryption type is chosen via the encrypt option:
The first encryption option above uses XtraBackup's built-in encryption. This option currently fail on CentOS/RHEL 6 with the following error:
This may be related to ReproducingThe configuration file that is used on both joiner and donor is:
To generate the encryption key, let's follow the directions shown here. For example:
Then we can fill in the [sst] section of the configuration file for the donor and joiner:
When the joiner attempts to SST, it fails. The joiner's log:
The donor's log:
And /var/lib/mysql/innobackup.backup.log on the donor contains:
|
| Comments |
| Comment by Seppo Jaakola [ 2018-10-16 ] |
|
I tried xtrabackup SST with encrypt mode 1, first on Ubuntu and MariaDB versions 10.1 and 10.0, and SST worked fine {{ |
| Comment by Seppo Jaakola [ 2018-10-16 ] |
|
xtrabackup encrypt modes 1,2 and 3 have been declared deprecated, and the only supported encrypt mode is now 4. Is there some specific reason for having this mode 1 symmetric encryption working? |
| Comment by Geoff Montee (Inactive) [ 2019-05-20 ] |
|
If encrypt=4 is the only supported encryption mode for XtraBackup SSTs, then where does that leave TLS support in Mariabackup SSTs? The TLS methods in the Mariabackup SST script were ported directly from the XtraBackup SST script, but encrypt=4 has not been ported to Mariabackup yet. See |