[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Condor-users] Re: My jobs in idle state - not running



Just to add to that (if this helps), my SchedLog file contains the
following

3/1 12:34:44 Using config file: C:\Condor\condor_config
3/1 12:34:44 Using local config files: C:\Condor/condor_config.local
3/1 12:34:44 DaemonCore: Command Socket at <152.14.22.60:3593>
3/1 12:34:44 "C:\Condor/bin/condor_shadow.pvm -classad" did not produce
any output, ignoring
3/1 12:34:44 "C:\Condor/bin/condor_shadow.std -classad" did not produce
any output, ignoring
3/1 12:35:38 DaemonCore: Command received via UDP from host
<152.14.22.60:3625>
3/1 12:35:38 DaemonCore: received command 421 (RESCHEDULE), calling
handler (reschedule_negotiator)
3/1 12:35:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 12:35:38 Called reschedule_negotiator()
3/1 12:40:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 12:45:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 12:50:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 12:55:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:00:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:05:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:10:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:15:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:20:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx
3/1 13:25:38 Sent ad to central manager for rkvenkat@xxxxxxxxxxxxxxx

-Ravi

> On Tue, 1 Mar 2005, Ravi Krishnan Venkatesan wrote:
>
> >
> > Hi,
> >
> > I have a pool of 85 machines - Windows (64) + Linux (20). When I submit a
> > job from a windows machine it justs sits there in idle state. & when I do
> > a condor_q -analyze, I get the following :
> >
> > -- Submitter: warthog.ecew2k.ncsu.edu : <152.14.22.60:3593> :
> > warthog.ecew2k.ncsu.edu
> >   ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD
> >  ---
> >  008.000:  Run analysis summary.  Of 85 machines,
> >       20 are rejected by your job's requirements
> >       23 reject your job because of their own requirements
> >        0 match, but are serving users with a better priority in the pool
> >       42 match, 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
> >
> >  1 jobs; 1 idle, 0 running, 0 held
> >
> >
> > - What is that unknown reasons ? Can anyone plz help ?
> >
> > -Ravi
> >
>