As you've discovered, a limited proxy can't be used to submit jobs. By default, globusrun delegates a limited proxy to jobs, so a job can't itself submit another job.
In GT 4.1.1 and later, globusrun has a new -full-proxy option to delegate a "full" proxy instead of a "limited" proxy to jobs. Also, for GRAM4, globus-credential-delegate can be combined with globusrun-ws to submit jobs with full proxies. For example: globus-credential-delegate -h hostname epr.txt globusrun-ws -Jf epr.txt -J -submit -F hostname -s -c globus-job-run localhost /bin/ls Ole Christian Weidner <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to execute the following command(s): > > # grid-proxy-init > # globus-job-run localhost globus-job-run localhost /bin/ls > > and get the following error: > > GRAM Job submission failed because authentication with the remote > server failed (error code 7) > > The gatekeeper log-file says: > > TIME: Wed Jun 20 15:52:53 2007 > PID: 22660 -- Notice: 5: Authenticated globus user: /O=Louisiana > State University/OU=CCT/OU=ca.cct.lsu.edu/OU=cct.lsu.edu/CN=Ole > Christian Weidner > TIME: Wed Jun 20 15:52:53 2007 > PID: 22660 -- Notice: 0: GRID_SECURITY_HTTP_BODY_FD=7 > TIME: Wed Jun 20 15:52:53 2007 > PID: 22660 -- Notice: 5: Requested service: jobmanager > Failure: Attempt to use limited proxy for service > TIME: Wed Jun 20 15:52:53 2007 > PID: 22660 -- Failure: Attempt to use limited proxy for service > > A simple "globus-job-run localhost /bin/ls" works fine. What exactly > is a "limited proxy" and how do I have to set up my environment to > avoid this error? > > Thanks for your help! > > Ole
