DISP system event notifications.
| Name | Severity | ID | Description | Action |
|---|---|---|---|---|
| ACCEPTING_TOTAL | information | 10 | DISP operation continuing (despite previous errors) as the received update is a total one. | No Operator Action |
| CONSUMER_MISSED_FIRST_UPDATE | error | 5 | The remote consumer claims it missed the first update supplied by this DSA. | Directory replication out of synchronization. Use total update to correct. |
| CONSUMER_MISSED_LAST_UPDATE | error | 6 | The remote consumer claims it missed the last update supplied by this DSA. | Directory replication out of synchronization. Use total update to correct. |
| CONSUMER_UPDATE_ALREADY_RECEIVED | error | 7 | The remote consumer claims it has an update older than the one being supplied. | Directory replication out of synchronization. Use total update to correct. |
| ELECTING_TOTAL | information | 11 | Proceeding supplier operation (despite previous errors) by providing a total update. | No Operator Action |
| FORBIDDEN_MODIFY_DN | error | 50 | This event occurs if an incremental update would require the inclusion of a modifyDN operation when these are forbidden by the shadow agreement's policy. The supplier will attempt a total update unless automatic total updates are also not permitted. | If automatic total updates are forbidden then an operator forced total update will be necessary. |
| FULL_UPDATE_REQUIRED | error | 20 | Full update required before shadowing can proceed. | Directory replication out of synchronization. Use total update to correct |
| ID_MISMATCH | error | 8 | DISP agreement ID or version number mismatch. | Directory replication configuration error. Must be corrected. |
| INACTIVE_AGREEMENT | error | 15 | DISP agreement ID or version number mismatch. | Directory replication configuration error. Must be corrected. |
| INCR_ADD_ATTR_ERR | information | 45 | An add attribute operation failed because the attribute already exists in the target entry. If the existing attribute is the same as the one requested for addition then the error is ignored (this is indicated by the value of 'fatal' in the message detail). | No action. |
| INCR_ADD_TARGET_ALREADY_EXISTS | information | 39 | An add operation in an incremental shadow update is inconsistent because the target entry already exists. | This usually means that the supplier has repeated an already delivered incremental change. No action necessary unless data inconsistency is observed. |
| INCR_ADD_VALS_ERR | information | 47 | An add values operation failed because some or all of the values already exist in the target entry. Never treated as fatal. | No action. |
| INCR_MOD_NO_DIFFS | information | 44 | An incremental modify operation was ignored as the target entry already reflects the changes. | No action. |
| INCR_REM_ATTR_ERR | information | 46 | A remove attribute operation failed because the attribute doesn't exist in the target entry. Never treated as fatal. | No action. |
| INCR_REM_TARGET_DOES_NOT_EXIST | information | 40 | A remove operation in an incremental shadow update was ignored because the target entry does not exist. | This usually means that the supplier has repeated an already delivered incremental change. No action necessary unless data inconsistency is observed. |
| INCR_REM_VALS_ERR | information | 48 | A remove values operation failed because the target entry does not contain some or all of the values requested for removal. Never treated as fatal. | No action. |
| INCR_REPLACE_VALS_ERR | information | 49 | A replace values operation is inconsistent the target entry does not contain an attribute of the given type. | No action. |
| INCR_STEP_UPDATE_ERR | error | 43 | An incremental step update failed on the given entry. | If automatic total updates are forbidden then an operator forced total update will be necessary. |
| INCREMENTAL_DESTINATION_ALREADY_EXISTS | error | 37 | A incremental update operation requiring the creation of a new DN in the database failed because the destination DN already exists. | A total update is required. The DSA will perform an automatic total update if permitted otherwise a manual forced total update will be required. |
| INCREMENTAL_SUPERIOR_DOES_NOT_EXIST | error | 38 | A incremental update operation requiring the creation of a new DN in the database failed because the superior of the DN to be added does not exist. | A total update is required. The DSA will perform an automatic total update if permitted otherwise a manual forced total update will be required. |
| INCREMENTAL_TARGET_DOES_NOT_EXIST | error | 36 | An incremental update operation failed because the target DN does not exist in the database. | A total update is required. The DSA will perform an automatic total update if permitted otherwise a manual forced total update will be required. |
| INCREMENTAL_UPDATE_INFO | information | 32 | Incrementatal update processed. | No Operator Action. |
| INITIATOR_MISMATCH | error | 9 | DISP agreement initiator mismatch. | Directory replication configuration error. Must be corrected. |
| INVALID_AGREEMENT_ID | error | 14 | DISP agreement ID or version number mismatch. | Directory replication configuration error. Must be corrected. |
| INVALID_INFORMATION_RECEIVED | error | 19 | Invalid information received in shadow update. | Contact operator of peer directory in order to correct information being supplied. |
| INVALID_SEQUENCING | error | 17 | Successive shadow coordinates were received or an update was received without a preceding coordinate. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| MISSED_FIRST_UPDATE | error | 2 | Supplier claims that an update has already been sent, when no update has been received. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| MISSED_LAST_UPDATE | error | 3 | The supplier claims an update has already been sent at a given time when no update was received at that time. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| PEER_UNAVAILABLE | error | 1 | Failed to open a connection to a remote DSA for shadowing. | Failure is most likely due to remote directory server not running or network connectivity problem between the servers. Operator should investigate. |
| RECEIVED_FULL_UPDATE_REQUIRED_ERR | error | 26 | Peer DSA returned a full update required error. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| RECEIVED_INACTIVE_AGREEMENT_ERR | error | 23 | Peer DSA returned an inactive agreement ID error. | Directory replication configuration error. Must be corrected. |
| RECEIVED_INVALID_AGREEMENT_ID_ERR | error | 22 | Peer DSA returned an invalid shadow agreement ID error. | Directory replication configuration error. Must be corrected. |
| RECEIVED_INVALID_INFORMATION_RECEIVED_ERR | error | 31 | Peer DSA returned an update already received error. | Directory replication configuration error. Must be corrected. |
| RECEIVED_INVALID_SEQUENCING_ERR | error | 30 | Peer DSA returned an update already received error. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| RECEIVED_MISSED_PREVIOUS_ERR | error | 25 | Peer DSA returned a missed previous update error. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| RECEIVED_UNSUITABLE_TIMING_ERR | error | 28 | Peer DSA returned an unsuitable timing error. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| RECEIVED_UNSUPPORTED_STRATEGY_ERR | error | 24 | Peer DSA returned an unsupported update strategy error. | Directory replication configuration error. Must be corrected. |
| RECEIVED_UNWILLING_TO_PERFORM_ERR | error | 27 | Peer DSA returned an unwilling to perform error. | May be a temporary resource problem. If problem repeats, it is probably a configuration problem with the remote DSA. |
| RECEIVED_UPDATE_ALREADY_RECEIVED_ERR | error | 29 | Peer DSA returned an update already received error. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| SHADOW_PREFIX_NOT_FOUND | error | 34 | An attempt to configure or use a shadow agreement failed as the requested shadow area is not in the target database. | Verify that the shadowed area exists. Verify the DSA database. |
| TOTAL_CLEAN_FAIL | error | 42 | Failed to remove a number of previously existing entries now not present in total update. | This is likely to be because the entries requested for removal are non-leaf entries. This implies a fault in the supplier. |
| TOTAL_ENTRY_CLEAN_FAIL | error | 41 | Failed to remove an entry not present in total update. | |
| TOTAL_UPDATE_ENTRY | debug | 35 | Diagnostic information. | Diagnostic information, no action required. |
| TOTAL_UPDATE_FORBIDDEN | error | 12 | Failed to perform a supplier operation as total updates are disabled. | If a total update is not required, this can be ignored. If total update is required, need to update remote server configuration, or use alternate mechanism such as Isode out of band update. |
| TOTAL_UPDATE_INFO | information | 33 | Total update processed. | No Operator Action. |
| UNSUITABLE_TIMING | error | 21 | Shadow update cannot be accepted at this time. | May be a temporary resource problem. If problem repeats, it is probably a configuration problem with the remote DSA. |
| UNSUPPORTED_STRATEGY | error | 16 | Unsupported strategy requested in shadow coordinate. | Directory replication configuration error. Must be corrected |
| UNWILLING_TO_PERFORM | error | 18 | Two shadow coordinates were received (with no intervening update). | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| UPDATE_ALREADY_RECEIVED | error | 4 | This (consumer) DSA already has the update that the supplier is sending. | Replication protocol error. Use total update if error repeats. May be error in peer directory server. |
| UPDATE_FORBIDDEN | error | 13 | Did not continue with a shadow supplier operation as the agreement is disabled. | May be a temporary resource problem. If problem repeats, it is probably a configuration problem with the remote DSA. |