Replacing the mariadb server after replication - Error - Waiting for changelog lock.

Hello.
The current scheme is as follows:

1. The Traccar server itself is the (latest) debian 12 version.
2. mariadb 10.11.9 debian 10 master server.
3. mariadb 10.11.12 debian 12 slave server.

I started the transition from debian 10 to 12 and switched slave to master mode.
But Traccar does not stratify. Error Waiting for changelog lock.
Did an update DATABASECHANGELOGLOCK set LOCKED=0
The database was restarted, the Traccar.
It didn't help.
The line ended correctly.
I tried to stop Traccar, mariadb backup, transfer the database to slave and run it.
The Waiting for changelog lock pops up anyway.

I also noticed that when Traccar is launched, the fields LOCKED=1,LOCKGRANTED =now(), LOCKEDBY='unknown';
What can be done?

У меня есть подозрение в разнице версий mariadb.
По идее 10.11.9 и 10.11.12 не имеют глобальных отличий.
Может как нибудь запустить Траккар с отладкой запросов к БД?
Посмотреть на чем он останавливается?
Траккар останавливаю корректно. БД тоже выключаются корректно.

What's in the logs?

[object Object]

Are you sure it's the first launch after clearing the lock?

Yes.
I stopped the Traccar completely.
Then I stopped mariadb.
I did an update DATABASECHANGELOGLOCK set LOCKED=0 on the new database.
But even so, the value was LOCKED=0.
And only then did he start the Traccar .

Now I did logging of sql queries.
The problem is similar after initialization.
It is in md5

[object Object]