On Fri, 28 Sep 2007 08:21:03 -0500 Tim Freeman <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Sep 2007 12:43:46 +0200 > Samatha Kottha <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I am having a mysterious problem. I am updating globus to 4.0.5 on > > romeo (IA-64). The code was compiled and installed successfully. GridFTP, > > RFT, and GSISSH are working properly. But when I submit a job I am getting > > this error. > > > > [EMAIL PROTECTED]:~> globusrun-ws -submit -F > > https://romeo.urz.tu-dresden.de:8443/wsrf/services/ManagedJobFactoryService > > -c /bin/date > > Submitting job...Done. > > Job ID: uuid:ee9ce780-6d9d-11dc-a9df-080069149999 > > Termination time: 09/29/2007 08:36 GMT > > Current job state: Failed > > Destroying job...Done. > > globusrun-ws: Job failed: Error code: 200 > > Sudo is misconfigured to run the globus-job-manager-script.pl script for > > user zimd0022. > > > > [EMAIL PROTECTED]:~>echo $GLOBUS_LOCATION > > /opt/globus > > [EMAIL PROTECTED]:~> > > > > I see no problem with entries in sudoers. I sent the same job to othello > > (X86-64) and it worked successfully. So, I copied the /etc/sudeors from > > othello to romeo but I am still getting the same error. Can you tell me why > > this is happening? I am attaching the container log in DEBUG mode as well. I > > just took the sudo command from the log file and tried to execute it > > directly and I am getting this message. It is asking me for password!!! > > > > [EMAIL PROTECTED]:~> /usr/bin/sudo -H -u zimd0022 -S > > /opt/globus-4.0.5/libexec/globus-gridmap-and-execute -g > > /etc/grid-security/grid-mapfile > > /opt/globus-4.0.5/libexec/globus-job-manager-script.pl -m fork -f > > /opt/globus-4.0.5/tmp/gram_job_mgr6978.tmp -c submit > > > > We trust you have received the usual lecture from the local System > > Administrator. It usually boils down to these two things: > > > > #1) Respect the privacy of others. > > #2) Think before you type. > > > > Password: > > Sorry, try again. > > Password: > > Sorry, try again. > > Password: > > /usr/bin/sudo: 2 incorrect password attempts > > [EMAIL PROTECTED]:~> > > > > So, what is wrong with the /etc/sudeors file?? > > There may be nothing wrong with the sudoers policy itself, you usually need to > 'initialize' sudo for the account even if there is a NOPASSWD flag (you get > the 'usual lecture' message just once). Type the password correctly and then > try the command again, it should go through then. Oh, indeed the paths are different like others are saying: /opt/globus/ is in sudo policy but /opt/globus-4.0.5 is being used in the sudo commands generated by GRAM. You might get away with restarting the container with GLOBUS_LOCATION set to /opt/globus in this case. Tim > > Tim > > > > > > thank you, > > Samatha > > > > > > -- > > Samatha Kottha > > Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH) > > Technische Universität Dresden Tel: (+49) 351 > > 463-38776 Room 1019 Fax: (+49) 351 > > 463-38245 Noethnitzer Straße 46 > > 01187 Dresden > > Germany > > > > > > > ----------------------------------------- > Tim Freeman - [EMAIL PROTECTED] > http://www-unix.mcs.anl.gov/~tfreeman/ > Grid Search: http://www.gridindex.org > ----------------------------------------- Tim Freeman - [EMAIL PROTECTED] http://www-unix.mcs.anl.gov/~tfreeman/ Grid Search: http://www.gridindex.org
