Globus Toolkit Tutorial The Globus Consortium
 
 

Chapter 8: Connecting Globus Gram WS and SUN Grid Engine

Turning on reporting for SGE

Before building the WS GRAM SGE job manager you need to modify the SGE installation to turn on reporting. This is easily done using the 'qconf' command.

As user root on nodeC run:

[root@nodeC sge-root]# /opt/sge-root/bin/lx24-x86/qconf -mconf

This invokes the default system editor. Find the 'reporting_params' configuration option in the file and edit it so that it appears as shown below:

shepherd_cmd none
qmaster_params none
execd_params none
reporting_params accounting=true reporting=true \
  flush_time=00:00:15 joblog=true sharelog=00:00:00
finished_jobs 100
gid_range 20000-20500
qlogin_command telnet
qlogin_daemon /usr/sbin/in.telnetd

Quit the editor and run a simple job as user root in order to test and make sure that the reporting is working:

[root@nodeC ~]# /opt/sge-root/bin/lx24-x86/qsub /opt/sge-root/examples/jobs/simple.sh

Watch for it to finish using /opt/sge-root/bin/lx24-x86/qstat, and look in /root/ for the job output:

[root@nodeC ~]# cat simple.sh.o3

Note that simple.sh.o3 is an example filename, you may want to do an ls -la command to find a recently created simple.sh.o* file, this will be the file you should look to for the job output.

Fri Feb 24 10:43:30 CST 2006
Fri Feb 24 10:43:50 CST 2006

Now check for the 'reporting' file:

[root@nodeC ~]# ls -l /opt/sge-root/default/common/reporting
-rw-r--r-- 1 root root 1516 Feb 24 10:44 /opt/sge-root/default/common/reporting

This file is necessary, since it is used by GRAM to monitor the status of a job.

 
 
 
FAQ Feedback The Globus Consortium Home Page