MariaDB dump failed on backup -

SYSTEM INFORMATION
OS and Version - AlmaLinux 9.8
Kernel and CPU - Linux 5.14.0-503.34.1.el9_5.x86_64 on x86_64 - AMD EPYC 7502P 32-Core Processor, 64 cores, 256GB DDR4 ECC memory
Virtualmin version - 8.1.0 Professional

All backups are failing local and scheduled S3 storage due to the database dump error detailed below:

Creating backup for virtual server XXXXX.com ..

  • Copying virtual server configuration ..
    .. done
    Backing up Cron jobs ..
    .. none defined
    Creating TAR file of home directory ..
    .. done
    Saving mail aliases ..
    .. done
    Saving mail and FTP users ..
    .. done
    Backing up mail and FTP user Cron jobs ..
    .. none to backup
    Copying Apache virtual host configuration ..
    .. done
    Copying Apache log files ..
    .. done
    Copying SSL Apache virtual host configuration and certificate ..
    .. done
    Copying Logrotate configuration ..
    .. done
    Copying MariaDB user details ..
    .. done
    Dumping MariaDB database XXXXXX..
    .. dump failed :

    : line 1: /*M!999999-: No such file or directory
    : line 2: syntax error near unexpected token `('
    : line 2: `-- MariaDB dump 10.19  Distrib 10.5.29-MariaDB, for Linux (x86_64)'
    
    

    Dumping MariaDB database XXXXX_wordpress .. .. dump failed :

    : line 1: /*M!999999-: No such file or directory
    : line 2: syntax error near unexpected token `('
    : line 2: `-- MariaDB dump 10.19  Distrib 10.5.29-MariaDB, for Linux (x86_64)'
    mysqldump: Got errno 32 on write
    

Sounds like its having issue dumping to the temporary file location webmin uses, have you done any modification to that location? I do backups every night with no problem, and this error has never been reported on the forum.
temp directory should be at /tmp/.webmin
I ran a scheduled backup and that’s where its happening on my system.

Thanks Stefan, my server has 345 days uptime and has been backing up to Amazon S3 every night without fail throughout that time and I’ve never had an issue with it.

Sunday for some reason, that changed. I have about 40 Wordpress sites hosted on the server, some of which have been running and shown signs of attack in the Updraft compromise, which all happened around the same day that backups started to fail. https://www.wordfence.com/blog/2026/06/critical-unauthenticated-authentication-bypass-vulnerability-patched-in-updraftplus-wordpress-plugin/

I’m not sure if they are linked or not, but backups in WP Workbench also fail with the same error, but I’ve been working with ChatGPT to tweak the way MariaDB is backing up, but none of it seems to be working. The only thing I can do for now is backup without database, which is pretty pointless in Wordpress!

Your on Pro license, so maybe raise a ticket and see if staff can sort it.