Hello We observer an possible replicate bug.
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) FIREBIRD-4 (origin) Sat May 15 12:11:23 2021 Database: D:\NBS_DATABASE\MINICMS.GDB ERROR: Replication is stopped due to critical error(s) ---------------------------------------------------- The Environment is: WindowS 2019 Firebird 64 Bit Classic Server Master and 2 Slaves on same Server Synchron Replication The setting file: ---------------------------------------------------- database { ### PRIMARY SIDE SETTINGS log_errors = true # All errors (and warnings) are written to replication.log report_errors = false # Errors are returned to the client application buffer_size = 1048576 # 1MB log_directory = D:\nbs_database\Replication\Log log_archive_directory = D:\nbs_database\Replication\LogArchive log_archive_command = "copy $(logpathname) $(archpathname)" source_guid = 6F9619FF-8B86-D011-B42D-00CF4FC964FF verbose_logging = true } database = D:/nbs_database/MINICMS.GDB { sync_replica = sysdba:masterkey@firebird-4:D:/nbs_database/MINICMS_Slave01.GDB sync_replica = sysdba:masterkey@firebird-4:D:/nbs_database/MINICMS_Slave02.GDB } ---------------------------------------------------- Is this really a bug or a setting Problem? With best regards Nils Bödeker
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel