Issues

• Often in DEV or QA environments, customer found that Iguana was taking a long time to commit

• It also takes a longer time to start up

  • [INFO ] Optimizing Git repositories. This may take a few minutes...

• In some special cases, the commits will fail or timeout

Cause

• Overtime the IguanaMainRepo has too many commit histories which may affect Iguana to update the repo

Solutions

• Cleanup IguanaMainRepo but preserve existing channels and configurations

Steps to Cleanup IguanaMainRepo

1. Create a local temporary repository (e.g “TempRepo”)

2. Ensure all translator changes have been committed

3. Export all your channels with sample data to TempRepo

   • If you are exporting a large amount of channels, export 10-20 channels at a time. This ensures that if there is an issue with Iguana while exporting only some channels must be re-exported.

4. Make a backup of “IguanaMainRepo” folder

5. Make a backup of the “run” and “edit” folders

6. Make a backup of “IguanaConfiguration.xml” file found in IguanaConfigurationRepo folder

7. Stop the Iguana Service

8. Delete the following folders:

   1. Edit, Run, data, IguanaMainRepo, IguanaConfigurationRepo

9. Start the Iguana Service

10. Once started, if Log encryption is enabled, choose reuse existing key option

11. Login to Iguana Dashboard

12. Add local repository (e.g “TempRepo”) and import all channels back

    • If you are importing a large amount of channels, import 10-20 channels at a time. This ensures that if there is an issue with Iguana while importing only some channels must be re-imported.

13. Stop the Iguana Service

14. Overwrite IguanaConfiguration.xml in the new IguanaConfigurationRepo with the backup made in step 6

15. Start the Iguana Service