Submitted by donnyspi on Thu, 09/01/2016 - 10:06
Ubuntu 16.04 Webmin 1.801 VirtualMin 5.03 Pro Linux 4.5.0-x86_64-linode65 on x86_64
When restoring a virtual server from a backup (full restore), the MySQL password doesn't work anymore. I have replicated this on two virtual server restores. Once I change the MySQL password to something else, it works.
Also, if a virtual server is backed up in a disabled state, then I enable the virtual server, then restore from a backup, the site is restored in a disabled state, but VM doesn't show it as being disabled. If I disable it again in VM, then reenable it, it's correctly enabled and marked enabled.
Don
Status:
Active
Comments
Submitted by andreychek on Thu, 09/01/2016 - 12:09 Comment #1
Jamie, he's using plaintext passwords.
He says that the password has not been changed outside of Virtualmin.
I verified that the user exists in MySQL -- but upon restoring the backup, the database password is no longer accepted for that user.
It initially sounds like an issue with the password being changed outside of Virtualmin, but he assures me that's not the case, that it's using the initial Virtualmin supplied database password.
I'm going to try and test it on another Ubuntu 16.04 system, though my test VM is acting up so that's taking longer than expected :-)
Submitted by JamieCameron on Thu, 09/01/2016 - 19:27 Comment #2
Was the backup taken on a different system?
Also, which MySQL version is the system running? I recently discovered a bug that could cause this kind of problem on MySQL 5.7 and later.
Submitted by andreychek on Thu, 09/01/2016 - 19:37 Comment #3
Jamie, the backup was generated on this same server. The restore was made after an unrelated problem occurred with the website.
It is indeed with MySQL 5.7 (which is what comes with Ubuntu 16.04).
Submitted by JamieCameron on Fri, 09/02/2016 - 00:35 Comment #4
Ok, I think this is the same issue that effects restores in 5.7. MySQL changed the semantics of the
set password
function, which breaks use of pre-hashed passwords (as seen in restores). The next Virtualmin release will fix this though.