MySQL backups failed

Hi, I think this issue happens after recently update of Virtualmin Pro.

When a domain administrator try to make a database backup it fails with the following error message:

Database backup failed : DBI connect failed : Access denied for user 'domainadmin'@'localhost' to database 'mysql'

If I login as root the backup works fine, and Virtualmin backup the right database.

It the same issue in this post in forums http://virtualmin.com/node/34186

I have the same issue in all my Virtualmin Pro servers, all have the latest Virtualmin version with Debian 6 or 7. Here the software version details for the Debian 7 servers:

Debian 7.6 Wheezy

webmin-virtual-server 4.10

webmin 1.701

mysql-server-5.5 5.5.38-0+wheezy1

thanks in advance,

Santiago

Status: 
Closed (fixed)

Comments

So just to verify -- your websites are otherwise working, and that particular user is able to access their databases.

You're just seeing this issue during the backup process?

Also, I just wanted to confirm that you're seeing that issue with both your Debian 6 and Debian 7 servers?

Hi, the websites are working fine, the user (domain owner) can connect to databases from PHP or mysql CLI. From Virtualmin he can see all DB details like list of tables or all records in a table.

The backups are working fine from "Backup and Restore" - "Scheduled Backups" or "Backup Virtual Servers", but this task are done as root user.

The issue only occurs when the domain owner try manually to do a DB backup in: Edit Databases - Click on DB name - Manage database - Backup database. Define the file path in "Backup to file" and click on "Backup now".

If I try the same task as root user it works fine.

I'm seeing the issue in all my Debian 6 and 7 servers. In Debian 7 I use only official packages from Debian (mysql and php) or Virtualmin. One of my servers with Debian 6 have official packages, others have mysql 5.5 from Dotdeb. I can see the issue in Virtualmin 4.10 GPL too.

Thanks for all the info you've provided!

Jamie did some digging, and determined the cause of this issue. It is indeed a bug, and will be fixed in the next Virtualmin version.

Actually the next Webmin release (version 1.710)

Great, I'm glad you have found the bug. best regards, Santiago