Grid Engine Home > Installing > Installing the Software With the GUI Installer >

Troubleshooting the GUI Installer

You will find the known issues and their workarounds in this section as well as additional answers to some frequently asked questions.

FAQs

1. I cannot start the installer. It throws an exception!
   Most likely a general problem with any GUI application in your current environment. You are probably starting the installer on a remote host and either did not export the DISPLAY variable properly or did not allow displaying remote GUI applications on the target system (where the GUI should pop-up).
   

   1. Display variable is not set.
      If your DISPLAY variable is not set and you are not locally on the system you will see a similar message:

      hostA# ./start_gui_installer 
      Starting Installer ...
      java.awt.HeadlessException: 
      No X11 DISPLAY variable was set, but this program performed an operation which requires it.
              at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)
              at java.awt.Window.<init>(Window.java:317)
              at java.awt.Frame.<init>(Frame.java:419)
              at java.awt.Frame.<init>(Frame.java:384)
              at javax.swing.JFrame.<init>(JFrame.java:150)
              at com.izforge.izpack.installer.GUIInstaller.loadLangPack(Unknown Source)
              at com.izforge.izpack.installer.GUIInstaller.access$000(Unknown Source)
              at com.izforge.izpack.installer.GUIInstaller$1.run(Unknown Source)
              at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)
              at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
              at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
              at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
              at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
      java.lang.NullPointerException
              at com.izforge.izpack.installer.GUIInstaller.loadGUI(Unknown Source)
              at com.izforge.izpack.installer.GUIInstaller.access$100(Unknown Source)
              at com.izforge.izpack.installer.GUIInstaller$2.run(Unknown Source)
              at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
              at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
              at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
              at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
              at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
              at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
      

      If you start the installer on hostA, but want to display it on hostB, you need to set a proper DISPLAY variable. If hostB has your graphical session on port 22, type the following command as user that will start the installer:

      hostA# DISPLAY=hostB:22 ; export DISPLAY
      

      See next step to finish the setup.
      
      

   2. Remote host does not allow remote GUI applications.
      In this case you will see a similar message:

      hostA# ./start_gui_installer 
      Starting Installer ...
      Xlib: connection to "hostB:22" refused by server
      Xlib: No protocol specified
      
      Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using 'hostB:22' as the value of the DISPLAY variable.
              at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
              at sun.awt.X11GraphicsEnvironment.access$000(X11GraphicsEnvironment.java:53)
              at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:142)
              at java.security.AccessController.doPrivileged(Native Method)
              at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:164)
              at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
              at sun.awt.motif.MToolkit.<clinit>(MToolkit.java:93)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:164)
              at java.awt.Toolkit$2.run(Toolkit.java:821)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:804)
              at javax.swing.UIManager.initialize(UIManager.java:1262)
              at javax.swing.UIManager.maybeInitialize(UIManager.java:1245)
              at javax.swing.UIManager.getDefaults(UIManager.java:556)
              at javax.swing.UIManager.put(UIManager.java:841)
              at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(Unknown Source)
              at com.izforge.izpack.installer.GUIInstaller.<init>(Unknown Source)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
              at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
              at java.lang.Class.newInstance0(Class.java:350)
              at java.lang.Class.newInstance(Class.java:303)
              at com.izforge.izpack.installer.Installer.main(Unknown Source)
      

      You have to explicitly allow remote GUI connections from hostA. Type the following command as the user running the graphical session on hostB:

      hostB# xhost +hostA
      

      Now you may start the start_gui_installer and the Welcome screen should get displayed on the remote host.

2. How can I remove a host from the host selection that I previously added?
   Right_click the host and select Remove selected action from the pop-up menu.
   

3. Can I save hosts that I selected in the host selection to a file?
   Yes, you can. Select multiple hosts using CTRL + left-click and do a right-click. A pop-up menu appears allowing you to save all hosts in the current tab or just the selected hosts.
   

4. Qmaster JMX thread does not appear to be running.
   The qmaster messages file shows message could not load libjvm ld.so.1: sge_qmaster: fatal: jvm_missing: open failed: No such file or directory. Message means that the installer could not auto-detect a suitable JVM library. Possible reasons include being on a 64-bit platform and not having the 64-bit Java installed at all on the target hosts. Once you install correct Java you may change the libjvm_path attribute from jvm_missing to the correct path to the JVM library by calling qconf -mconf command.

Known issues and workarounds

1. Installing BDB server always fails with a timeout state.
   Unfortunately you can't currently use the GUI installer to install a BDB server to any other platform, but Solaris OS. You may use the CLI installation (inst_sge -db) to do the job locally. You may then use the GUI installer to install qmaster and any number of shadow and executions hosts if the password-less access is configured. See issue 2941 for more information.
2. Cannot install additional execd hosts from a remove host (different from qmaster) when qmaster was installed with CSP or JMX SSL and a custom connect user is used.
   It's recommended to always start the installation in the qmaster host. The reason is that in the subsequent standalone execd installation there is no way to specify a connect user for qmaster host. The remote connection to a qmaster host will be attempted as a user who started the GUI installer.