Replication errors

Edit online

You can troubleshoot replication errors by using the replication logs.

Replication errors for each replication server are logged in a log file. You can troubleshoot the replication errors by looking at the log and taking the required action. Following is a list of the replication error codes and messages that are logged:
  • CBXRN0000E: Unable to start a FaspManager session (connection to the other replication server)
  • CBXRN0001E: Unable to replicate the file (see the replication server log for specific information)
  • CBXRN0002W: A replication server is marked offline after several failed attempts
  • CBXRN0003E: All replication servers for data center {0} are offline.
  • CBXRN0004E: An error occurred in session with replication server
  • CBXRN0005E: An error occurred while replicating file from replication server
  • CBXRN0006E: Unable to look up Scheduled Executor service
  • CBXRN0007E: While polling replication requests, an exception occurred. Specific error is: {0}
  • CBXRN0008E: Unable to remove barrier
  • CBXRN0009E: Unable to update replication request status

You can set up a log viewer for automatic alerts or notifications.

The format of the error message is as follows:

[time stamp] [thread ID] [class] [logging level] [error ID]: [error message]