Introduction
Iguana does not does not start up correctly. There are two symptoms: Iguana will not start at all, or it starts but then shuts down (almost) immediately.
There are a couple of common causes:
- The Iguana service/daemon does not have full read/write access to its working directory
- Iguana been improperly shut down
Note: On rare occasions it is possible that the Iguana local repository can get get corrupted — see Causes of Iguana local Repository Corruption for advice on how to fix this.
Issue [top]
Iguana will not start, or shuts down very soon after restarting.
Solution [top]
These are solutions for the two most common issues.
Iguana does not have full read/write access to its working directory:
- Grant read write permission for the Iguana working directory to the user that runs the Iguana service/daemon
- Restart the Iguana service/daemon
Iguana was shut down incorrectly:
- If the previous Iguana service/daemon is still running in an “indeterminate” or “zombie” state:
- This “zombie” process can cause a port conflict when you try to restart.
- Identify and close the previous (zombie) Iguana instance.
- If this does not work then restart the server that Iguana is running on.
Note: To ensure that Iguana is always shutdown correctly, follow the instructions in Gracefully Stopping Iguana Service on Windows and Gracefully stopping Iguana service/daemon on Linux.
These articles also have more detailed information on the problems caused when Iguana is not shut down cleanly.
Prevention [top]
- Ensure that Iguana the Iguana service/daemon has read/write access to its working directory.
- Ensure that Iguana is always shutdown correctly, see Gracefully Stopping Iguana Service on Windows and Gracefully stopping Iguana service/daemon on Linux.
More Information [top]
- Iguana is Slow or Hangs on a Mac
- Troubleshooting Unresponsive Channels
- Gracefully Stopping Iguana Daemon on Linux
- Gracefully Stopping Iguana Service on Windows