[MDEV-26066] mariabackup reporting of completed and failures includes no details Created: 2021-07-01  Updated: 2021-08-16

Status: Open
Project: MariaDB Server
Component/s: mariabackup
Affects Version/s: 10.5.11
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Tomas Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: reporting
Environment:

CentOS 7



 Description   

When the backup is running, it reports which file is going to be copied:

[01] 2021-07-01 07:39:29 Copying ./VMPTX_central/actlog#P#P202008.ibd to /backup/b4/VMPTX_central/actlog#P#P202008.ibd

But when the copying has completed, the details about which file has been completed are missing, which will be difficulty to trace if there are multiple paralell copying performed at the same time (which copying is "...done" ?):

[01] 2021-07-01 07:39:30 ...done

When backup has been completed with the status of failure, the FATAL error message does not include the name of the datafile that fails to be copied, nor any os error messages or return codes causing the failures:

[00] FATAL ERROR: 2021-07-01 08:05:47 failed to copy datafile.

The actual OS or MariaDB error details causing the copying to fail is not presented, even if --verbose flag has been used.



 Comments   
Comment by Tomas [ 2021-08-16 ]

I see this error in the OS messages file

Aug 16 13:16:31 testhost mariadbd: 2021-08-16 13:16:31 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'mariabackup' host: 'localhost' (Got an error reading communication packets)

Comment by Tomas [ 2021-08-16 ]

Further investigations shows that all innofiles are succesfully copied.
I guess that it fails when it is trying to perform the below steps:

[00] 2021-08-16 11:43:04 Acquiring BACKUP LOCKS...
[00] 2021-08-16 11:43:04 Starting to backup non-InnoDB tables and files

Generated at Thu Feb 08 09:42:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.