Bug 3002 – sudo path isn't set correctly in libexec/globus-sh-tools-vars.sh

Bug 3002 - sudo path isn't set correctly in libexec/globus-sh-tools-vars.sh

Summary:

sudo path isn't set correctly in libexec/globus-sh-tools-vars.sh

Status:	RESOLVED FIXED

Product:	GRAM
Component:	wsrf managed execution job service
Version:	3.9.5
Platform:	PC Linux

Importance:	P3 normal
Target Milestone:	4.0.2
Assigned To:	Peter Lane

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-24 07:44 by Mathias Dalheimer
Modified:	2005-10-05 17:12 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Mathias Dalheimer 2005-03-24 07:44:58

I went through the installation, but I wasn'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.<init>(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 = ""

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

At the time I compiled GT, I didn't had sudo installed, so I think the build
scripts weren'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

------- Comment #1 From Charles Bacon 2005-05-31 11:26:17 -------

Sudo was added to the documented requirements during the 3.9.x series.

Reassigning to GRAM for a better error message.

------- Comment #2 From Peter Lane 2005-05-31 11:53:40 -------

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'll add a check in the config setup to make sure GLOBUS_SH_SUDO is 
set.

------- Comment #3 From Peter Lane 2005-10-05 17:10:15 -------

Fix in trunk. Branch fix comming soon.

------- Comment #4 From Peter Lane 2005-10-05 17:12:56 -------

Fix in globus_4_0_branch now as well.