aims team mailing list archive

[Mike Taylor <miketay@xxxxxxxxxxxx>]

I can confirm this is still an issue.  Deckard's solution helped, but it
only looks at the DBEXCLUDE parameter if you are also setting the
configuration parameter DBNAMES line to "all" in the
/etc/default/automysqlbackup file.

By default, the configuration file has these defaults:

 DBNAMES=`mysql --defaults-file=/etc/mysql/debian.cnf --execute="SHOW
DATABASES" | awk '{print $1}' | grep -v ^Database$ | grep -v ^mysql$ |
tr \\\r\\\n ,\ `

 DBEXCLUDE="information_schema"

They could be changed to this to fix the issue:

 DBNAMES="all"

 DBEXCLUDE="information_schema performance_schema"

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/995587

Title:
  mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to user
  'debian-sys-maint'@'localhost' for table 'cond_instances' when using
  LOCK TABLES

Status in “automysqlbackup” package in Ubuntu:
  Confirmed

Bug description:
  Release:	12.04
  automysqlbackup:
    Installed: 2.6+debian-2
    Candidate: 2.6+debian-2
    Version table:
   *** 2.6+debian-2 0
          500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
          100 /var/lib/dpkg/status


  
  After a remove --purge, reinstall of automysqlbackup, and configure in /etc/defaults/automysqlbackup, I am emailed the following error when cron runs /usr/sbin/automysqlbackup:

  mysqldump: Got error: 1142: SELECT,LOCK TABL command denied to user
  'debian-sys-maint'@'localhost' for table 'cond_instances' when using
  LOCK TABLES

  it seems that the default on ubuntu is to use the user debian-sys-
  maint to run this backup, however debian-sys-maint doesn't have full
  permissions.  Some say that these tables are not necessary to backup
  and recommend the flag " --skip-add-locks" OR "--skip-lock-tables":

  http://serverfault.com/questions/268566/cant-backup-the-mysql-table-
  with-mysqldump-select-lock-tabl-command-denied-for

  I managed to get the error to go away by adding "--skip-lock-tables"
  to /usr/sbin/automysqlbackup:


          if [ -z "${USERNAME}" -o -z "${PASSWORD}" ] ; then
                  mysqldump --defaults-file=/etc/mysql/debian.cnf $NEWOP\
  T --skip-lock-tables $1 > $2
          else
                  mysqldump --user=$USERNAME --password=$PASSWORD --host\
  =$DBHOST --skip-lock-tables $NEWOPT $1 > $2
          fi
          return 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automysqlbackup/+bug/995587/+subscriptions