Hi Diego...,
I guess you r asking me to submit jobs using globusrun-ws ...
lets show u example.. on my node...
$ globusrun-ws -submit -c /bin/true
Submitting job...Done.
Job ID: uuid:d7a01708-2f7f-11db-b64f-000ae432324e
Termination time: 08/20/2006 12:40 GMT
Current job state: Active
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
i think its working quite well... :-)
and its working quite well when i submit to other machine as well...
can u help me now..!!!...
Pranav
On 8/17/06, Diego Bello
<dbello@xxxxxxxxx> wrote:
On 8/17/06, Pranav Aggarwal <pranav.aggwl@xxxxxxxxx> wrote:
> Hi Diego...,
>
> Well thanks for your review...
> I have worked a week with condor... and submitted the jobs from condor
> submission machine to condor host.. and host was able to delegate the jobs
> to the condor pool and the result is posted back to submission machine...
> this was kinda C jobs..
>
> well now moving step ahead... now throwing jobs to GT 4...using Condor...
> this is my submission file... lot is done to improve it...
>
> $ cat env3test
> executable = /bin/ls
>
> universe = grid
> grid-type = gt4
> #globusscheduler = i2it:8443
> JobManager_type = Fork
> #universe = globus
> grid_resource = gt4
>
https://192.168.7.131:8443/wsrf/service/ManagedJobFactoryService
> Fork
> output = test_env3.out
> log = test_env3.log
> error = test_env3.err
> notification = error
> #requirements = (OpSys == "LINUX")
> queue 1
>
> considering ur mail and reading text .. got that Fork is default
> scheduler...
> now when i submit this ...
> $ condor_q -ana
> -- Submitter:xxxxxxxxxxxxxx : <
192.168.7.131:32849> : xxxxxxxxxxxxxxxxxx
>
> ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
> 78.0 pranavg 8/17 15:38 0+00:00:00 H 0 9.8 ls
> 79.0 pranavg 8/17 15:38 0+00:10:59 R 0 9.8
> gridftp_wrapper.sh
>
> 2 jobs; 0 idle, 1 running, 1 held
>
> this 79.0 was greated after 2 minutes of submission of 'env3test'
> well i dont know why.. explain me if u get the answer...
>
> now the problem... well looking at the log file it says so...
>
> 000 (078.000.000) 08/17 15:38:10 Job submitted from host: <
> 192.168.7.131:32849>
> ...
> 018 (078.000.000) 08/17 15:38:24 Globus job submission failed!
> Reason: 0 The AXIS engine could not find a target service to invoke!
> targetService is null
> ...
> 012 (078.000.000 ) 08/17 15:38:28 Job was held.
> Globus error: The AXIS engine could not find a target service to
> invoke! targetService is null
> Code 0 Subcode 0
> ...
>
> could you tell what is the probable problem with this... and the solution as
> well :-)
>
> Thanx...
> Pranav.......
>
Try to submit the jobs directly to globus, i.e., using globusrun-ws.
If there is any problem, that, and the globus logs, should tell you
what's not working.
Regards.
--
Diego Bello Carreño
Estudiante Memorista de Ingeniería Civil Informática
UTFSM, Valparaíso, Chile
Usuario #294897
counter.li.org
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR