Trouble Shooting

There are a number of reasons elm-sync could fail for any CDCM Configuration Area:

1. The network connection to CDCM and/or ELM GCM could fail for any number of reasons, including possibly loosing a VPN connection.

2. The CDCM or ELM GCM server may be temporarily shut down or is otherwise unavailable while elm-sync is still running

3. The CDCM change log could be rebased, pruned, or the trs:order could exceed its maximum value and wrap around rendering the object_mapping last_seen_order invalid.

4. There could be a coding error that results in an unrecoverable exception

This version of elm-sync has no automated validation and repair facilities. Synchronization errors are captured in the object_mapping entry for a CDCM configuration areas with state LOADING_ERROR or TRS_ERROR. These entries are skipped on all subsequent sync iterations. Manual recovery is required.

To see if there are any elm-sync errors, use (replacing localhost:8080 with your host and port):

Open

This lists the CDCM configuration area to ELM GCM project area mappings that have sync errors.

Click on Error Details, and/or examine the elm-sync log to find the cause of error using the information to diagnose and correct the error.

If the mapping error is LOADING_ERROR, then the error occurred during the initial sync of a CDCM configuraiton area to a new ELM GCM project area. Recovery from these errors requires the ELM GCM project area to be renamed and archived, and the initial sync of the CDCM configuration area is tired again after the issue has been addressed.

If the mapping error is TRS_ERROR, then the error occured during the processing of a CDCM change event. Recovery from these errors can be done by trying the operation again after the issue has been addressed. The TRS event causing the error will not be lost, it will be retried.

Once the issues identified in the log have been addressed, you can retry the operations by clearing one or all of the mapping errors. To clear an individual mapping error, click Repair on the desired row, or use:

Where mappingId is the identifier of the mapping error as shown in the …/mapping request.

To clear all mapping errors and retry all operations, click Repair All, or use:

Use this with caution and when you are sure all of the issues causing the errors have been addressed. For example, if the elm-sync errors were caused by the ELM GCM server being down, then repairing all the errors after bringing the server back up would be appropriate.

Note that all LOADING_ERRORS will result in the ELM GCM project area to be archived and recreated. So you should ensure the issues causing the error have been addressed before retrying the operation too many times.

Refresh the sandbox/mapping/ page after any repair operation to see the updated state of each configuration area mapping.