Nitin,

you can check the job description that gets generated by Gram4
as described in
http://www.globus.org/mail_archive/gt-user/2007/10/msg00169.html
Check if anything does not fit the needs of your pool there
and/or submit these generated condor job descriptions manually
using condor_submit and have a look at the condor logfiles for
more information why these jobs get rejected.
If you need to change certain parameters of the condor job description
you can have a look at
$GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/condor.pm
It's here where the parameters of a Gram4 job description get
transformed into a condor job description

Martin

> hi all,
> i have submitted job to condor through globus but the job remains in idle
> state for long time. i followed few threads for the same problem but they
> are not useful.
> (http://www-unix.globus.org/mail_archive/gt4-friends/2005/09/msg00011.html
> http://www.globus.org/mail_archive/discuss/2005/09/msg00591.html)
>
> the problem is job requirement as shown below in the condor_q output
>
> Please Tell me how to specify the job requirements in job specification
> file
> (RSL).
>
>
> the results are
> [EMAIL PROTECTED] ~]$ condor_q -analyze 57
> -- Submitter: niting-w2p.corp.cdac.in : <192.168.7.221:40017> :
> niting-w2p.corp.cdac.in
>  ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE
> CMD
> ---
> 057.000:  Run analysis summary.  Of 7 machines,
>       5 are rejected by your job's requirements
>       1 reject your job because of their own requirements
>       0 match but are serving users with a better priority in the pool
>       1 match but reject the job for unknown reasons
>       0 match but will not currently preempt their existing job
>       0 are available to run your job
>         Last successful match: Wed Oct 31 23:03:39 2007
>
>
> Thank You
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Nitin M. Gavhane
> MS in Adavanced Software Technologies
> International Institute of Information Technology
> P-14,Hinjewadi,Pune, India.
> ---------------------------------------------------------------------------------------------------------------------------
>


Reply via email to