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
Adding this to the DBEXCLUDE configuration setting solved this issue for
me:
# List of DBNAMES to EXLUCDE if DBNAMES are set to all (must be in quotes)
DBEXCLUDE=information_schema performance_schema
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thomas, I think an Ubuntu upgrade was responsible for some errors that
have already be fixed expect this one is still a remainder of that.
Which right should user debian-sys-maint have on table cond_instances?
then I can compare it and probably fix it.
--
You received this bug notification
root@host /var/lib/mysql# ls -lah performance_schema/cond_instances.frm
-rw-rw 1 mysql mysql 8.5K Jun 10 03:13 performance_schema/cond_instances.frm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thomas, it is installed out of the box version 2.6+debian-2 with
/etc/default/automysqlbackup
# By default, the Debian version of automysqlbackup will use:
# mysqldump --defaults-file=/etc/mysql/debian.cnf
# but you might want to overwrite with a specific user pass.
# To do this, simply edit
I've got the same issue with version 3.0rc6. Allthough I used the following in
automysqlbackup.conf
CONFIG_table_exclude=( 'cond_instances' )
Any ideas?
By the way thank you for this nice piece of sortware. It really helps so
much.
--
You received this bug notification because you are a
Sorry, I am not using automysqlbackup, we have a few line script that does
it, and I somehow thought this was a general mysql (mysqldump, to be
precise) bug.
On 1 February 2013 09:14, Thomas Goirand tho...@goirand.fr wrote:
On Fri Feb 1 2013 02:27:21 PM CST, Jan Groenewald j...@aims.ac.za
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
This bug persists for me on 12.04
On 1 February 2013 07:33, Thomas Goirand tho...@goirand.fr 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
On Fri Feb 1 2013 02:27:21 PM CST, Jan Groenewald j...@aims.ac.za
wrote:
This bug persists for me on 12.04
hi,
please post you /etc/default/automysqlbackup, and
tell which version of automysqlbackup you use.
Thomas
--
You received this bug notification because you are a member of Ubuntu
If this is a bug, it's a bug in mysqldump, not automysqldump. It
happens when automysqldump runs mysqldump performance_schema.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995587
Title:
@Andrex Yeah, it's well documented that it is because of the
performance_schema table.. I however disagree that it is a bug in
mysqldump; it is trying to dump that table as requested, and getting
denied (someone may very well want to dump the current stats out of that
table, and if they want to,
Solved this by ecluding performance_schema (along with already exlcuded
information_schema) from the backups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995587
Title:
mysqldump: Got error: 1142:
Is this not a general mysql bug? Or is the behaviour intentially different from
that on lucid?
(I'm not using automysqlbackup, just a cron script running mysqldump on every
database.
I get the same error on precise, but not on lucid)
--
You received this bug notification because you are a
Is --skip-lock-tables not an unsafe solution that might produce corrupt backups?
Is it not better to simply stop mysql, mysldump, then start, if you prioritize
backups
over 247 uptime?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did you use the passwords in /etc/mysql/debian.cnf from when the
database was initially created? These can change when reinstalling a
system or moving a database to other systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
to ignore 'performance_schema' database dump, replace in file
/etc/default/automysqlbackup the line :
DBNAMES=`mysql --defaults-file=/etc/mysql/debian.cnf --execute=SHOW DATABASES
| awk '{print $1}' | grep -v ^Database$ | grep -v ^mysql$ | tr \\\r\\\n ,\ `
with :
DBNAMES=`mysql
Correct solutions appears to be to exclude the 'performance_schema'
database from mysqldump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995587
Title:
mysqldump: Got error: 1142: SELECT,LOCK TABL
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: automysqlbackup (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995587
19 matches
Mail list logo
