[클러스터] globus 3.2 설치 하기

GT3.2 설치

작성자: 김상완(sangwan@kisti.re.kr)

최초 작성일: 2004-07-08

이 문서는 GT3.2를 설치하는 방법을 설명한다.

문서 업데이트 상황

최초 작성후 업데이트 업음.

목차

1. GT3.2를 설치하기 전에

2. 필요한 소프트웨어 설치

  2.1. Java2 SDK 설치

  2.2. Ant 설치

  2.3. Junit 설치

3. 글로버스 설치

  3.1. 인스톨러 실행

  3.2. 환경설정

  3.3. Setuid 퍼미션 변경

4. 보안 설정

  4.1. Globus SimpleCA를 이용

  4.2. 호스트 인증서 설치

  4.3. 사용자 인증서 설치

  4.4. 프록시 초기화하기

  4.5. Grid-mapfile에 사용자 추가

5. 테스트

  5.1. 컨테이너 실행

  5.2. Fork 작업 예제 실행

  5.3. 프로세스 모닡터링

  5.4. 컨테이너 종료하기

참고문서

——————————————————————————–

1. GT3.2를 설치하기 전에  [[목차]]

GT3.2를 설치하는 방법은 글로버스 사이트에 있는 다음 문서를 참조하여도 된다.

– http://www-unix.globus.org/toolkit/docs/3.2/index.html

이 문서에서는 레드헷 리눅스 9에서 bash 쉘을 사용한다고 가정하겠다.

리눅스 설치후 globus라는 사용자 계정을 만들어 globus 계정으로 GT3를 설치한다.

globus 계정의 홈디렉토리는 /home/globus 이고, 쉘 환경 설정을 위해 ~/.bashrc 를 수정한다.

글로버스 계정이 없으면 만든다.

[root]# adduser globus

[root]# passwd globus

2. 필요한 소프트웨어 설치  [[목차]]

GT3.2 설치에 필요한 소프트웨어들은 다음과 같다.

– Java SDK

– Ant

– Junit

그 밖에 C 컴파일러와 Yacc 등은 리눅스에 기본적으로 설치되어 있다고 가정하겠다.

2.1. Java2 SDK 설치  [[목차]]

[root]# mkdir /usr/java ; cd /usr/java/

[root]# wget http://gridtest.gridcenter.or.kr/software/Java/J2SDK/1.4.2/j2sdk-1_4_2-linux-i586.bin

[root]# chmod 755 j2sdk-1_4_2-linux-i586.bin

[root]# ./j2sdk-1_4_2-linux-i586.bin

…

yes

…

Creating j2sdk1.4.2/lib/tools.jar

Creating j2sdk1.4.2/jre/lib/rt.jar

Creating j2sdk1.4.2/jre/lib/jsse.jar

Creating j2sdk1.4.2/jre/lib/charsets.jar

Creating j2sdk1.4.2/jre/lib/ext/localedata.jar

Creating j2sdk1.4.2/jre/lib/plugin.jar

Creating j2sdk1.4.2/jre/javaws/javaws.jar

Done.

[globus]$ vi ~/.bashrc

..

# java

export JAVA_HOME=/usr/java/j2sdk1.4.2

export PATH=/usr/java/j2sdk1.4.2/bin:$PATH

:wq

2.2. Ant 설치  [[목차]]

Jakarta Ant 홈페이지: http://jakarta.apache.org/ant/

[root]# cd /usr/local

[root]# wget http://testbed.gridcenter.or.kr/software/Apache/ant/apache-ant-1.6.1-bin.tar.gz

[root]# tar zxvf apache-ant-1.6.1-bin.tar.gz

[root]# rm -f apache-ant-1.6.1-bin.tar.gz

[root]# ln -s apache-ant-1.6.1 ant

[globus]$ vi ~/.bashrc

…

# ant

export ANT_HOME=/usr/local/ant

export PATH=$PATH:/usr/local/ant/bin

:wq

