<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugzilla.globus.org/bugzilla/bugzilla.dtd">

<bugzilla version="3.2.3"
          urlbase="http://bugzilla.globus.org/bugzilla/"
          maintainer="bacon@mcs.anl.gov"
>

    <bug>
          <bug_id>3002</bug_id>
          
          <creation_ts>2005-03-24 07:44</creation_ts>
          <short_desc>sudo path isn&apos;t set correctly in libexec/globus-sh-tools-vars.sh</short_desc>
          <delta_ts>2005-10-05 17:12:56</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>GRAM</product>
          <component>wsrf managed execution job service</component>
          <version>3.9.5</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          
          <priority>P3</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>4.0.2</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Mathias Dalheimer">dalheimer@itwm.fhg.de</reporter>
          <assigned_to name="Peter Lane">lane@mcs.anl.gov</assigned_to>
          <cc>gose@mcs.anl.gov</cc>
    
    <cc>rynge@isi.edu</cc>

      

      
          <long_desc isprivate="0">
            <who name="Mathias Dalheimer">dalheimer@itwm.fhg.de</who>
            <bug_when>2005-03-24 07:44:58</bug_when>
            <thetext>I went through the installation, but I wasn&apos;t abele to submit any job using
WS-GRAM. Setting the container to debug log level, the container.log revealed this:

---
2005-03-24 15:37:33,796 DEBUG exec.JobManagerScript [Thread-25,run:177]
Executing command:
 -H -u dalheime -S /usr/local/globus-3.9.5/libexec/globus-gridmap-and-execute
/usr/local/globus-3.9.5/libexec/globus-job-manager-script.pl -m fork -f
/tmp/gram_job_mgr27879.tmp -c cache_cleanup
2005-03-24 15:37:33,796 WARN  exec.JobManagerScript [Thread-24,run:258] 
java.io.IOException: java.io.IOException: : not found
        at java.lang.UNIXProcess.&lt;init&gt;(UNIXProcess.java:148)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
        at java.lang.Runtime.exec(Runtime.java:591)
        at java.lang.Runtime.exec(Runtime.java:507)
        at
org.globus.exec.service.exec.JobManagerScript.run(JobManagerScript.java:184)
---

globusrun-ws says:
---
Submitting job...Done.
Job ID: uuid:41a80068-9c72-11d9-868b-000e0c4eae28
Termination time: 03/25/2005 14:37 GMT
Current job state: Failed
Destroying job...Done.
globusrun-ws: Job failed: Internal fault occurred while running the submit script.
---

As some debugging and source-reading revealed: The path of sudo is not set in
libexec/globus-sh-tools-vars.sh:
GLOBUS_SH_SUDO = &quot;&quot;

Setting this variable to the correct path of the binary solves the problem.

At the time I compiled GT, I didn&apos;t had sudo installed, so I think the build
scripts weren&apos;t able to figure this out. Please provide a better error message
in the container log, and suggest to install sudo as a software prerequisite at
the very beginning of the admin manual.

thanks,
mathias</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Charles Bacon">bacon@mcs.anl.gov</who>
            <bug_when>2005-05-31 11:26:17</bug_when>
            <thetext>Sudo was added to the documented requirements during the 3.9.x series.

Reassigning to GRAM for a better error message.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Peter Lane">lane@mcs.anl.gov</who>
            <bug_when>2005-05-31 11:53:40</bug_when>
            <thetext>The GRAM admin documenation clearly states sudo as a prerequisite:

http://www-unix.globus.org/toolkit/docs/4.0/execution/wsgram/admin-index.html#s-wsgram-
admin-installing-req

That said, when I get a chance I&apos;ll add a check in the config setup to make sure GLOBUS_SH_SUDO is 
set.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Peter Lane">lane@mcs.anl.gov</who>
            <bug_when>2005-10-05 17:10:15</bug_when>
            <thetext>Fix in trunk. Branch fix comming soon.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Peter Lane">lane@mcs.anl.gov</who>
            <bug_when>2005-10-05 17:12:56</bug_when>
            <thetext>Fix in globus_4_0_branch now as well.</thetext>
          </long_desc>
      
      

    </bug>

</bugzilla>