Nitin,

If your goal is to submit the job to a condor-pool:

you'll either have to add Condor as parameter to globusrun-ws like

   globusrun-ws -submit -Ft Condor -f cond.xml

or add it to the job description in the factory element of your
job description like

   <factoryEndpoint
      xmlns:gram="http://www.globus.org/namespaces/2004/10/gram/job";
      xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";>
      <wsa:Address>
         https://<host>:<port>/wsrf/services/ManagedJobFactoryService
      </wsa:Address>
      <wsa:ReferenceProperties>
         <gram:ResourceID>Condor</gram:ResourceID>
      </wsa:ReferenceProperties>
   </factoryEndpoint>

If you set jobType to "condor" in your job description the Condor
universe element will be set to "standard".
But this does only make sense if you submit a job to Condor. In your
case you submit to Fork (default). A jobType set to "condor" does only
make sense in a job that is submitted to Condor.
That's the reason for the failure.

You can remove the jobType element unless you need the "standard"
universe and specify the target local resource manager as mentioned
above. By removing the jobType element the universe will be
set to "vanilla" (our default) in the generated Condor job description.

Martin

> hi all,
> i have installed the gt4.0.5 with condor-ws support enabled. but still i
> am
> facing a problem whilie submitting job to condor through globus. condor is
> running on this host
>
> [EMAIL PROTECTED] ~]$ globusrun-ws -submit -f cond.xml
> Submitting job...Done.
> Job ID: uuid:851af684-8707-11dc-b56c-0016d4015b66
> Termination time: 10/31/2007 16:45 GMT
> Current job state: Failed
> Destroying job...Done.
> globusrun-ws: Job failed: The jobType condor feature is not available on
> this resource.
> [EMAIL PROTECTED] ~]$
>
> this host is condor submit and execute node
>
> [EMAIL PROTECTED] ~]$ ps -aux | grep condor
> Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7
> /FAQ
> globus    7666  0.0  0.1   4728  1656 ?        S    20:50   0:00
> /usr/local/globus-4.0.5/libexec/globus-scheduler-event-generator -s condor
> -t 1193757617
> root      8528  0.0  0.1   4808  1132 pts/2    S    21:58   0:00 su -
> condor
> condor    8529  0.0  0.1   4640  1444 pts/2    S+   21:58   0:00 -bash
> condor    8578  0.0  0.2   7152  2684 ?        Ss   21:59   0:00
> /usr/local/condor/sbin/condor_master
> condor    8579  0.3  0.3   7916  3500 ?        Ss   21:59   0:04
> condor_startd -f
> condor    8580  0.0  0.3   8312  3504 ?        Ss   21:59   0:00
> condor_schedd -f
> psegrid   8815  0.0  0.0   3900   688 pts/3    S+   22:18   0:00 grep
> condor
> [EMAIL PROTECTED] ~]$
>
> the cond.xml is
> <?xml version="1.0" encoding="UTF-8"?>
> <job>
>     <executable>/home/condor/condor-6.8.6/examples/sh_loop</executable>
>     <directory>${GLOBUS_USER_HOME}</directory>
>     <argument>123</argument>
>     <stdin>/dev/null</stdin>
>     <stdout>${GLOBUS_USER_HOME}/stdout</stdout>
>     <stderr>${GLOBUS_USER_HOME}/stderr</stderr>
>     <jobType>condor</jobType>
> </job>
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Nitin M. Gavhane
> MS in Adavanced Software Technologies
> International Institute of Information Technology
> P-14,Hinjewadi,Pune, India.
> ---------------------------------------------------------------------------------------------------------------------------
>


Reply via email to