2.3. Junit 설치  [[목차]]

http://www.junit.org 에서 파일을 받는다.

[root]# wget http://unc.dl.sourceforge.net/sourceforge/junit/junit3.8.1.zip

[root]# unzip junit3.8.1.zip

[root]# cd junit3.8.1

[root]# CLASSPATH=.:./junit.jar java junit.textui.TestRunner junit.samples.AllTests

…………………………………..

…………………………………..

……………………………….

Time: 1.757

OK (119 tests)

ant/lib 디렉토리로 jar를 복사한다.

[root]# cp junit.jar /usr/local/ant/lib/

3. 글로버스 설치  [[목차]]

글로버스를 설치할 디렉토리를 만들고, 소유권을 globus로 설정한다.

[root]# mkdir /usr/local/gt3.2

[root]# chown globus.globus /usr/local/gt3.2

3.1. 인스톨러 실행  [[목차]]

홈디렉토리에 gt라는 폴더를 만들고, Redhat9 용 인스톨러 버젼을 다운 받는다.

[globus]$ cd ~ ; mkdir gt ; cd gt

[globus]$ wget http://testbed.gridcenter.or.kr/software/globus/3.2/3.2.0/installers/bin/rh9/gt3.2-all-linux-rh9-installer.tar.gz

압축을 풀고, install-gt3-bin 스크립트를 실행한다.

/usr/local/gt3.2는 GT3.2가 설치될 경로이다.

[globus]$ tar zxvf gt3.2-all-linux-rh9-installer.tar.gz

[globus]$ cd gt3.2-all-linux-rh9-installer

[globus]$ ./install-gt3-bin /usr/local/gt3.2 &> install.log

[install.log 보기]

3.2. 환경설정  [[목차]]

.bashrc에 환경변수를 추가한다.

[globus]$ vi ~/.bashrc

…

# gt3.2

export GLOBUS_LOCATION=/usr/local/gt3.2

# 클러스터에서 /home이 공유되어 있는 경우 계산 노드에서는 /usr/local/gt3.2가 없으면

# 에러가 출력되므로, 프론트 노드에서만 user-env.sh를 읽도록 한다.

if [ `hostname -s` == “node01” ] ; then

  . $GLOBUS_LOCATION/etc/globus-user-env.sh

fi

…

:wq

3.3. Setuid 퍼미션 변경  [[목차]]

UHE 실행을위해 사용되는 setuid 프로그램의 퍼미션을 변경한다.

[root]# more /usr/local/gt3.2/bin/setperms.sh

#!/bin/sh

chown root /usr/local/gt3.2/bin/launch_uhe_setuid

chmod 4750 /usr/local/gt3.2/bin/launch_uhe_setuid

chown root /usr/local/gt3.2/bin/globus-grim

chmod 4755 /usr/local/gt3.2/bin/globus-grim

chown root /usr/local/gt3.2/bin/launch_uhe.sh

chmod 755 /usr/local/gt3.2/bin/launch_uhe.sh

[root]# sh /usr/local/gt3.2/bin/setperms.sh

[launch_uhe.sh 보기] [comment]

4. 보안 설정  [[목차]]

4.1. Globus SimpleCA를 이용  [[목차]]

[root]# $GLOBUS_LOCATION/setup/globus/setup-simple-ca

    C e r t i f i c a t e    A u t h o r i t y    S e t u p

This script will setup a Certificate Authority for signing Globus

users certificates.  It will also generate a simple CA package

that can be distributed to the users of the CA.

The CA information about the certificates it distrubtes will

be kept in:

/root/.globus/simpleCA/

The unique subject name for this CA is:

cn=Globus Simple CA, ou=simpleCA-vega01.gridcenter.or.kr, ou=GlobusTest, o=Grid

Do you want to keep this as the CA subject (y/n) [y]:y

Enter the email of the CA (this is the email where certificate

requests will be sent to be signed by the CA):sangwan@kisti.re.kr

The CA certificate has an expiration date. Keep in mind that

