Nitin, My understanding is that the below condor logfile statements show that the job had been fully and successfully processed. >From what you describe Gram behaves correctly. I don't know why the job does not produce output. If it really should produce output then this is more a question for the e-mail lists of Condor. Good luck! Martin
> yes martin, > i followed the job description generated by GRAM, it is as follows > > ===================================================== > [EMAIL PROTECTED] NIP]$ cat /tmp/condor_job_description > # > # description file for condor submission > # > Universe = vanilla > Notification = Never > Executable = /home/psegrid/NIP/nip > Requirements = OpSys == "LINUX" && Arch == "INTEL" > Environment = GLOBUS_LOCATION=/usr/local/globus-4.0.5 > /;X509_CERT_DIR=/etc/grid-security/certificates;X509_USER_PROXY=;X509_USER_CERT=;X509_USER_KEY=;HOME=/home/psegrid;LOGNAME=psegrid;SCRATCH_DIRECTORY=/home/psegrid/.globus/scratch;JAVA_HOME=/usr/java/jdk1.6.0_03/jre;GLOBUS_GRAM_JOB_HANDLE= > https://192.168.7.221:8443/wsrf/services/ManagedExecutableJobService?8fd6ab20-8894-11dc-8ae6-cf6ad78997b4;LD_LIBRARY_PATH= > Arguments = > InitialDir = /home/psegrid > Input = /dev/null > Log = /usr/local/globus-4.0.5//var/globus-condor.log > log_xml = True > #Extra attributes specified by client > > Output = /home/psegrid/stdout > Error = /home/psegrid/stderr > queue 1 > ================================================= > > bydeafult it is setting universe as vanilla, because in globus job > description file i have not mentioned jobtype as condor, but when i add > the > jobtype to the globus job description file, the jobs are getting executed > but no output. the executeble is compiled with condor_compile. > even if i tsubmit the same job using condor_submit the jobs is getting > executed but no ouput. the log file and the condor submit file are as > below. > ======================================= > [EMAIL PROTECTED] NIP]$ cat nip.submit > executable =nip > universe = standard > Requirements = OpSys == "LINUX" && Arch == "INTEL" > output = nip.$(Process) > log = nip.log > > Queue > =========================== > [EMAIL PROTECTED] NIP]$ cat nip.log > 000 (074.000.000) 11/01 21:44:46 Job submitted from host: < > 192.168.7.221:49551> > ... > 009 (074.000.000) 11/01 21:46:07 Job was aborted by the user. > via condor_rm (by user psegrid) > ... > 000 (075.000.000) 11/01 21:46:32 Job submitted from host: < > 192.168.7.221:49551> > ... > 001 (075.000.000) 11/01 21:47:01 Job executing on host: > <192.168.7.221:59017 >> > ... > 005 (075.000.000) 11/01 21:47:01 Job terminated. > (1) Normal termination (return value 4) > Usr 0 00:00:00, Sys 0 00:00:00 - Run Remote Usage > Usr 0 00:00:00, Sys 0 00:00:00 - Run Local Usage > Usr 0 00:00:00, Sys 0 00:00:00 - Total Remote Usage > Usr 0 00:00:00, Sys 0 00:00:00 - Total Local Usage > 265 - Run Bytes Sent By Job > 13926992 - Run Bytes Received By Job > 265 - Total Bytes Sent By Job > 13926992 - Total Bytes Received By Job > ... > > ================================================================== > > what does the Normal Termination (return value 4) means in log file? > > thank you > Nitin > > On 10/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >> 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. >> > >> --------------------------------------------------------------------------------------------------------------------------- >> > >> >> >> > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Nitin M. Gavhane > MS in Adavanced Software Technologies > International Institute of Information Technology > P-14,Hinjewadi,Pune, India. > --------------------------------------------------------------------------------------------------------------------------- >
