Search code examples
bashendeca

How to fix "Failed to obtain lock" error in Endeca?


Endeca does not seems to be popular here, anyway

The problem:

Accidentally kill a running base line update process, and the lock is left-over somewhere.

I wish to find out where the left-over lock is, and to manually remove that.

Not so useful message returned by the base line update script:

INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
INFO: Definition has not changed.
INFO: Starting baseline update script.
WARNING: Failed to obtain lock.

...ended

Alternatively, anyone can provide some links on endeca documentation (without login credential) will be helpful too.


Solution

  • RTFM

    If the running Deployment Template script breaks halfway through its execution due to an unhandled exception, or is manually interrupted by a user pressing Ctrl-C while it is running, the lock remains set within the EAC.

    On Windows: .\runcommand.bat LockManager releaseLock update_lock

    On UNIX: ./runcommand.sh LockManager releaseLock update_lock

    Both the above will work if the default lock name is unchanged (update_lock)