once the CA certificate has expired, all the certificates

signed by that CA become invalid.  A CA should regenerate

the CA certificate and start re-issuing ca-setup packages

before the actual CA certificate expires.  This can be done

by re-running this setup script.  Enter the number of DAYS

the CA certificate should last before it expires.

[default: 5 years (1825 days)]: Enter

Generating a 1024 bit RSA private key

……………………………..++++++

…..++++++

writing new private key to ‘/root/.globus/simpleCA//private/cakey.pem’

Enter PEM pass phrase: 패스워드

Verifying – Enter PEM pass phrase: 한번더

…

***************************************************************************

Note: To complete setup of the GSI software you need to run the

following script as root to configure your security configuration

directory:

/usr/local/gt3.2/setup/globus_simple_ca_9864ff8c_setup/setup-gsi

For further information on using the setup-gsi script, use the -help

option.  The -default option sets this security configuration to be

the default, and -nonroot can be used on systems where root access is

not available.

***************************************************************************

setup-ssl-utils: Complete

[root]# /usr/local/gt3.2/setup/globus_simple_ca_9864ff8c_setup/setup-gsi -default

setup-gsi: Configuring GSI security

Making /etc/grid-security…

mkdir /etc/grid-security

Making trusted certs directory: /etc/grid-security/certificates/

mkdir /etc/grid-security/certificates/

Installing /etc/grid-security/certificates//grid-security.conf.9864ff8c…

Running grid-security-config…

Installing Globus CA certificate into trusted CA certificate directory…

Installing Globus CA signing policy into trusted CA certificate directory…

setup-gsi: Complete

[root]# ls /etc/grid-security/

certificates  globus-host-ssl.conf  globus-user-ssl.conf  grid-security.conf

[root]# ls /etc/grid-security/certificates/

9864ff8c.0               globus-host-ssl.conf.9864ff8c  grid-security.conf.9864ff8c

9864ff8c.signing_policy  globus-user-ssl.conf.9864ff8c

4.2. 호스트 인증서 설치  [[목차]]

[root]# cd /etc/grid-security/

[root]# ls -la

drwxr-xr-x    2 root     root         4096 Jul  8 16:43 certificates

lrwxrwxrwx    1 root     root           62 Jul  8 16:43 globus-host-ssl.conf -> /etc/grid-security/certificates//globus-host-ssl.conf.9864ff8c

lrwxrwxrwx    1 root     root           62 Jul  8 16:43 globus-user-ssl.conf -> /etc/grid-security/certificates//globus-user-ssl.conf.9864ff8c

lrwxrwxrwx    1 root     root           60 Jul  8 16:43 grid-security.conf -> /etc/grid-security/certificates//grid-security.conf.9864ff8c

[root]# ls -la host*

-rw-r–r–    1 root     root            0 Jul  8 16:44 hostcert.pem

-rw-r–r–    1 root     root         1447 Jul  8 16:44 hostcert_request.pem

-r——–    1 root     root          891 Jul  8 16:44 hostkey.pem

CA를 이용하여 hostcert_request.pem을 이용하여 hostcert.pem을 발급받는다.

(참고) SimpleCA를 이용하여 인증서 발급받기

[root]# grid-ca-sign  -in hostcert_request.pem  -out hostsigned.pem

Enter password for the CA key: 패스워드

The new signed certificate is at: /root/.globus/simpleCA//newcerts/01.pem

[root]# cp -f /root/.globus/simpleCA//newcerts/01.pem /etc/grid-security/hostcert.pem

[root]# vi hostcert.pem

Certificate:

    Data:

        Version: 3 (0x2)

        Serial Number: 1 (0x1)

        Signature Algorithm: md5WithRSAEncryption

        Issuer: O=Grid, OU=GlobusTest, OU=simpleCA-vega01.gridcenter.or.kr, CN=Globus Simple CA

        Validity

            Not Before: Jul  8 07:46:33 2004 GMT

            Not After : Jul  8 07:46:33 2005 GMT

        Subject: O=Grid, OU=GlobusTest, OU=simpleCA-vega01.gridcenter.or.kr, CN=host/vega01

