[MDEV-13557] Startup failure, unable to decrypt ibdata1 - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Affects Version/s: 10.1.26, 10.2.7
Fix Version/s: 10.1.27, 10.2.9, 10.3.2
Component/s: Encryption, Platform RedHat, Server, Storage Engine - InnoDB
Labels:
None
Environment:
Red Hat Enterprise Linux Server 7.3
Server version: 10.2.7-MariaDB-log MariaDB Server

Description

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.

# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1

{print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}

' |mysql dev_cms

5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

10.1.26_error.txt
7 kB
2017-08-18 03:01
custom_server.cnf.txt
0.4 kB
2017-08-17 04:16
encryption.cnf.txt
0.4 kB
2017-08-17 04:16
error_output.txt
6 kB
2017-08-17 04:16
mdev13557_ibdata.tar.gz
1.81 MB
2017-08-17 10:25
server.cnf.txt
0.2 kB
2017-08-17 04:16

Issue Links

causes

MDEV-14701 install_db shows corruption for rest encryption with innodb_data_file_path=ibdata1:3M

Closed

duplicates

MDEV-13093 Leak of Datafile::m_crypt_info on shutdown after failed startup

Closed

MDEV-13488 InnoDB writes CRYPT_INFO even though encryption is not enabled

Closed

relates to

MDEV-10977 [ERROR] InnoDB: Block in space_id 0 in file ibdata1 encrypted.

Closed

MDEV-13181 encryption.innodb-first-page-read sporadically fails in buildbot with signal 8

Closed

Activity

Ascending order - Click to sort in descending order

Dennis Corp created issue - 2017-08-17 04:15

Dennis Corp made changes - 2017-08-17 04:16

Field	Original Value	New Value
Attachment		error_output.txt [ 44001 ]

Dennis Corp made changes - 2017-08-17 04:16

Attachment

custom_server.cnf.txt [ 44002 ]

Dennis Corp made changes - 2017-08-17 04:16

Attachment

encryption.cnf.txt [ 44003 ]

Dennis Corp made changes - 2017-08-17 04:16

Attachment

server.cnf.txt [ 44004 ]

Dennis Corp made changes - 2017-08-17 04:18

Description

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.
5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.
# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1 {print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}' |mysql dev_cms
5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

Dennis Corp made changes - 2017-08-17 04:19

Description

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.
# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1 {print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}' |mysql dev_cms
5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.

# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1 {print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}' |mysql dev_cms

5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

Dennis Corp made changes - 2017-08-17 04:19

Description

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.

# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1 {print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}' |mysql dev_cms

5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

After upgrading from an older 5.5 release and implementing Data At Rest Encryption, then proceeding to convert a lot of myisam tables over to innodb, the following errors are now reported when starting the mariadb service.

[ERROR] InnoDB: The page [page id: space=0, page number=7] in file './ibdata1' cannot be decrypted.
[Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
[ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.

(See attached error_output.txt for full startup log detail)

The entire upgrade process did work smoothly, until the point I restarted the mariadb service.

The upgrade process went through the following stages.
1: Update mariadb via yum using the mariadb repo.
2: Rework config files due to path changes and start mariadb
3: Stop database, add in encryption configuration and start again.
4: Run sql query to convert tables from myisam to innodb.

\# mysql dev_cms -e "show table status where Engine='MyISAM';" | awk 'NR>1 {print "ALTER TABLE `"$1"` ENGINE = InnoDB;"}' |mysql dev_cms

5: Test and verify that encryption is working.
6: Stop and restart mariadb - Fault occurs on startup.

I've referenced two other issues which appear to be the same problem, however they're both listed and fixed in the 10.1 branch not 10.2

I don't have, but can probably generate more data if required.

Jan Lindström (Inactive) made changes - 2017-08-17 09:50

Assignee

Jan Lindström [ jplindst ]

Marko Mäkelä made changes - 2017-08-17 09:59

Link

This issue relates to ~~MDEV-10977~~ [ ~~MDEV-10977~~ ]

Elena Stepanova made changes - 2017-08-17 10:25

Attachment

mdev13557_ibdata.tar.gz [ 44005 ]

Elena Stepanova made changes - 2017-08-17 10:25

Status

Open [ 1 ]

Confirmed [ 10101 ]

Elena Stepanova made changes - 2017-08-17 10:44

Fix Version/s		10.2 [ 14601 ]
Fix Version/s		10.1 [ 16100 ]
Affects Version/s		10.1.26 [ 22553 ]

Dennis Corp made changes - 2017-08-18 03:01

Attachment

10.1.26_error.txt [ 44007 ]

Jan Lindström (Inactive) made changes - 2017-08-22 11:11

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Jan Lindström (Inactive) made changes - 2017-08-28 09:45

Link

This issue duplicates ~~MDEV-13488~~ [ ~~MDEV-13488~~ ]

Jan Lindström (Inactive) made changes - 2017-08-29 12:12

Fix Version/s		10.1.27 [ 22609 ]
Fix Version/s	10.1 [ 16100 ]

Jan Lindström (Inactive) made changes - 2017-08-30 05:51

Link

This issue duplicates ~~MDEV-13093~~ [ ~~MDEV-13093~~ ]

Jan Lindström (Inactive) made changes - 2017-08-30 07:12

Assignee	Jan Lindström [ jplindst ]	Marko Mäkelä [ marko ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Marko Mäkelä made changes - 2017-08-31 07:01

Fix Version/s		10.2.9 [ 22611 ]
Fix Version/s		10.3.2 [ 22533 ]
Fix Version/s	10.2 [ 14601 ]
Resolution		Fixed [ 1 ]
Status	In Review [ 10002 ]	Closed [ 6 ]

Jan Lindström (Inactive) made changes - 2017-08-31 10:43

Link

This issue relates to ~~MDEV-13181~~ [ ~~MDEV-13181~~ ]

Marko Mäkelä made changes - 2017-10-12 05:59

Assignee

Marko Mäkelä [ marko ]

Jan Lindström [ jplindst ]

Jan Lindström (Inactive) made changes - 2017-12-18 13:29

Link

This issue causes ~~MDEV-14701~~ [ ~~MDEV-14701~~ ]

Sergei Golubchik made changes - 2021-12-06 21:45

Workflow

MariaDB v3 [ 82136 ]

MariaDB v4 [ 152643 ]

People

Assignee:: Jan Lindström (Inactive)

Reporter:: Dennis Corp

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2017-08-17 04:15

Updated:: 2017-12-18 13:29

Resolved:: 2017-08-31 07:01

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration