Trouble Shooting

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

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

2. The network connection to CDCM and/or ELM GCM could fail for any number of reasons.

3. One common issue that can happen when running elm-sync on your local machine is you computer could go to sleep while elm-sync is running, and eventually loose its VPN connection. When the computer wakes up and elm-sync starts syncing again, communication to CDCM will fail because the VPN connection is closed. You can recover from this by simply editing each impacted row in the object_mapping table with state:ERROR, set the state to IDLE and start elm-sync. It will now pick up where it left off.

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

5. 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.

This version of elm-sync has no automated validation and repair facilities. So if an object_mapping entry has state: ERROR, the entry is skipped on all subsequent sync iterations. Manual recovery is required and can be accomplished by one of the following (in the preferred order):

1. Examine the elm-sync log to find the cause of the error. Depending on what the error is, you may be able to correct the issue, and put the object_mapping entry back into the IDLE state to resume synchronization of TRS change events.

2. If you can’t find the problem, or it is not possible to fix it, you can start over for the for the CDCM configuration area by:

   1. Stop the elm-sync server

   2. Rename and archive the ELM GCM project area associated with the row with state: ERROR

   3. Delete the row with state:ERROR from the object_mapping table

   4. Restart elm-sync and let the project area be recreated and synchronized.

   5. In some cases you may have to also restore the object_mapping project_area_uri if it has been deleted and is null.

The first approach is best because it preserves any existing uses of the synced ELM GCM project area and its configurations. The second approach makes all these links broken so user will have to update all their ELM configurations to use the newly synced project area and configurations.