Sync fails with logged error of "Exception caught during execution of rm command"

Version/Environment (if relevant):

All

Issue:

A sync may fail with a non-descript failure error in a red toaster box that your sync has failed.  In the log output of your run you may see the error:

Exception caught during execution of rm command

Root Cause:

A prior failed sync may have left behind a lock file:

/mnt/execution-vol/mnt/.domino/repo/.git/index.lock.  

Note that the dispatcher log may also contain an exception similar to the following:

ERROR [d.e.r.WorkingDirSynchronizer] Error while synchronizing working directory correlationId="ULpAKqklsA" request="WorkingDirectorySynchronizationRequest(true,false,None,Some(<userid> <user email address>),Some(SyncOperationInfo(a73d2901-c21f-490b-b371-d0a234defab3,onlyDfs)))" thread="application-akka.actor.default-dispatcher-38" 5org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command

Resolution:

Remove the lock file.  Note that from with a workspace the path to this lock file will be:

/mnt/.domino/repo/.git/index.lock 

So execute the command:

$ rm /mnt/.domino/repo/.git/index.lock 

As an admin if you exec'ing in to the running pod the full path to this lock file will be:

/mnt/execution-vol/mnt/.domino/repo/.git/index.lock 

If you are unable to remove this file there may be a running process that may have an open lock on the file so stop the workspace and restart it to lift the filelock and then reattempt the delete with the 'rm' command.

Notes/Information:

There is an open bug with Domino engineering to correct this problem and provide better error messaging: DOM-40935