Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users] jobs wait in idle mode unecessarily
- Date: Tue, 22 Jun 2004 14:20:32 -0400
- From: "Bryan S. Maher" <Bryan.Maher@xxxxxxxxxx>
- Subject: RE: [Condor-users] jobs wait in idle mode unecessarily
Ian,
are you submitting jobs from a Win2K box to a Win2K box? By default, Condor will try to find a machine running the exact same OS at the submitter. Most of my group is running XP on their desktop and we saw this same behavior until we added a requirements statement something like
requirements = (OpSys != BOGUS)
Hope this helps.
-Bryan
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Dr Ian C. Smith
> Sent: Tuesday, June 22, 2004 11:20 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] jobs wait in idle mode unecessarily
>
>
> Thanks for that - unfortunately it's a Windows 2K OS. I tried changing
> FILESYSTEM_DOMAIN and UID_DOMAIN to $(FULL_HOSTNAME) but it doesn't
> seem to have made any difference.
>
> -ian.
>
> --On 22 June 2004 09:06 -0500 Michael Remijan
> <remijan@xxxxxxxxxxxxx> wrote:
>
> >
> > I think this is a very common newbie question but I've
> found very few
> > answers addressing it. I can tell you about my own experiences.
> >
> > First, by default if you're using non-windows operating
> system the condor
> > installation assumes that all the computers in the pool share both a
> > common file system and a common way to allow login to
> machines. If your
> > machines are not like this, I found it impossible to run
> jobs. To "fix"
> > the problem, look for FILESYSTEM_DOMAIN and UID_DOMAIN in both the
> > condor.config file *and* the condor.config.local file.
> Make sure the
> > value is $(FULL_HOSTNAME). Doing this tells condor that
> the computers do
> > not share a file system or login accounts.
> >
> > At 05:07 AM 6/21/2004, you wrote:
> >> Hi,
> >>
> >> When I submit a Condor job it seems to wait in the idle
> >> state and take ages to start despite a host being free
> >> for it to run on. Using condor_q -analyze I get
> >>
> >> 174.000: Run analysis summary. Of 2 machines,
> >> 1 are rejected by your job's requirements
> >> 0 reject your job because of their own requirements
> >> 0 match, but are serving users with a better priority
> in the pool
> >> 1 match, but prefer another specific job despite its worse
> >> user-priority 0 match, but will not currently preempt their
> >> existing job 0 are available to run your job
> >> Last successful match: Mon Jun 21 10:54:27 2004
> >>
> >> What does the "1 match, but prefer another specific job
> >> despite its worse user-priority" mean ? Is there anyway
> around this ?
> >>
> >> thanks in advance,
> >>
> >> -ian.
> >>
> >> -----------------------------------
> >> Dr Ian C. Smith,
> >> e-Science team,
> >> University of Liverpool
> >> Computing Services Department
> >>
> >> _______________________________________________
> >> Condor-users mailing list
> >> Condor-users@xxxxxxxxxxx
> >> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> >
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > http://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
>