Not the answer you need?
Register and ask your own question!

innobackupex fails after Percona Server yum update

bleungbleung EntrantInactive User Role Beginner
Hi,

On my Centos 5.5(final) box, I ran a yum update on my Percona-Server files and now xtrabackup fails with the following:

[[email protected] backup]# innobackupex --password=XXX /backup
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2011. All Rights Reserved.
...
120209 15:24:41 innobackupex: Connected to database with mysql child process (pid=20671)
120209 15:24:47 innobackupex: Connection to database server closed
...
innobackupex: Using mysql Ver 14.14 Distrib 5.1.60, for unknown-linux-gnu (x86_64) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

innobackupex: fatal error: no 'mysqld' group in MySQL options
innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options

The versions I have installed now are:

These are the versions I have now where innobackupex fails:
[[email protected] ~]# yum list installed | grep Percona
Percona-Server-client-51.x86_64 5.1.60-rel13.1.413.rhel5 installed
Percona-Server-devel-51.x86_64 5.1.60-rel13.1.413.rhel5 installed
Percona-Server-server-51.x86_64 5.1.60-rel13.1.413.rhel5 installed
Percona-Server-shared-compat.x86_64 5.5.20-rel24.1.217.rhel5 installed


Below shows my session on how it was working perfectly fine before I did the yum update..

[[email protected] mysql]# yum list | grep Percona
Percona-Server-client-51.x86_64 5.1.52-rel11.6.140.rhel5 installed
Percona-Server-devel-51.x86_64 5.1.52-rel11.6.140.rhel5 installed
Percona-Server-server-51.x86_64 5.1.52-rel11.6.140.rhel5 installed
Percona-Server-shared-compat.x86_64 5.1.48-6 installed


[[email protected] mysql]# yum list | grep xtrabackup
xtrabackup.x86_64 1.6.4-314.rhel5 percona
xtrabackup-debuginfo.x86_64 1.6.4-314.rhel5 percona

[[email protected] backup]# innobackupex --password=XXX /backup
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2011. All Rights Reserved.
...
120209 15:05:53 innobackupex: Starting mysql with options: --password=xxxxxxxx --unbuffered --
120209 15:05:53 innobackupex: Connected to database with mysql child process (pid=18925)
120209 15:05:59 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".

innobackupex: Using mysql Ver 14.14 Distrib 5.1.52, for unknown-linux-gnu (x86_64) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.

Warning: xtrabackup: ignoring option '--log-stream' due to invalid value '/var/log/mysqld.log'
innobackupex: Created backup directory /backup/2012-02-09_15-05-59
120209 15:05:59 innobackupex: Starting mysql with options: --password=xxxxxxxx --unbuffered --
120209 15:05:59 innobackupex: Connected to database with mysql child process (pid=18951)
120209 15:06:01 innobackupex: Connection to database server closed
120209 15:06:01 innobackupex: Starting ibbackup with command: xtrabackup --backup --suspend-at-end --target-dir=/backup/2012-02-09_15-05-59
innobackupex: Waiting for ibbackup (pid=18966) to suspend
innobackupex: Suspend file '/backup/2012-02-09_15-05-59/xtrabackup_suspended'
...
xtrabackup: use O_DIRECT
120209 15:06:01 InnoDB: Warning: allocated tablespace 5052, old maximum was 9
>> log scanned up to (74203137403)
...
120209 15:10:00 innobackupex: All tables unlocked
120209 15:10:00 innobackupex: Connection to database server closed

innobackupex: Backup created in directory '/backup/2012-02-09_15-05-59'
innobackupex: MySQL binlog position: filename '', position
120209 15:10:00 innobackupex: completed OK!



Please help! Thanks!
b

Comments

  • WheresWardyWheresWardy Contributor Inactive User Role Beginner
    Check that your /etc/my.cnf file exists after the update, and that it contains the information that xtrabackup is looking for (a [mysqld] section and a datadir setting) - it may have been moved or altered as a result of doing the yum update.
  • bleungbleung Entrant Inactive User Role Beginner
    Those are all still intact. I actually found the bug report for it last night, but just not sure how to get the fix.
    Here is the link to the bug report, https://bugs.launchpad.net/percona-xtrabackup/+bug/910206
    Thanks for the tip though!
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.