Thx for your feedback! But on the old Server (Ubuntu 22/MariaDB 10), bind-address was also set to the extern IP of this server (for replication reason). Everything was fine.
... maybe we should note:
bind-address = 127.0.0.1, xxx.xxx.xxx.xxx
or
bind-adress = 0.0.0.0
It's a production server, so we can't test it properly. It is just surprising why it works for other domains on the server, but not for the two that are replicated.
@papahausa And? Was this the solution? xxx.xxx.xxx.xxx -> public IP.
We have the same error. Do we need the bind-adress for replication? Strange, a manual backup worked yesterday.
Unable to make database dump. Error: Failed to exec mariadb-dump: Exit code: 2: WARNING: option...
... very strange, same system and same hoster like the other server, but WinSCP show me the false time on this machine (see screenshot) and there is no setup for timezone in WinSCP.
#/var/log # date
Tue 04 May 2021 11:15:26 AM CEST
#/var/log # ls -F --full-time auth.log
-rw-r----- 1 syslog adm...
... the same output like on all other server:
~ # timedatectl
Local time: Tue 2021-05-04 11:04:33 CEST
Universal time: Tue 2021-05-04 09:04:33 UTC
RTC time: Tue 2021-05-04 09:04:33
Time zone: Europe/Berlin (CEST, +0200)
System clock...