Turning on CAS SDK logging

While running a CAS migration, you may run into some errors that cannot be explained by the logs or database within ecs-sync. Since ecs-sync uses the CAS SDK under the covers to handle all CAS transactions, and that SDK is a collection of native libraries, it may be impossible for ecs-sync (which is a Java application) to determine the cause of the error.

In these cases, we recommend turning on CAS SDK logging. This is done by setting an environment variable in root's profile and creating a configuration file. Edit root's profile (sudo vi /root/.bash_profile) and add the following line to the end of the file:

export FP_LOG_STATE_PATH=/var/log/ecs-sync/cas-sdk.config

Then create a config file as the ecssync user (vi /var/log/ecs-sync/cas-sdk.config) and paste the following:

##################################
# FPLogState Configuration File
##################################
FP_LOGPATH=/var/log/ecs-sync/cas-sdk.log
FP_LOGLEVEL=3
FP_LOGFORMAT=TAB
FP_LOGFILTER=ALL
FP_LOGKEEP=APPEND
FP_LOG_DISABLE_CALLBACK=TRUE
FP_LOG_STATE_POLL_INTERVAL=1
FP_LOG_MAX_SIZE=10240
FP_LOG_MAX_OVERFLOWS=1

(please be sure you know how to use the vi tool, or use a different editor to change these files).

Once this is done, you need to restart the ecs-sync service:

sudo systemctl stop ecs-sync
sudo systemctl start ecs-sync

Then you can attempt to re-migrate the failed objects and you should get additional information in /var/log/ecs-sync/cas-sdk.log.