The following is a list of known issues that may arise while installing or attempting to run Iris. If you encounter a problem that is not listed here, first check for it on the Iris Bugs & Caveats page, and then contact the CXC Helpdesk for assistance, if necessary. It is recommended that you include in your bug report the results of the Iris installation smoke test.
I do not have the Java version required to run Iris.
When you run the Iris startup command, the application does not open; the SED Importer startup command fails with an error message. This likely indicates that you do not have the minimum required Java version on your system to run the Iris application; or you do, but your global 'path' variable points to an older Java version which coexists on your system with the up-to-date one. In the case of the former, you should upgrade to at least Java SE 6 (version 1.6) by following the installation instructions for the Java Runtime Environment (JRE) specific to your computer platform, on the Oracle website.
In the case of the latter, first check to see if your path points to an older version of Java on your system; if so, contact your systems administrator to find out if a newer version of Java is available elsewhere on your system.
For example, the output below shows that the global path variable is pointed to a directory containing an outdated version of Java.
% which java /usr/bin/java % java -version java version "1.4.2" gij (GNU libgcj) version 4.1.2 20080704 (Red Hat 4.1.2-50)
Checking /usr/local/bin, however, reveals that an up-to-date Java version coexists on the system with the older version:
% /usr/local/bin/java -version java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)
Editing the global path variable so that the directory containing Java SE 6 is searched before the directory containing the older version, will allow Iris to properly install.
% set path = (/usr/local/bin $path) % Iris &
Adding the "set path ..." line shown above to your user preferences file for the shell, e.g. ~/.cshrc.user or ~/.cshrc for the tcsh shell or ~/.bashrc for bash shell, will make this change permanent; running it in the terminal window will alter the path only temporarily, i.e., for that particular terminal session.
I exited Iris with a Force Quit or 'kill' command; now it does not run properly.
If the Iris application is killed off either by Force Quit (on Linux or Mac) or the 'kill' command, as opposed to the Iris "File -> Exit" menu option, the Sherpa program may survive as a spurious Python process. As a result, the next time you try to use Iris, it may not work properly. To remedy the problem, you can end the spurious process using 'ps' and 'kill' or using System Monitor. The process name should appear as something like 'python2.7'.
This occurs because Iris is responsible for starting and stopping the Sherpa Python process. If Iris is killed without executing its usual shutdown procedure, Sherpa could be left running. Since Iris uses SAMP to communicate, the spurious Sherpa process can conflict with Iris when it tries to establish a new connection.
You can also confirm the issue by inspecting the Iris log file located in your home directory, ~/.vao/iris/log.txt, which should contain an error message indicating the problem.