Hello! If I were to guess: symlinks. I had some Problems with them and sudo, since my GLOBUS_LOCATION is /opt/globus, which is a symlink to /opt/globus-4.0.[35]
Globus uses some hard coded links internally I guess, so if you've got the symlinked path in sudoers and globus uses the absolute and direct path, it does not work. Maybe the only way to make globus really work with a symlink & versions filesystem structure is to install it in /opt/globus and later move that directory to /opt/globus-4.0.5 and create the symlink afterwards. Haven't tried that though. I also ended upt using [...] /opt/globus-4.0.5/libexec/globus-gridmap-and-execute * inntead of the version you use, with "-g <grid-mapfile> [...]" because that did not work for me. Not so secure, but my installation is mainly for testing and evaluation purposes - not for production use. Regards, Christian Aßfalg -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Samatha Kottha Gesendet: Freitag, 28. September 2007 12:44 An: [email protected] Betreff: [gt-user] Sudo is misconfigured to run the globus-job-manager-script.pl script 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?? 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
