aims team mailing list archive

[Jan Groenewald <jan@xxxxxxxxxx>]

This bug persists for me on 12.04


On 1 February 2013 07:33, Thomas Goirand <thomas@xxxxxxxxxx> wrote:

> Hi,
>
> There's absolutely no reason why this bug is still open, with comments
> from users. This has been fixed a long time ago in Debian, and should be
> also in Ubuntu. Perhaps this is just affecting users of Ubuntu 10.04, in
> which case I would advise to upgrade to the latest version of
> automysqlbackup from Debian SID (it will also work with any version of
> Ubuntu normally).
>
> For the above reasons, I'm asking for the closing of this bug.
>
> Thomas
>
> --
> 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
>
> --
> Mailing list: https://launchpad.net/~aims
> Post to     : aims@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~aims
> More help   : https://help.launchpad.net/ListHelp
>


-- 
  .~.
  /V\     Jan Groenewald
 /( )\    www.aims.ac.za
 ^^-^^

-- 
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