Warning "failed to find uploaded binlog behind " on all backups since upgrade to mariadb 10.11

[Deracination]

Database name

MariaDB 10.11

Issue description

Since upgrading from mariadb 10.3 to 10.11 running a full backup '/usr/local/bin/wal-g --config=/etc/wal-g.json backup-push' emits the following warning on every backup:

WARNING: 2024/03/04 10:09:09.717187 failed to find uploaded binlog behind

Is it safe to just ignore these warnings?

Config

{
        "AWS_ACCESS_KEY_ID": "**,
        "AWS_SECRET_ACCESS_KEY": "**",
        "WALG_S3_PREFIX": "s3://**",
        "WALG_S3_STORAGE_CLASS": "STANDARD_IA",
        "WALG_COMPRESSION_METHOD": "brotli",
        "WALG_MYSQL_DATASOURCE_NAME": "user:pass@tcp(localhost:3306)/db",
        "WALG_STREAM_CREATE_COMMAND": "mariabackup --backup --stream=xbstream --datadir=/var/lib/mysql",
        "WALG_STREAM_RESTORE_COMMAND": "mbstream -x -C /var/lib/mysql",
        "WALG_MYSQL_BACKUP_PREPARE_COMMAND": "mariabackup --prepare --target-dir=/var/lib/mysql",
        "WALG_MYSQL_BINLOG_REPLAY_COMMAND": "mysqlbinlog --stop-datetime=\"${WALG_MYSQL_BINLOG_END_TS}\" ${WALG_MYSQL_CURRENT_BINLOG} | mysql",
        "WALG_MYSQL_BINLOG_DST": "/tmp/binlogs"
}

[ostinru]

Hi, @Deracination
Do you have binlogs uploaded?

Technically, it is ok. You should be able to restore MariaDB from backup without any issues. However Point in Time Recovery will not work (wal-g doesn't know which binlogs to apply). However I have doubts that PiTR worked for any version of MariaDB.

[Deracination]

Thanks. bin-log archiving has stopped working for MariaDB 10.11. It was working previously.

It throws the following error:

ERROR: 2024/03/02 14:00:02.554562 failed to query mysql variable: sql: Scan error on column index 0, name "@@log_bin_index": converting NULL to string is unsupported