Re: [Condor-users] job goes held

[Ariff <ariff_sattar@xxxxxxxxx>]

1) yes, it's a personal gatekeeper, however i don't
find this error while submitting job with
globus-job-run.

[arif@Cern1-8 scratch]$ globus-job-run
Cern1-8:40611:/O=Grid/OU=GlobusTest/OU=simpleCA-localhost.localdomain/OU=localdomain/CN=arifsattar
/bin/date
Wed Oct 12 14:28:30 PKST 2005
[arif@Cern1-8 scratch]$

and this is the entry of globus scheduler from submit
file ; it's the same

globusscheduler=Cern1-8:40611:/O=Grid/OU=GlobusTest/OU=simpleCA-localhost.localdomain/OU=localdomain/CN=arifsattar:/jobmanager-fork


2) ofcourse, i amn't interested in matchmaking or
glide-in at this point ; i think that i checked (or
perhaps might added) that entry in config file after i
gone through a similar type of poblem description on
condor-users mailing archives.

thanks for guidance ; still need fix

regards

Ariff


--- Jaime Frey <jfrey@xxxxxxxxxxx> wrote:

> On Oct 12, 2005, at 3:30 PM, Ariff wrote:
> 
> > i am extremely new to condor usage. whenever i
> submit
> > my job through condor_submit, job first goes to
> idle
> > status, and then goes held. i am finding it
> difficult
> > to figure out where the problem really lies.
> ...
> > -- This is the log details for the last job
> >
> >
> > 000 (044.000.000) 10/12 12:53:30 Job submitted
> from
> > host: <10.10.21.8:32798>
> > ...
> > 018 (044.000.000) 10/12 12:53:33 Globus job
> submission
> > failed!
> >     Reason: 7 authentication failed: GSS Major
> Status:
> > Unexpected Gatekeeper or Service Name GSS Minor
> Status
> > Error Chain:  init.c:499:
> > globus_gss_assist_init_sec_context_async: Error
> during
> > context initialization
> 
> The Globus gatekeeper is using a certificate whose
> subject is  
> different than the expected one. You should see this
> same error if  
> you try submitting a job with globusrun or
> globus-job-run. What value  
> are you using for globus_scheduler in your submit
> file? What  
> credential is the gatekeeper using? Is it a personal
> gatekeeper?
> 
> > one more thing, whenever i issue condor_status
> > command,
> > it results in the following output
> >
> > [arif@Cern1-8 scratch]$ condor_status
> > Error:  Could not fetch ads --- can't find
> collector
> >
> > while this daemon is specified in the config file.
> 
> Is the collector listed in DAEMON_LIST in  your
> Condor config file?  
> Is there a condor_collector process running on your
> machine?
> 
> Unless you wan to use match-making or glide-in for
> your Condor-G  
> jobs, condor_status is useless and you really don't
> need a collector  
> running.
> 
>
+----------------------------------+---------------------------------+
> |            Jaime Frey            |  Public Split
> on Whether        |
> |        jfrey@xxxxxxxxxxx         |  Bush Is a
> Divider              |
> |  http://www.cs.wisc.edu/~jfrey/  |         -- CNN
> Scrolling Banner |
>
+----------------------------------+---------------------------------+
> 
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
>
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 


 





		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/