Bugzilla – Bug 3002
sudo path isn't set correctly in libexec/globus-sh-tools-vars.sh
Last modified: 2005-10-05 17:12:56
You need to
before you can comment on or make changes to this bug.
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]
-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
Job ID: uuid:41a80068-9c72-11d9-868b-000e0c4eae28
Termination time: 03/25/2005 14:37 GMT
Current job state: Failed
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
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.
Sudo was added to the documented requirements during the 3.9.x series.
Reassigning to GRAM for a better error message.
The GRAM admin documenation clearly states sudo as a prerequisite:
That said, when I get a chance I'll add a check in the config setup to make sure GLOBUS_SH_SUDO is
Fix in trunk. Branch fix comming soon.
Fix in globus_4_0_branch now as well.