…

—–BEGIN CERTIFICATE—–

MIICazCCAdSgAwIBAgIBATANBgkqhkiG9w0BAQQFADBqMQ0wCwYDVQQKEwRHcmlk

…

aYdQfO8+aej7VM50rMKT7dm12CZrD2MtajzdO62hX5eGyUeV5hDydp+BiAwlpSs=

—–END CERTIFICATE—–

BEGIN … END 부분만 남기고 삭제한다.

[root]# more hostcert.pem

—–BEGIN CERTIFICATE—–

MIICazCCAdSgAwIBAgIBATANBgkqhkiG9w0BAQQFADBqMQ0wCwYDVQQKEwRHcmlk

…

aYdQfO8+aej7VM50rMKT7dm12CZrD2MtajzdO62hX5eGyUeV5hDydp+BiAwlpSs=

—–END CERTIFICATE—–

4.3. 사용자 인증서 설치  [[목차]]

[globus]$ grid-cert-request

Enter your name, e.g., John Smith: test

A certificate request and private key is being created.

You will be asked to enter a PEM pass phrase.

This pass phrase is akin to your account password,

and is used to protect your key file.

If you forget your pass phrase, you will need to

obtain a new certificate.

Generating a 1024 bit RSA private key

……..++++++

…………….++++++

writing new private key to ‘/home/globus/.globus/userkey.pem’

Enter PEM pass phrase: 패스워드

Verifying – Enter PEM pass phrase: 한번더

[globus]$ cd ~/.globus

[globus]$ ls -al

-rw-r–r–    1 globus   globus          0 Jul  8 16:52 usercert.pem

-rw-r–r–    1 globus   globus       1449 Jul  8 16:52 usercert_request.pem

-r——–    1 globus   globus        951 Jul  8 16:52 userkey.pem

CA를 이용하여 usercert_request.pem을 이용하여 usercert.pem을 발급받는다.

(참고) SimpleCA를 이용하여 인증서 발급받기

[root]# grid-ca-sign -in /home/globus/.globus/usercert_request.pem -out signed.pem

Enter password for the CA key: 패스워드

The new signed certificate is at: /root/.globus/simpleCA//newcerts/02.pem

[root]# cp /root/.globus/simpleCA//newcerts/02.pem /home/globus/.globus/usercert.pem

BEGIN … END 부분만 남기고 삭제한다.

[globus]$ vi ~/.globus/usercert.pem

—–BEGIN CERTIFICATE—–

MIICbjCCAdegAwIBAgIBAjANBgkqhkiG9w0BAQQFADBqMQ0wCwYDVQQKEwRHcmlk

…

Qez3qpYQiKomeabYCVdINUF8nYGgCa21MBGnOAMxAI4j+m3TX+p6PBRpQapueRKi

BYs=

—–END CERTIFICATE—–

4.4. 프록시 초기화하기  [[목차]]

[globus]$ grid-proxy-init

Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA-vega01.gridcenter.or.kr/OU=gridcenter.or.kr/CN=test

Enter GRID pass phrase for this identity:

Creating proxy ………………………………… Done

Your proxy is valid until: Fri Jul  9 04:57:20 2004

4.5. Grid-mapfile에 사용자 추가  [[목차]]

/etc/grid-security/grid-mapfile 파일에 사용자의 인증서 DN과 로컬계정명을 적어준다.

[root]# more /etc/grid-security/grid-mapfile

“/O=Grid/OU=GlobusTest/OU=simpleCA-vega01.gridcenter.or.kr/OU=gridcenter.or.kr/CN=test” globus

5. 테스트  [[목차]]

5.1. 컨테이너 실행  [[목차]]

[globus]$ globus-start-container

…

http://123.123.123.123:8080/ogsa/services/core/admin/AdminService

