[MDEV-18607] MariaDB Galera Cluster SST fails while using encryption Created: 2019-02-17  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Encryption, Galera, mariabackup, Plugin - AWS key management
Affects Version/s: 10.3.12
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Jeyaprakash Assignee: Julius Goryavsky
Resolution: Unresolved Votes: 2
Labels: aws, encryption, galera, mariabackup
Environment:

CentOS Linux release 7.6.1810 (Core) x86_64 GNU/Linux

Attachments: File first_node_innobacupex.log     File new_node.err    
Issue Links:
Relates
relates to MDEV-17787 Unable to backup using mariabackup , ... Closed

 Description   

Hi Guys,
We need to setup a 3 node Galera cluster with AWS key encrytion enabled.

We have configured the single node cluster with encryption.

When we tried to add a new node to the cluster, the SST(mariabackup) fails with UNKNOWN error.

190217 15:11:28 [01] Streaming ibdata1
--innobackupex: Error writing file 'UNKNOWN' (Errcode: 32 "Broken pipe")
xb_stream_write_data() failed.
--innobackupex: Error writing file 'UNKNOWN' (Errcode: 32 "Broken pipe")
[01] mariabackup: Error: xtrabackup_copy_datafile() failed.
[01] mariabackup: Error: failed to copy datafile.

Kindly let us know if any other possibilities to overcome this issue.

PFA for error log of the new node and backup log from first node.

 Comments   
Comment by Sukan [ 2019-03-06 ]

Can we have an update here?

Comment by Aleksandr Omelchuk [ 2020-01-09 ]

Faced with the same issue.
No encryption used.
Tried to add the second node to Galera cluster.
Server version: 10.4.10-MariaDB MariaDB Server
CentOS Linux release 7.4.1708 (Core) x86_64 GNU/Linux

Could you please provide an update on this?
Thank you.

Comment by Aleksandr Omelchuk [ 2020-01-13 ]

For some reason the root cause of the issue was timeout for service startup. So due to timeout systemctl terminated the SST process and it failed.
But we got totally uninformative errors in mariabackup log.
To fix the issue I've added the following parameter using "systemctl edit --full mariadb.service":

TimeoutStartSec=1800

Thank you.

Comment by MikaH [ 2020-02-18 ]

Same error with 10.4.11 and TimeoutStartSec=8000. Centos7 and no encryption. Mariabackup is SST-method

EDIT: With 10.4 old method is no-longer valid. systemctl edit mariadb does not work, followed by daemon-reload. Ignoring the lines:

[Service]
 
TimeoutStartSec=8000

Instead of that, put above to /etc/systemd/system/mariadb.service.d/timeoutsec.conf

Generated at Thu Feb 08 08:45:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.