[MDEV-20607] Mariabackup doesn't detect error and give "Completed ok" status. Created: 2019-09-17  Updated: 2020-08-25  Resolved: 2019-10-01

Status: Closed
Project: MariaDB Server
Component/s: mariabackup
Affects Version/s: 10.2.21
Fix Version/s: 10.2.24, 10.3.15, 10.4.5

Type: Bug Priority: Major
Reporter: Nilnandan Joshi Assignee: Vladislav Lesin
Resolution: Fixed Votes: 0
Labels: None


 Description   

Even there is an error in backup, mariabackup doesn't detect error and give "Completed ok" status. 

2019-09-14 1:49:06 139835221698304 [Note] InnoDB: page_cleaner coordinator priority: -20
 
2019-09-14 1:49:06 139872001148736 [Note] InnoDB: Highest supported file format is Barracuda.
 
2019-09-14 1:49:06 139872001148736 [ERROR] InnoDB: Obtaining redo log encryption key version 1 failed (4294967295). Maybe the key or the required encryption key management plugin was not found.
 
2019-09-14 1:49:06 139872001148736 [ERROR] InnoDB: Reading checkpoint encryption info failed.
 
2019-09-14 1:49:06 139872001148736 [ERROR] InnoDB: No valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.
 
2019-09-14 1:49:06 139872001148736 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
 
[00] 2019-09-14 01:49:06 mariabackup: innodb_init() returned 11 (Generic error).
 
[00] 2019-09-14 01:49:07 completed OK!



 Comments   
Comment by Vladislav Lesin [ 2019-09-22 ]

The issue was fixed in the following commit:
===
commit 6b5d3c51b3d4260ba692bb84c64eb2705635e051
Author: Vladislav Vaintroub <wlad@mariadb.com>
Date: Tue Apr 23 12:44:09 2019 +0100

Do fast exit with error code and FATAL ERROR message, if innodb cannot start during prepare.

Otherwise, it is possible for "prepare" to exit with error code 0,
even if it did not work at all.
===

This commit was released in 10.2.24

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