[MDEV-14989] Database failing to start Created: 2018-01-18  Updated: 2018-01-19  Resolved: 2018-01-19

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jai Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Production


Attachments: Text File mariadb.log    

 Description   

Hi,
Database is failing to come online. Below is the error I am seeing. I am using xtrabackup to backup and restore. Please help

2018-01-18 11:13:20 7fd700dcc900 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Using Linux native AIO
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Using SSE crc32 instructions
2018-01-18 11:13:20 140561409165568 [Note] InnoDB: Initializing buffer pool, size = 16.0G
2018-01-18 11:13:24 140561409165568 [Note] InnoDB: Completed initialization of buffer pool
2018-01-18 11:13:25 140561409165568 [Note] InnoDB: The first specified data file /var/lib/mysql/ibdata/ibdata1 did not exist: a new database to be created!
2018-01-18 11:13:25 140561409165568 [Note] InnoDB: Setting file /var/lib/mysql/ibdata/ibdata1 size to 512 MB
2018-01-18 11:13:27 140561409165568 [Note] InnoDB: Setting log file ./ib_logfile101 size to 2000 MB
2018-01-18 11:13:42 140561409165568 [Note] InnoDB: Setting log file ./ib_logfile1 size to 2000 MB
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2018-01-18 11:13:52 140561409165568 [Warning] InnoDB: New log files created, LSN=45782
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Doublewrite buffer not found: creating new
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Doublewrite buffer created
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: 128 rollback segment(s) are active.
2018-01-18 11:13:52 140561409165568 [Warning] InnoDB: Creating foreign key constraint system tables.
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Foreign key constraint system tables created
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Creating tablespace and datafile system tables.
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Tablespace and datafile system tables created.
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Waiting for purge to start
2018-01-18 11:13:52 140561409165568 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 0
2018-01-18 11:13:52 140539932440320 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-01-18 11:13:52 140561409054464 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
2018-01-18 11:13:52 140561409165568 [Warning] Failed to setup SSL
2018-01-18 11:13:52 140561409165568 [Warning] SSL error: SSL_CTX_set_default_verify_paths failed
ERROR: 6 Error on delete of './performance_schema/db.opt' (Errcode: 13 "Permission denied")
2018-01-18 11:13:52 140561409165568 [ERROR] Aborting



 Comments   
Comment by Elena Stepanova [ 2018-01-18 ]

The error message seems fairly straightforward, Error on delete of './performance_schema/db.opt' (Errcode: 13 "Permission denied"). Check ownership and permissions.

Comment by Jai [ 2018-01-19 ]

Hi Elena,
Thanks for your reply. I have right permissions and tried to start the database and ran into issue again. BTW my source database is 10.1.22-MariaDB and destination database version is MariaDB 10.1.30. Do you think I need to run mysql_upgrade before I bring up the database.

Thanks,
Jai

Comment by Jai [ 2018-01-19 ]

NVM, I was able to figure it out. Thanks for your help.

Thanks,
Jai

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