Fisheye Does Not Start Due To Lock Files, fisheye.lck, write.lock

Symptoms

Fisheye/Crucible doesn't start. Messages of the following type are logged:

• ERROR [main ] fisheye.app InstanceLock-acquireLock - Lock already locked <FISHEYE_INST>/fisheye.lck

• ERROR [main ] fisheye.app Run-mainImpl - Another instance of FishEye and Crucible seems to be running

  and

• Problem starting FishEye and Crucible: com.cenqua.obfuscate.<unique_identifier_here>.locking.FileLockedExternallyException: Cannot lock file in exclusive mode - already in use

  and

• Caused by: org.apache.lucene.store.LockReleaseFailedException: Cannot forcefully unlock a NativeFSLock which is held by another indexer component: <FISHEYE_INST>/data/cache/globalfe/idx0/write.lock

E.g.:

and

and

Cause

Two possible causes exist. Either:

1. Fisheye prevents multiple instances from running on the same server and as such, creates lock files for itself as well as activity lock files for internal database activity:

   1. Application lock file:

      fisheye.lck

   2. Repository lock files:

      ./var/cache/<repository_name_here>/idx0/write.lock

      ./var/cache/<repository_name_here>/idx1/write.lock

      ./var/cache/<repository_name_here>/idx2/write.lock

   3. Indexing library lock files (these store review data):

      ./cache/cruidx/idx1/write.lock

      ./cache/globalfe/idx0/write.lock

      ./cache/globalfe/idx1/write.lock

      These files aren't properly removed if Fisheye is shutdown using an alternative method other than using the stop.bat script or if you are running Fisheye as a service, the "Stop service" feature (or if the server/application crashes). A restarting Fisheye instance won't start if it detects these leftover .lck and .lock files.

      Or:

2. A crashed instance of Fisheye can corrupt one of its internal database data files, e.g. <FISHEYE_INST>/var/data/data0.bin

Resolution

Depending on the cause above, choose one of the resolutions below. Either:

1. If you don't see any Java processes running you can safely delete these lock files (search for and delete .lck and .lock files) and try restarting your instance. Check for a running Fisheye process:

   1. ps -ef | grep java

   2. lsof | grep data*.bin

      Or:

2. The data*.bin file is an internal database data file that contains mostly user and group membership information and other data related to your settings.

   1. If this file exists, save a backup copy.

   2. Replace it with a backup version OR if you don't have a backup copy, remove the file completely and it will be created anew upon successful start – note that you will have to recreate/re-do your settings in this case.