Fix local Repository corruption after upgrading/migrating Iguana

Introduction

The Iguana local repository can be corrupted if you do not follow the correct procedure when migrating or upgrading Iguana.

When the Iguana repository is corrupted you will receive errors like revspec not found or refs/heads/master not found. This article covers causes and solutions for repository corruption during upgrade or migration.

Note: If these errors did not occur immediately after a migration or upgrade then then read the Causes of Iguana local Repository Corruption FAQ.

Issue [top]

One of these errors revspec not found or refs/heads/master not found occurs immediately after you have migrated or upgraded Iguana.

Cause [top]

In general Iguana repository corruption is caused by not following the correct procedure when migrating or upgrading Iguana.

Iguana has two copies of the local repository a main version (IguanaMainRepo) and working copy (IguanaConfigurationRepo). Issues occur when these two get out of sync, or the working copy contains invalid information. When you are upgrading or migrating Iguana you must not copy the the working repository! Iguana will create a new copy of the working repository using the information stored in the main repository (IguanaMainRepo).

Most problems are caused when you move/copy the <working directory>/IguanaConfigurationRepo, during an upgrade or migration. This is because the (old) working repository contains hard coded remote paths pointing to the old/invalid working directory location (which corrupts the repository structure). It is not necessary to copy the working repository (IguanaConfigurationRepo) as Iguana will create a new version of it when the Iguana service/daemon starts.

Specific migration/upgrade mistakes that cause errors (by moving/copying an old IguanaConfigurationRepo) include:

  • Copying your whole working directory.

    Trying to migrate/upgrade Iguana by copying your whole working directory in Iguana 6 instead of moving just the IguanaMainRepo (and logs, etc).

  • Migrating into an old working directory (by moving IguanaMainRepo).

    Migrating into an old working directory (by just moving IguanaMainRepo) will cause an issue if the the location has previously existing <working directory>/IguanaConfigurationRepo folders.

  • Migrating by changing the path to the working directory.

    Changing the path to the working directory (as in renaming working directory from C://Program Files/iNTERFACEWARE/iguana606/ to C://Program Files/iNTERFACEWARE/iguana607) counts as a “migration” to a different directory.

Solution [top]

If after performing these procedures, you are still receiving the error, contact support

  1. The primary solution is to perform the migration again:
  2. Alternatively you can:
    • Stop Iguana.
    • Delete the <working directory>/IguanaConfigurationRepo folders.
    • Restart Iguana.
      Note: Iguana will automatically create the IguanaConfigurationRepo folders on startup using information in the local repository (in the IguanaMainRepo folders).
    • If this does not work you will need to follow method (1) and perform the migration again.

Note: If these errors did not occur immediately after a migration or upgrade then then read the Causes of Iguana local Repository Corruption FAQ.

Prevention [top]

In general if you follow our practices on how to migrate or upgrade Iguana — then these issues should not occur.

More specifically do not do any of the things described in the Cause section above.

Leave A Comment?