Hello Dmitry, > These settings are not necessary for synchronous-only setup. Moreover, > removing them will actually cause your issue to disappear ;-) But this way > we'd never find this bug ;-)
So that I get it right. There is no bug in the synchronous replications. There is an bug in the asynchronous replication respectively the logging for the replications replication. Removing this setting means synchronous replications works well. Correct? With best regards Nils Bödeker > > Am 17.05.2021 um 19:18 schrieb Dmitry Yemanov <firebi...@yandex.ru>: > > 17.05.2021 16:29, Nils Bödeker wrote: >> Under parallel writing we get the following error in the replication log >> (sometimes, not always): >> ---------------------------------------------------- >> FIREBIRD-4 (origin) Sat May 15 12:11:23 2021 >> Database: D:\NBS_DATABASE\MINICMS.GDB >> ERROR: Log file D:\nbs_database\Replication\Log\MINICMS.GDB.chlog-000000026 >> rename failed (error: 32) > > Looks like a bug, I'm investigating. It seems to be specific to Classic > Server. > >> ---------------------------------------------------- >> log_directory = D:\nbs_database\Replication\Log >> log_archive_directory = D:\nbs_database\Replication\LogArchive >> log_archive_command = "copy $(logpathname) $(archpathname)" > > These settings are not necessary for synchronous-only setup. Moreover, > removing them will actually cause your issue to disappear ;-) But this way > we'd never find this bug ;-) > >> source_guid = 6F9619FF-8B86-D011-B42D-00CF4FC964FF > > This setting belongs to the replica side of the asynchronous setup, it may be > removed. > > > Dmitry > > > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
