Recent changes to bugs

#73 Emailing not working (3.0_rc6)

2020-08-06T16:44:37.244000Z

Yes, this fixed the problem.

However on CentOS it's a different package.

    yum install gnupg2-smime

Got it going for me!

#73 Emailing not working (3.0_rc6)

2020-07-10T07:29:35.807000Z

Do you have gpgsm packet installed, Mutt (the system used by automysqlbackup to send email) need this packet ?
Try this to see:
dpkg -l | grep gpgsm
You may have this kind of response:
ii gpgsm 2.1.18-8~deb9u4 amd64 GNU privacy guard - S/MIME version
If you don't have gpgsm, install it:
sudo apt-get install gpgsm
sudo yum install gpgsm (for CentOS)

#73 Emailing not working (3.0_rc6)

2020-02-11T10:21:48.472000Z

Me too!

OS: CentOS release 6.10 (Final)
mysql: mysql Ver 8.0.19 for Linux on x86_64 (MySQL Community Server - GPL)
(Runing Virtualmin as well)

I don't see a way to set debug flags, etc. but I'm happy to help if asked to try things.

I confirmed my mailserver is working; mail to root from cron jobs, etc. get delivered normally.

WARNING: --ssl is deprecated

2017-08-16T16:04:18.351000Z

Backup of Database Server - localhost
Databases - WARNING: --ssl is deprecated and will be removed in a future version. Use --ssl-mode instead.
Databases (monthly) - WARNING: --ssl is deprecated and will be removed in a future version. Use --ssl-mode instead.

#86 mysql 5.6 and mysql 5.7 error with full schema

2017-07-02T03:57:03.501000Z

bad milestone this is actually against 3.0

mysql 5.6 and mysql 5.7 error with full schema

2017-07-02T03:56:06.700000Z

even if i add this to the config:
CONFIG_db_exclude=( 'information_schema' 'performance_schema' 'sys' )

at every backup I get this error when full schema is enabled:

mysqldump: Got error: 1142: SELECT, LOCK TABLES command denied to user 'backupuser'@'localhost' for table 'accounts' when using LOCK TABLES

this is because full schema backup use the --all-databases option instead of getting a list of db minus the virtual db to remove.

Support for MySQL 5.6

2016-02-01T09:40:19.531000Z

Hey, guys,

first of all, thanks for this great skript!

I wrote two patches to support setting a login-path with the mysql_config_editor which can be used with automysqlbackup. Maybe you're interested in merge them into the official tree. Without this patch automysqlbackup ends up with warning because MySQL 5.6 does not like to give the password in cleartext on the console anymore.

kind regards
Andi

#79 Use --events

2015-08-18T17:59:06.676000Z

since we want a backup, the event table should probably in the backup.

#78 errors/warnings on MySQL 5.6.11

2015-08-04T09:50:01.200000Z

#79 Use --events

2015-08-04T09:47:19.800000Z

Or use
opt=( '--ignore-table=mysql.event' )