Issue

A customer restarts Iguana and all their channels and configurations are gone. This happens because the IguanaConfiguration.xml gets corrupted. Corruption happens from commits that empty the IguanaConfiguration.xml. Iguana is able to run fine with an empty IguanaConfigration.xml, but when it is restarted, it will empty the channels.

Causes

• Iguana runs out of memory while building the configuration.xml

• Bugs that empty configuration.xml

Solutions

1. Check the last update on the emptied IguanaConfiguration.xml

2. Restore a backed up IguanaMainRepo prior to the IguanaConfiguration.xml being emptied

3. Reinstall Iguana following these steps:
   https://help.interfaceware.com/v6/backup-and-restore

If they do not have a back up

Iguana 6

1. Analyze their IguanaMainRepo from sourcetree:
   https://interfaceware.atlassian.net/wiki/spaces/CSHC/pages/1032618281

2. Find the commit that emptied the IguanaConfiguration.xml

3. Revert the commit until that point

4. Reinstall Iguana following these steps:
   https://help.interfaceware.com/v6/backup-and-restore

Iguana 5

1. Obtain the customers IguanaConfiguration.xml and vcs_repo.sqlite

   1. This will not work if the scripts are missing from vcs_repo.sqlite

   2. IguanaConfiguration.xml must have some data in it

2. Modify the IguanaConfiguration.xml to be in a valid format, you will need to add and delete lines

   1. You can compare it to the default Iguana 5 configruation.xml to get the correct format

3. Start Iguana with the modified configuration.xml and vcs_repo.sqlite file in the working directory

4. You should be able to get some configurations (not all)