Replication errors in log files
The following log file messages appearing in the idmsuite.log file indicate replication problems:
Log message | Explanation |
|---|---|
Failed to insert data block into receive queue | Likely means that the local queue – which holds transactions that will be committed to the local database – is either corrupt or full. |
Failed to deserialize record for x | Something in the receive queue could not be parsed. Likely due to disk corruption, queue file corruption or a truncated transmission inbound to the local node. |
Failed to execute replication | Received a transaction from a remote node which should be committed to the local database and failed to execute the relevant stored procedure on the local database. See the remainder of the message for details about which procedure was called and with what arguments. Please refer to the failed procedures log for the data that could not be posted locally. |
Retried proc x times. Aborting. | Unknown (database-related) errors encountered while running stored procedure on the local database. Review contents of the failed procedures log to see what procedure was attempted. |
Failed to initialize the send queue for node. | Something is wrong with the setup of a new queue file which will hold transactions pending transmission to a remote node. The queue file may be corrupted or the disk full. |
Stopping replication to... x, as it is sharing schema with this site. | The local database has a unique schema ID. The remote database also has a unique schema ID. Replication has been configured between the two nodes, but the replication services on the two communication endpoints noticed that the two schema IDs are the same. This implies that the two databases are one and the same (a shared schema) so replication should not be performed. |