Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Issue

  • Iguana instance becomes unresponsive and dashboard cannot be reached

  • Crash dump files may or may not be generated

  • Iguana service may be running, but the dashboard is unreachable

Possible Causes and Solutions

Case 1: Quick Troubleshooting steps

  • Restart the Iguana Service

  • Reboot the Iguana Server

  • Check for any anti-viruses and/or backup processes running on the server

  • Verify network settings

Case 2: Browser related Issue

...

Causes

Possible Solutions

Browser Related issues

  • May see “This page isn't working ERR_EMPTY_RESPONSE“

  • Page doesn’t load, unable to access Iguana Dashboard

...

  • Clear Browser Cache

  • To rule out it being a browser related issue, try sending a HTTP/HTTPS request to the web page and it should send a response back:

    • Open Powershell in Command Prompt

      Code Block
      powershell
      Invoke-WebRequest
      uri: http://localhost:6543/

...

It should look something like this:

...

Case 3: Monitor the Iguana Instance

Too Many Open Sockets

...

Error

  • Iguana Logs > “too many open sockets (FD_SETSIZE=2048 reached)”

...

  • This error occurs when you try to open more than 2048 socket connections for an instance of Iguana.

  • Run the socket diagnostic command to check socket usage:

Code Block
http://localhost:<Iguana port number>/socket_diagnostic.html
  • Adjust the IGUANA_WEB_SOCKET_IDLE_TIMEOUT_SECONDS system variable to a lower value (default is 120 seconds) – you can set it as low as one second.

...

Case 5: Reset Network Settings

...

...

External Environment Issue

  • Network issues

  • External application preventing users from reaching Iguana dashboard

Other Issues

(Previous Support Tickets)

  • Iguana logs stored on a shared drive

  • Search of the logs that did not include a time range

  • A source file location that was on a file share which was not up and running

  • Confirm with the team responsible for the server storage whether or not the drive that the Iguana logs are stored on are truly local