Prerequisites

  1. Download ant.
  2. [bacon@bacon] bzip2 -dc apache-ant-1.5.3-1-bin.tar.bz2 | tar xf -
  3. [bacon@bacon] export ANT_HOME=`pwd`/apache-ant-1.5.3-1
  4. Download java
  5. [root@bacon root]# rpm -i j2sdk-1_4_1_03-fcs-linux-i586.rpm
  6. [bacon@bacon] export JAVA_HOME=/usr/java/j2sdk1.4.1_03
  7. [bacon@bacon] export PATH=$ANT_HOME/bin:$JAVA_HOME/bin:$PATH
  8. Download Postgresql. From this step on, the prerequisites are optional, and used by RFT and RLS. You may also perform these steps at a later date. 
  9. [bacon@bacon] rpm -qa | grep postgresql
postgresql-server-7.2.2-1mdk
postgresql-7.2.2-1mdk
  10. Edit /etc/init.d/postgresql so that the startup line looks like:
    su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -o '-i' -D $PGDATA -p /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null
    The addition is in the -o '-i'. That allows postgresql to accept TCP/IP connections.
  11. Run /etc/init.d/postgresql start. The first time, this will create /var/lib/pgsql/data. If you want to accept internet connections from machines other than your own, you will need to edit /var/lib/pgsql/data/pg_hba.conf. Please see Postgresql docs on how to accomplish this.

The installer

  1. Download the installer from the download page.
  2. Untar the installer.
    • If you are using JDK 1.3.1, you will need to let ant know where to find jaas.jar. You can set "ANT_OPTS=-Djava.ext.dirs=<dir of jaas.jar>" to accomplish that. After your installation is complete, copy jaas1_0_01/lib/jaas.jar to $GLOBUS_LOCATION/lib.
  3. [bacon@bacon] ./install-gt3 /home/bacon/pkgs/gt3 |& tee install.log

    This step will take a while. If you would like to see more verbose logging output, edit the script and add "-verbose" to the definition of GPT_BUILD and GPT_INSTALL. This is a good time to grab a snack.

  4. [bacon@bacon] grep ERROR install.log

    If you look through the install log, make sure to find the first error listed. Initial errors will cause subsequent failures in dependent components. For instance, the first time I was installing, I saw the following when I was done: 

    running /home/bacon/pkgs/gt3/setup/globus/setup-mjs-fork...
Can't open perl script "/home/bacon/pkgs/gt3/etc/setup-mjs.pl": No such file or directory
ERROR: Command failed
Can't open perl script "/home/bacon/pkgs/gt3/etc/setup-mmjfs.pl": No such file or directory

    It turns out that the real failure was far above. core failed to build because I was missing junit.jar. So if you have an error to report, please try to identify which error caused any later errors.

    Also, note that it's normal to see the following if you don't have PBS installed: 

    configure: error: Cannot locate qstat
Error finding pbs tools
loading cache ./config.cache
checking for qstat... no
ERROR: Command failed

    These errors are also listed in the debugging section of this manual.

Post-installation setup

There are a few steps remaining to be run.
  1. [bacon@bacon] cd /home/bacon/pkgs/gt3
  2. [bacon@bacon] ant setup
  3. [root@bacon]# mkdir /usr/java/j2sdk1.4.1_03/jre/lib/endorsed
  4. [root@bacon]# cp endorsed/xalan.jar /usr/java/j2sdk1.4.1_03/jre/lib/endorsed
  5. [root@bacon gt3]# export GLOBUS_LOCATION=`pwd`
  6. [root@bacon gt3]# setup/globus/setup-gsi
    • Hit 'y' to continue
    • Hit 'q' to save values.
  7. [root@bacon gt3]# bin/grid-cert-request -host bacon.mcs.anl.gov
  8. Send /etc/grid-security/hostcert_request.pem to ca@globus.org using your ordinary mail client, from a domain associated with the host in your request.
  9. Get a credential back in the mail. Make sure the account can receive mail! This is often a problem if you follow the instructions to run 'cat ... | mail ca@globus.org".
  10. After you get a hostcert, run install-gt3-mmjfs. Run setperms.sh as root. This will enable grim and mmjfs.
  11. If you ran install-gt3-mmjfs before you had a hostcert, your container startup will fail. While you wait for a hostcert so that globus-grim can run correctly, you can comment out the following lines in server-config.wsdd to run without grim: 
    <!-- <parameter name="containerHandlers"
      value="org.globus.ogsa.impl.security.grim.GrimContainerHandler 
             org.globus.ogsa.impl.base.gram.mmjfs.UHERestartHandler"/>
      -->
<!-- <parameter name="containerProxy" value="/tmp/x509cp_bacon_grim"/> -->

    As a reminder, this is only a workaround for people who run install-gt3-mmjfs without having a hostcert or the ability to make bin/globus-grim setuid.

So, how is everything?

  1. [bacon@bacon] export GLOBUS_LOCATION=`pwd`
  2. [bacon@bacon] source etc/globus-user-env.sh
  3. [bacon@bacon] bin/globus-start-container -p 8080
    • This should start up the gridservices hosting environment. You will see a list of services hosted in the container go by. Control will not return to the terminal. If you would like to start a container and keep logs, I use the command
      nohup bin/globus-start-container > var/mhe.log & to put it in the background and keep a log.
    • If you get errors, or the container exits after starting, see the debugging section. Otherwise, move on to service configuration.

For support, please see the Support Page

bacon@mcs.anl.gov
Last modified: Tue Jul 15 16:20:41 CDT 2003