backup/backup

Mysql warnings regarding insecure password (regression in v4.4.0 ?)

pySilver opened this issue · 5 comments

This is kinda old issue originally raised at #752 and #679 (and #618) that started to popup again after update to a latest version.

Is that a regression? Is that just me who is affected?

Typical log (got like 200 of them today & yesterday):

[2018/02/15 03:07:45][info] Performing Backup for 'xxxxxxxx_biz_pl (xxxxxxxx_biz_pl)'!
[2018/02/15 03:07:45][info] [ backup 4.4.0 : ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] ]
[2018/02/15 03:07:45][info] Database::MySQL Started...
[2018/02/15 03:07:45][info] Using Compressor::Gzip for compression.
[2018/02/15 03:07:45][info]   Command: '/bin/gzip'
[2018/02/15 03:07:45][info]   Ext: '.gz'
[2018/02/15 03:07:45][warn]   Pipeline STDERR Messages:
[2018/02/15 03:07:45][warn]   (Note: may be interleaved if multiple commands returned error messages)
[2018/02/15 03:07:45][warn] 
[2018/02/15 03:07:45][warn]   Warning: Using a password on the command line interface can be insecure.
[2018/02/15 03:07:45][info] Database::MySQL Finished!
[2018/02/15 03:07:45][info] Packaging the backup files...
[2018/02/15 03:07:45][info] Using Encryptor::OpenSSL to encrypt the archive.
[2018/02/15 03:07:46][info] Packaging Complete!
[2018/02/15 03:07:46][info] Cleaning up the temporary files...
[2018/02/15 03:07:46][info] Storage::S3 Started...
[2018/02/15 03:07:46][info] Storing 'sites-backup/xxxxxxxx_biz_pl/2018.02.15.03.07.45/xxxxxxxx_biz_pl.tar.enc'...
[2018/02/15 03:07:46][info] Cycling Started...
[2018/02/15 03:07:46][info] Storage::S3 Finished!
[2018/02/15 03:07:46][info] Cleaning up the package files...
[2018/02/15 03:07:46][warn] Backup for 'xxxxxxxx_biz_pl (xxxxxxxx_biz_pl)' Completed Successfully (with Warnings) in 00:00:01
[2018/02/15 03:07:46][info] Sending notification using Notifier::Mail...

@pySilver it's not a warning from the backup gem, but it's caused by setting the MySQL password in the backup model. Instead set it in the MySQL config file like I described here: #752 (comment)

@tombruijn I was just surprised it poped out of the blue after few years of working just fine :) no updates at all has been made.

Oh that's weird. No Backup update? Maybe a MySQL update? (version or config)

@tombruijn no, nothing and thats was weird :)

Then I'm afraid I don't know 😕
✨ Computers ✨