http://123.123.123.123:8080/ogsa/services/core/management/OgsiManagementService

http://123.123.123.123:8080/ogsa/services/core/registry/ContainerRegistryService

http://123.123.123.123:8080/ogsa/services/core/jmsadapter/JMSAdapterFactoryService

http://123.123.123.123:8080/ogsa/services/core/logging/OgsiLoggingManagementService

http://123.123.123.123:8080/ogsa/services/core/notification/httpg/NotificationSubscriptionFactoryService

http://123.123.123.123:8080/ogsa/services/core/ping/PingService

http://123.123.123.123:8080/ogsa/services/samples/registry/VORegistryService

http://123.123.123.123:8080/ogsa/services/samples/counter/notification/CounterService

http://123.123.123.123:8080/ogsa/services/samples/counter/notification/JMSCounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/notification/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/encoded/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/persistent/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/basic/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/basic/CounterFactoryFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/delegation/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/routable/MasterRedirectedCounter

http://123.123.123.123:8080/ogsa/services/samples/counter/routable/LocalCounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/generate/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/deactivation/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/soap-secure/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/counter/logging/CounterFactoryService

http://123.123.123.123:8080/ogsa/services/samples/notification/SinkListenerFactoryService

http://123.123.123.123:8080/ogsa/services/samples/exception/ExceptionFactoryService

http://123.123.123.123:8080/ogsa/services/samples/weather/WeatherFactoryService

http://123.123.123.123:8080/ogsa/services/samples/google/GoogleSearchFactoryService

http://123.123.123.123:8080/ogsa/services/samples/any/AnyFactoryService

http://123.123.123.123:8080/ogsa/services/samples/servicedata/ServiceDataService

http://123.123.123.123:8080/ogsa/services/samples/array/ArraySampleFactoryService

http://123.123.123.123:8080/ogsa/services/samples/chat/ChatFactoryService

http://123.123.123.123:8080/ogsa/services/ogsi/NotificationSubscriptionFactoryService

http://123.123.123.123:8080/ogsa/services/ogsi/HandleResolverService

http://123.123.123.123:8080/ogsa/services/base/gram/ResourceInformationProviderService

http://123.123.123.123:8080/ogsa/services/base/gram/ForkManagedJobFactoryService

http://123.123.123.123:8080/ogsa/services/base/gram/MasterForkManagedJobFactoryService

http://123.123.123.123:8080/ogsa/services/base/index/IndexService

http://123.123.123.123:8080/ogsa/services/base/servicegroup/ServiceGroupFactory

http://123.123.123.123:8080/ogsa/services/base/servicegroup/ServiceGroupService

http://123.123.123.123:8080/ogsa/services/base/streaming/FileStreamFactoryFactoryService

http://123.123.123.123:8080/ogsa/services/base/multirft/MultiFileRFTFactoryService

http://123.123.123.123:8080/ogsa/services/gsi/AuthenticationService

http://123.123.123.123:8080/ogsa/services/gsi/SecureNotificationSubscriptionFactoryService

5.2. Fork 작업 예제 실행  [[목차]]

[globus]$ managed-job-globusrun \\

-factory http://123.123.123.123:8080/ogsa/services/base/gram/MasterForkManagedJobFactoryService \\

-file /usr/local/gt3.2/schema/base/gram/examples/test.xml

WAITING FOR JOB TO FINISH

========== Status Notification ==========

Job Status: Done

=========================================

DESTROYING SERVICE

SERVICE DESTROYED

실행결과는 홈디렉토리에 stdout에 첨가된다.

[globus]$ more ~/stdout

12 abc 34 pdscaex_instr_GrADS_grads23_28919.cfg pgwynnel was here

(참고1) managed-job-globusrun 스크립트는 org.globus.ogsa.impl.base.gram.client.GlobusRun 클래스를 호출한다.

[managed-job-globusrun 보기] [comment]

(참고2) GlobusRun 클래스 실행 예

$ java org.globus.ogsa.impl.base.gram.client.GlobusRun

