replication error not reported on the replication.log

[Dany40]

Hello;

Using Firebird 5.0.3 64 bit I found this case today (same in 3 diferent database and machine).

It seems the slave-side received a segment (corrupt, I guess ...), and Firebird is not accepting it. The point is that Firebird is not using it for updating the database, but it does not report any issue on the replication.log file.

When I overrided this segment with a new copy (not corrupted, I guess) then Firebird used it.

I attached here the control file and the segment, maybe this is a minor bug that may be fixed.

Regards.

[Ashley Labuschagne]

Hi there 

Is it a corrupt journal file, or is it that the journal files are not in order? 
Did it receive  345 but still waiting for 344 ? 

All the Best
 -ashley

[Daniel Schaer]

Journal file is in order.

--
Support the ongoing development of Firebird! Consider donating to the Firebird Foundation and help ensure its future. Every contribution makes a difference. Learn more and donate here:
https://www.firebirdsql.org/donate
---
You received this message because you are subscribed to a topic in the Google Groups "firebird-support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebird-support/iHWbx4qfIHE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebird-suppo...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/firebird-support/123d7d23-4f6b-4951-b4af-41aac3e26437%40softwareshack.co.za.

[Vlad Khorsun]

Using Firebird 5.0.3 64 bit I found this case today (same in 3 diferent database and machine).

It seems the slave-side received a segment (corrupt, I guess ...), and Firebird is not accepting it. The point is that Firebird is not using it for updating the database, but it does not report any issue on the replication.log file.

  Turn on "verbose_logging" at replica config and you'll see "Skipping file (%s) due to unknown format" message in replicaiton.log

Regards,

Vlad