Both entries need to be on a single line. From the formatting of your mail, it looks like the first entry might be split across two lines. I recommend you use the visudo program to edit sudoers, as it can help find syntax errors. If you don't want to use vi to edit, you can set the EDITOR environment variable to your preferred editor.

If you edit $GLOBUS_LOCATION/container-log4j.properties file to uncomment the GRAM debugging line, you will see the entry in the $GLOBUS_LOCATION/var/container.log of the sudo command attempted. You can then try that command by hand to see exactly what goes wrong.


Charles

On Jan 28, 2008, at 5:32 AM, meriam jemel wrote:

Hi, I try to run this command
globusrun -ws -submit -c /bin/true but i have this error:

Submitting job...Done.
Job ID: uuid:5d85bb28-c67c-11db-ac3b-00163e010001
Termination time: 01/28/2008 16:05 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 meriam.this is /etc/sudoes file: globus ALL=(meriam) NOPASSWD: /opt/globus/GT4.0.5/libexec/globus- gridmap-and-execute -g /etc/grid-security/grid-mapfile
/opt/globus/GT4.0.5/libexec/globus-job-manager-script.pl *

globus ALL=(meriam) NOPASSWD: /opt/globus/GT4.0.5/libexec/globus- gridmap-and-execute -g /etc/grid-security/grid-mapfile /opt/globus/ GT4.0.5/libexec/globus-gram-local-proxy-tool * Plesae help me
Many thanks

Reply via email to