https://bugs.koozali.org/show_bug.cgi?id=11970
--- Comment #20 from John Crisp <[email protected]> ---
OK - I can see the same error as Terry.
mysqldump: Got error: 1556: "You can't use locks with log tables" when using
LOCK TABLES
Think the answer is here:
https://serverfault.com/questions/613532/mysql-cant-use-locks-with-log-tables
"Running table checks implicitly locks the table (equivalent to executing 'LOCK
TABLES') to prevent concurrency issues. The log engine is a table type (just
like myisam and innodb) that was introduced in 5.1 which do not need - and thus
do not support - locking. The slow log and general log use said engine by
default. The message you are seeing is harmless. The issue you linked too says
users can ignore the misleading message, and that the message will be removed
in a future version."
Shame this fix was on the older 2.5 version - we use 3.x which is quite a bit
different.
https://github.com/selim13/docker-automysqlbackup/issues/10
https://github.com/selim13/docker-automysqlbackup/commit/39c1b9a8b9141157326829bbe6991a9c6ffe2308
So it needs a modification to the command that does the mysqldump.
No idea where :worried:
Possibly in fullschema () ??
I need to step debug it.
Something else I was testing was the runmysqlcommand - it seems you need to use
-b as an option now, and then -c to specify the correct config file
Add $2 here
/usr/local/bin/automysqlbackup $1 $2 >/dev/null
And then in the cron file template do:
root /sbin/e-smith/runmysqlbackup -bc /etc/automysqlbackup/mymaria.conf >
/dev/null
Or
/sbin/e-smith/runmysqlbackup -bc /etc/automysqlbackup/mymaria105.conf >
/dev/null
Not sure that is the right solution but it's on my test box for tonight.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
