Cisco IOS XR System Error Message Reference Guide, Release 4.3.x
Library Messages
Downloads: This chapterpdf (PDF - 318.0 KB) The complete bookPDF (PDF - 18.29 MB) | Feedback

Table of Contents

Library Messages

REPLICATOR Messages

Library Messages

This section contains all Library related System Error Messages.

REPLICATOR Messages

Error Message %LIBRARY-REPLICATOR-3-BAD_HANDLENAME

Handle name ([chars]) has been corrupted. rc: [hex] ([chars])

Explanation The replicator library got an error back from NRS indicating that the data handle is no longer valid. This handle would have been validated on initialisation, so the likely cause of this error is memory corruption. The client process will be forcibly restarted to try to recover.

Recommended Action *RECUR*

Error Message %LIBRARY-REPLICATOR-3-IDT_FAIL

Failed to complete IDT after several retries: rc [hex] ([chars])

Explanation The replicator has repeatedly failed to complete IDT for a system data handle. There may be problems with communications or other low-level infrastructure.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-3-LARGE_HANDLE

Large item handle detected ([hex]/[hex])

Explanation The replicator library has received an exceptionally large item handle from NRS which may cause conflicts within the replicator library.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-3-WRITE_OWNERSHIP_FAIL

Failed to acquire data handle after several retries: rc [hex] ([chars])

Explanation The replicator has repeatedly failed to acquire ownership of a system data handle. The client process may need restarting.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-BAD_MAGIC

A corrupted peristent data structure was discovered ([chars])

Explanation The replicator library discovered a bad magic number in a persistent data structure. This suggests that the data has been corrupted. The replicator library will attempt to recover the situation.

Recommended Action *RECUR*

Error Message %LIBRARY-REPLICATOR-7-CTX_NOT_FOUND

Could not access [chars] context structure: rc [hex] ([chars])

Explanation The replicator library was unable to access an internal structure. This may result in failure of data replication to the standby node(s).

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-INTERNAL

[chars]: rc [hex] ([chars])

Explanation The replicator library has either failed a function that expected to succeed, or has got into an inconsistent state.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-LOCKING

Failed to [chars] [chars]. Error [dec] ([chars])

Explanation The replicator library has either failed to aquire or release a lock.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-MEMORY

Failed to malloc %zu bytes

Explanation The replicator has failed to acquire the required amount of memory.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-NO_CB

No completion notification received for update message [unsigned int]

Explanation The replicator library did not receive a callback from the transport library. The update will be allowed to continue without the replication acknowledgement. If any replicas have not received the update, they will resync on the next update.

Recommended Action *RECUR*

Error Message %LIBRARY-REPLICATOR-7-SEND_FAILED

Failed to send update: rc [hex] ([chars])

Explanation An error was returned from RDS when trying to send an update. Clients will handle this condition differently either by retrying later, or failing the operation. If this condition persists, data may be lost on failover.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-UPDATE_FAILED

Failed to apply [chars] update: rc [hex] ([chars])

Explanation The client returned an error when trying to apply an update. The replicator library will try to recover by requesting a replay of the update. If this condition persists, data may be lost on failover.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %LIBRARY-REPLICATOR-7-WRITE_OWNERSHIP

Failed to acquire data handle: rc [hex] ([chars])

Explanation The replicator has failed to acquire ownership of a system data handle.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.