ARGUMENTS:

         [options] [<factory>] <RSL>

         -p <RSL>

         -list [<factory>]

         (-status | -kill) <job service URL>

         -help | -usage | -version

with

     <RSL>     = -file <RSL filename> | <RSL string>

     <factory> = -factory <contact> [-type <type>]

     <contact> = [<protocol>://]<host>[:[port]][/<service>]

     [options] = [-s] [-w] [-o] [-q] [-n]

                 [-b] [-duration] [-terminate-at]

                 [-auth <auth>] [-xmlsec <sec>] [-nogrim] [-personal]

$ java org.globus.ogsa.impl.base.gram.client.GlobusRun \\

  -file /usr/local/gt3.2/schema/base/gram/examples/test.xml -p

RSL string successfully parsed.

$ java -Dorg.globus.ogsa.server.webroot=/usr/local/gt3.2/ \\

-Djava.endorsed.dirs=/usr/local/gt3.2/endorsed \\

-Dorg.globus.ogsa.server.webroot=/usr/local/gt3.2 \\

org.globus.ogsa.impl.base.gram.client.GlobusRun  \\

-factory http://123.123.123.123:8080/ogsa/services/base/gram/MasterForkManagedJobFactoryService  \\

-file /usr/local/gt3.2/schema/base/gram/examples/test.xml -batch

Warning: Will not wait for job completion, and will not destroy job service.

CREATED MANAGED JOB SERVICE WITH HANDLE: http://123.123.123.123:8080/ogsa/service

s/globus/base/gram/ForkManagedJobFactoryService/hash-22469597-1089350467849

5.3. 프로세스 모니터링  [[목차]]

글로버스 컨테이터와 사용자 UHE(User Hosting Environment)를 위한 자바 프로세스가

실행되는 것을 볼 수 있다.

[globus]$ ps -ax –width=10000 | grep java

26686 pts/0    S      0:15 java -Djava.endorsed.dirs=/usr/local/gt3.2/endorsed –

Dorg.globus.ogsa.server.webroot=/usr/local/gt3.2 -classpath /usr/local/gt3.2:/us

r/local/gt3.2/build/classes:/usr/local/gt3.2/lib/xmlsec.jar:/usr/local/gt3.2/lib

/xmlrpc-1.1.jar:/usr/local/gt3.2/lib/xmlParserAPIs.jar:/usr/local/gt3.2/lib/xmld

b-xupdate.jar:/usr/local/gt3.2/lib/xmldb-common.jar:/usr/local/gt3.2/lib/xmldb-a

pi-sdk-20021118.jar:/usr/local/gt3.2/lib/xmldb-api-20021118.jar:/usr/local/gt3.2

/lib/xml-apis-1.1.jar:/usr/local/gt3.2/lib/xindice-servicegroup-stub.jar:/usr/lo

cal/gt3.2/lib/xindice-servicegroup.jar:/usr/local/gt3.2/lib/xindice-1.1b3.jar:/u

sr/local/gt3.2/lib/xercesImpl.jar:/usr/local/gt3.2/lib/xalan.jar:/usr/local/gt3.

2/lib/wsif.jar:/usr/local/gt3.2/lib/wsdl4j.jar:/usr/local/gt3.2/lib/servlet.jar:

/usr/local/gt3.2/lib/sdb.jar:/usr/local/gt3.2/lib/saaj.jar:/usr/local/gt3.2/lib/

puretls.jar:/usr/local/gt3.2/lib/pg73jdbc2.jar:/usr/local/gt3.2/lib/openjms-0.7.

5.jar:/usr/local/gt3.2/lib/ogsa-samples.jar:/usr/local/gt3.2/lib/ogsa_messaging_

jms.jar:/usr/local/gt3.2/lib/ogsa.jar:/usr/local/gt3.2/lib/multirft.jar:/usr/loc

al/gt3.2/lib/mmjfs.jar:/usr/local/gt3.2/lib/mjs.jar:/usr/local/gt3.2/lib/mds-pro

viders.jar:/usr/local/gt3.2/lib/mds-index.jar:/usr/local/gt3.2/lib/mds-db.jar:/u

sr/local/gt3.2/lib/mds-aggregator.jar:/usr/local/gt3.2/lib/log4j-1.2.8.jar:/usr/

local/gt3.2/lib/jgss.jar:/usr/local/gt3.2/lib/jce-jdk13-120.jar:/usr/local/gt3.2

/lib/jboss-j2ee.jar:/usr/local/gt3.2/lib/jaxrpc.jar:/usr/local/gt3.2/lib/grim.ja

r:/usr/local/gt3.2/lib/gram-rips.jar:/usr/local/gt3.2/lib/filestreaming.jar:/usr

/local/gt3.2/lib/exolabcore-0.3.5.jar:/usr/local/gt3.2/lib/cryptix.jar:/usr/loca

l/gt3.2/lib/cryptix-asn1.jar:/usr/local/gt3.2/lib/cryptix32.jar:/usr/local/gt3.2

/lib/commons-pool.jar:/usr/local/gt3.2/lib/commons-logging.jar:/usr/local/gt3.2/

lib/commons-discovery.jar:/usr/local/gt3.2/lib/commons-dbcp.jar:/usr/local/gt3.2

/lib/commons-collections.jar:/usr/local/gt3.2/lib/cog-tomcat.jar:/usr/local/gt3.

2/lib/cog-jglobus.jar:/usr/local/gt3.2/lib/cog-axis.jar:/usr/local/gt3.2/lib/axi

s.jar org.globus.ogsa.server.ServiceContainer

27021 ?        S      0:16 /usr/java/j2sdk1.4.2_04/jre/bin/java -Djava.endorsed.

dirs=/usr/local/gt3.2/endorsed -DX509_USER_PROXY=/tmp/x509up_u500_grim -Dorg.glo

bus.ogsa.server.webroot=/usr/local/gt3.2/ org.globus.ogsa.impl.base.gram.uhe.Use

rContainer /usr/local/gt3.2 globus /O=Grid/OU=GlobusTest/OU=simpleCA-vega01.grid

center.or.kr/CN=host/vega01.gridcenter.or.kr/CN=500 123.123.123.123 8080 -lazy -p

37819

자바 프로세스를 간략하게 모니터링 하면 다음과 같이 하면 된다.

[root]# watch -n 1 “pstree -p -u | grep java”

        |-java(28953,globus)

        |-sshd(3844)-+-sshd(25981)—sshd(25985,globus)—bash(25986)—java(28921)

위쪽에 있는 것이 사용자 UHE이고,  아래쪽에 있는 것이 글로버스 컨테이너이다.

5.4. 컨테이너 종료하기  [[목차]]

컨테이너와 UHE를 종료시키려면 다음과 같이 한다.

[root]# killall java

5.5. 로그 메시지 보기  [[목차]]

로그 메시지를 보려면, 글로버스 설치경로의 log4j.properties 파일에서 로그 레벨을

조정한다. 로그 레벨은 DEBUG, WARN, ERROR, FATAL 등이 있고, 레벨이 낮을 수록

더 많은 로그 메시지를 볼 수 있다.

$ vi $GLOBUS_LOCATION/log4j.properties

…

line 2:

#log4j.rootCategory=WARN, CONSOLE

log4j.rootCategory=DEBUG, CONSOLE

…

컨테이너를 재시작 시킨다.

[root]# killall java

[globus]$ globus-start-container

컨테이너에서 출력하는 로그메시지는 화면에 출력된다.

UHE에서 출력되는 메지지는 ~/.globus/uhe-호스트명/log 파일에 남겨진다.

$ cd ~/.globus/uhe-`hostname`

$ tail -f log

참고문서  [[목차]]

– http://www-unix.globus.org/toolkit/docs/3.2/index.html

— GT3.2 설치  [[목차]]