Hi everyone, I wasn't able to send and receive emails after the update 2026-01. So I uninstalled my Mailcow with the following commands: docker-compose down -v rm -rvf mailcow-dockerized moved the folders under /var/lib/docker/volumes/ to /tmp/volumes/. Then I installed Mailcow with 'su umask 0022 cd /opt git clone https://github.com/mailcow/mailcow-dockerized cd mailcow-dockerized' copied mailcow.conf from the appropriate one of my daily backups and started Mailcow with docker compose pull docker compose up -d Once it was running, I executed /opt/mailcow-dockerized/helper-scripts/ ./backup_and_restore.sh restore . I selected the appropriate backup for my mailcow.conf and restored everything with the “0” option. Unfortunately, it cannot find any domains or mailboxes in Mailcow. What could be the reason for this?

The problem is that the db was not restored Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 126 Server version: 10.11.15-MariaDB-ubu2204 mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> USE mailcow; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [mailcow]> SELECT COUNT(*) FROM domain; +----------+ | COUNT(*) | +----------+ | 0 | +----------+ 1 row in set (0.001 sec) MariaDB [mailcow]> SELECT COUNT(*) FROM mailbox; +----------+ | COUNT(*) | +----------+ | 0 | +----------+ 1 row in set (0.000 sec) MariaDB [mailcow]> SELECT * FROM domain LIMIT 5; Empty set (0.000 sec) MariaDB [mailcow]> SELECT username, active FROM mailbox LIMIT 5; Empty set (0.000 sec) So I restored the DB with the helper-Script, but that does not work. Any suggestions?

Did you check the backup tar.zst files? Are they valid and containing the actual backup? Especially the backup_mariadb.tar.zst

@"keggy82"#p30492 is there any log output while restoring? Error messages etc?

@"keggy82"#p30505 yes, the output of the restore script... what does it say?

I have a similiar issue. During my restore i got this Error altho i have everything installed im getting this: Stopping watchdog-mailcow... 1e001ac32f53 mailcow will be stopped and the currently active mailcow.conf will be modified to use the DB parameters found in /opt/mailcow-2026-02-04-14-35-57//mailcow.conf - do you want to proceed? [Y|n] Y Stopping mailcow... [+] down 19/19 ✔ Container mailcowdockerized-memcached-mailcow-1 Removed 1.4ss ✔ Container mailcowdockerized-olefy-mailcow-1 Removed 10.2s ✔ Container mailcowdockerized-dockerapi-mailcow-1 Removed 0.8ss ✔ Container mailcowdockerized-ofelia-mailcow-1 Removed 0.3ss ✔ Container mailcowdockerized-watchdog-mailcow-1 Removed 0.0ss ✔ Container mailcowdockerized-postfix-mailcow-1 Removed 2.4ss ✔ Container mailcowdockerized-acme-mailcow-1 Removed 0.5ss ✔ Container mailcowdockerized-nginx-mailcow-1 Removed 10.4s ✔ Container mailcowdockerized-postfix-tlspol-mailcow-1 Removed 2.0ss ✔ Container mailcowdockerized-rspamd-mailcow-1 Removed 1.0s ✔ Container mailcowdockerized-php-fpm-mailcow-1 Removed 0.4s ✔ Container mailcowdockerized-sogo-mailcow-1 Removed 10.3s ✔ Container mailcowdockerized-dovecot-mailcow-1 Removed 2.4s ✔ Container mailcowdockerized-clamd-mailcow-1 Removed 0.3s ✔ Container mailcowdockerized-mysql-mailcow-1 Removed 0.7s ✔ Container mailcowdockerized-redis-mailcow-1 Removed 0.4s ✔ Container mailcowdockerized-unbound-mailcow-1 Removed 1.9s ✔ Container mailcowdockerized-netfilter-mailcow-1 Removed 0.0s ✔ Network mailcowdockerized_mailcow-network Removed 0.2s tar (child): pigz -d -p 2: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now /bin/tar: Child returned status 2 /bin/tar: Error is not recoverable: exiting now Modifying mailcow.conf... Starting mailcow...

No Domains / Mailboxes etc. after restore

keggy82

Yes, and the size fits:

9.0 GiB [########################################################] backup_vmail.tar.gz
35.9 MiB [ ] backup_rspamd.tar.gz
24.4 MiB [ ] backup_mariadb.tar.gz
7.6 MiB [ ] backup_redis.tar.gz
12.0 KiB [ ] mailcow.conf
4.0 KiB [ ] backup_postfix.tar.gz
4.0 KiB [ ] backup_crypt.tar.gz
0.0 B [ ] .x86_64

I also unzipped the backup_mariadb.tar.gz. There are data in it.

DocFraggle

keggy82 is there any log output while restoring? Error messages etc?

keggy82

’mysql-mailcow-1 | 2026-02-03 10:22:22+01:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
mysql-mailcow-1 | 2026-02-03 10:22:22 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
mysql-mailcow-1 | 2026-02-03 10:22:22 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mysql-mailcow-1 | 2026-02-03 10:22:22 0 [Note] mariadbd: ready for connections.
mysql-mailcow-1 | Version: ‘10.11.15-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
mysql-mailcow-1 | 2026-02-03 10:22:27 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
mysql-mailcow-1 | 2026-02-03 10:22:28 0 [Note] mariadbd: Shutdown complete
mysql-mailcow-1 | 2026-02-03 10:22:28+01:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
mysql-mailcow-1 | 2026-02-03 10:22:28 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
mysql-mailcow-1 | 2026-02-03 10:22:28 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mysql-mailcow-1 | 2026-02-03 10:22:28 0 [Note] mariadbd: ready for connections.
mysql-mailcow-1 | Version: ‘10.11.15-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
'

DocFraggle

keggy82 This looks like the normal mariadb container logs. I meant the logs while restoring

You can restore only the database, maybe try that again and paste all the output here

keggy82

’mysql-mailcow-1 | 2026-02-04 11:12:28+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.15+maria_ubu2204 started.
mysql-mailcow-1 | 2026-02-04 11:12:28+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.15+maria_ubu2204 started.
mysql-mailcow-1 | 2026-02-04 11:12:30 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mysql-mailcow-1 | 2026-02-04 11:13:02 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
mysql-mailcow-1 | 2026-02-04 11:13:02 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mysql-mailcow-1 | 2026-02-04 11:13:04 0 [Note] mariadbd: ready for connections.
mysql-mailcow-1 | Version: ‘10.11.15-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 0 mariadb.org binary distribution
mysql-mailcow-1 | 2026-02-04 11:13:05 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
mysql-mailcow-1 | 2026-02-04 11:13:06 0 [Note] mariadbd: Shutdown complete
mysql-mailcow-1 | 2026-02-04 11:13:06 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
mysql-mailcow-1 | 2026-02-04 11:13:06 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mysql-mailcow-1 | 2026-02-04 11:13:06 0 [Note] mariadbd: ready for connections.
mysql-mailcow-1 | Version: ‘10.11.15-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
'

Do you know other logs?

DocFraggle

keggy82 yes, the output of the restore script… what does it say?

keggy82

cat restore_2026-02-04_11-10.log
Using 1 Thread(s) for this run.
Notice: You can set the Thread count with the THREADS Variable before you run this script.
Using /mnt/backup as backup/restore location.

Found project name mailcowdockerized
Checking Docker image: ghcr.io/mailcow/backup:latest
Image update available, pulling ghcr.io/mailcow/backup:latest
latest: Pulling from mailcow/backup
Digest: sha256:e269449325e8ff4962a40a1de31c257b4f0fa4a2bc63bf94a4c2f60443b4b7c9
Status: Image is up to date for ghcr.io/mailcow/backup:latest
ghcr.io/mailcow/backup:latest
Successfully pulled ghcr.io/mailcow/backup:latest

[ 1 ] - /mnt/backup/mailcow-2026-01-28-00-01-09/

[ 0 ] - all
[ 1 ] - Crypt data
[ 2 ] - Redis DB
[ 3 ] - SQL DB
[ 4 ] - Postfix data
[ 5 ] - Rspamd data

Restoring mysql from /mnt/backup/mailcow-2026-01-28-00-01-09/…

Stopping watchdog-mailcow…
e5092cb7da91

Stopping mailcow…
Modifying mailcow.conf…
Starting mailcow…

Starting watchdog-mailcow…
2f2417e7270f

loggorus

I have a similiar issue. During my restore i got this Error altho i have everything installed im getting this:

Stopping watchdog-mailcow…
1e001ac32f53

mailcow will be stopped and the currently Stopping mailcow…
[+] down 19/19
✔ Container mailcowdockerized-memcached-mailcow-1 ✔ Container mailcowdockerized-olefy-mailcow-1 ✔ Container mailcowdockerized-dockerapi-mailcow-1 ✔ Container mailcowdockerized-ofelia-mailcow-1 ✔ Container mailcowdockerized-watchdog-mailcow-1 ✔ Container mailcowdockerized-postfix-mailcow-1 ✔ Container mailcowdockerized-acme-mailcow-1 ✔ Container mailcowdockerized-nginx-mailcow-1 ✔ Container mailcowdockerized-postfix-tlspol-mailcow-1 ✔ Container mailcowdockerized-rspamd-mailcow-1 ✔ Container mailcowdockerized-php-fpm-mailcow-1 ✔ Container mailcowdockerized-sogo-mailcow-1 ✔ Container mailcowdockerized-dovecot-mailcow-1 ✔ Container mailcowdockerized-clamd-mailcow-1 ✔ Container mailcowdockerized-mysql-mailcow-1 ✔ Container mailcowdockerized-redis-mailcow-1 ✔ Container mailcowdockerized-unbound-mailcow-1 ✔ Container mailcowdockerized-netfilter-mailcow-1 ✔ Network mailcowdockerized_mailcow-network tar (child): pigz -d -p 2: Cannot exec: tar (child): Error is not recoverable: exiting /bin/tar: Child returned status 2
/bin/tar: Error is not recoverable: exiting Modifying mailcow.conf…
Starting mailcow… active mailcow.conf will be modified to use the DB parameters found in /opt/mailcow-2026-02-04-14-35-57//mailcow.conf - do you want to proceed? [Y|n] Y
Removed 1.4ss
Removed 10.2s
Removed 0.8ss
Removed 0.3ss
Removed 0.0ss
Removed 2.4ss
Removed 0.5ss
Removed 10.4s
Removed 2.0ss
Removed 1.0s
Removed 0.4s
Removed 10.3s
Removed 2.4s
Removed 0.3s
Removed 0.7s
Removed 0.4s
Removed 1.9s
Removed 0.0s
Removed 0.2s
No such file or directory
now
now

keggy82

Any other ideas I can try?

DocFraggle

keggy82 Not really, as we still don’t know what exactly is going wrong here… what you could try: have a look at the script and try restoring the database manually. As I can see the are different approaches depending on which version you were running, old MySQL or new mariadb:

mailcow/mailcow-dockerizedblob/master/helper-scripts/backup_and_restore.sh#L376-L407

This way you should see where things go south

chriss

tar (child): pigz -d -p 2: Cannot exec: No such file or directory

Is pigz installed?

keggy82

yes pigz is installed

tmaex

keggy82 Had the same issue.
pigz is installed on host, but not in the mariadb container.

I patched the restore script (not pretty) so at least it works:

@@ -215,7 +215,7 @@
   if [[ -f "${location}/${backup_name}.tar.zst" ]]; then
     echo "${backup_name}.tar.zst|zstd -d -T${THREADS}"
   elif [[ -f "${location}/${backup_name}.tar.gz" ]]; then
-    echo "${backup_name}.tar.gz|pigz -d -p ${THREADS}"
+    echo "${backup_name}.tar.gz|gzip"
   else
     echo ""
   fi

kubik256

tmaex This was a real lifesaver - thanks a lot!
Simple, quick and working.

ap2dev

Same issue, the patched restore script worked.

Not sure why this affects only a few
Could we not simply create a dockerfile for the mariadb container, to have pigz installed, and use that dockerfile in the docker compose for mariadb?

# mariadb-10.11.mod:
FROM mariadb:10.11
# Update package lists and install  pigz
RUN apt-get update && \
    apt-get install -y pigz && \
    rm -rf /var/lib/apt/lists/*

and something like this

     mysql-mailcow:
     build:
         context: .
         dockerfile: mariadb-10.11.mod
         ...
         ...