I
always end up having to do it manually. That is following these steps .
. .
1. find out what the requirements for the job are and listing out
the attributes one by one
condor_q -long
<cluster>.<proc>
2. listing out the machine attributes one by
one
condor_status -long [hostname]
3.
when you have those, you can go through attribute by attribute and
compare.
For
example, the requirements on one of my jobs is (computer names changed to
protect the innocent) . . .
v:\users\tjones>condor_q -long 310.0 | grep
"^Requirements"
Requirements = (Machine == "abc.example.com" && (OpSys ==
"WINNT50" || OpSys == "WINNT51" || OpSys == "WINNT52")) && (Arch ==
"INTEL") && (Disk >= DiskUsage) && ((Memory * 1024) >=
ImageSize) && (HasFileTransfer) && (HasWindowsRunAsOwner
&& (LocalCredd =?= "def.example.com:9620"))
Let's just look at ((Memory * 1024) >= ImageSize). Memory is
an attribute of the target machine . . .
v:\users\tjones>condor_status -long abc.example.com | grep
"^Memory"
Memory = 1022
ImageSize is an attribute of the job . . .
v:\users\tjones>condor_q -long 310.0 | grep
"^ImageSize"
ImageSize_RAW = 0
ImageSize = 0
Doing a replacement ((1022 * 1024) >= 0) is true.
As you can see the attribute matches, so that's not the reason why it
was rejected, so I move on the another attribute, until I find which one is
the problem.
Unfortunately, this is very tedious. I hear that condor on unix
has "condor_q -better-analyze" which does all this for you. By the way,
I didn't use stock windows commands here. You may or may not have grep
installed.
my excel macro
jobs will run without USE_VISIBLE_DESKTOP on w2k3.
i can now also get them to run now on the xp machine as well.
the jobs fail if i restart condor on the xp machine without a reboot.
without the reboot, enabling USE_VISIBLE_DESKTOP allows the
jobs to run. it looks like this is some windows idiosyncracy.
condor_q analyze says "2 are rejected
by your jobs's requirements". perhaps there is some active directory
setting i need to enable for my user? is there a way to find out
exactly why it is being rejected? log file? query?
kurt
"Jones, Torrin A \(US
SSA\)" <torrin.jones@xxxxxxxxxxxxxx> Sent by:
condor-users-bounces@xxxxxxxxxxx
07/12/2007 10:03 AM
Please respond
to Condor-Users Mail List
<condor-users@xxxxxxxxxxx> |
|
To
| "Condor-Users Mail List"
<condor-users@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: [Condor-users]
USE_VISIBLE_DESKTOP and CREDD
issues |
|
I imagine that excel needs a gui to run, even
though it's a macro. That's probably why you need
USE_VISIBLE_DESKTOP.
I'm not sure about the credd problem.
When you submit a job directly to a winxp client what does "condor_q
-analyze" say?
-----Original
Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of
kvandenberg@xxxxxxx
Sent: Wednesday, July 11, 2007
19:23
To: Condor-Users Mail List
Subject: [Condor-users]
USE_VISIBLE_DESKTOP and CREDD issues
i am using condor 6.9.3 with a win2k3 server as master with an xp
slave. when jobs get allocated to the slave they exit with the message
below unless i have USE_VISIBLE_DESKTOP enabled on the slave. if
USE_VISIBLE_DESKTOP is enabled the job runs successfully. i do not
have condor_credd daemon running in this scenario. the jobs are excel
spreadsheets which autorun a macro and exit and saving results.
when trying to run credd
daemon and use run as owner on the w2k3 server, jobs never get allocated to
the xp client. all jobs get allocated to the w2k3 server and run
successfully. i tried dozens of confi variations with HOSTALLOW***,
included the necessary vars CREDD_HOST, STARTER_ALLOW_RUNAS_OWNER,
SEC_CLIENT_AUTHENTICATION_METHODS, CREDD_CACHE_LOCALLY, done all the
condor_store_cred variations, etc,etc.
so the 2 problems/questions are;
1. why does
USE_VISIBLE_DESKTOP have to be enabled for my jobs to run successfully on
the xp slave?
2. why won't the xp slave get jobs allocated when i try to run
with credd?
any ideas? thanks.
*********************************job log
005 (260.005.000) 07/11 22:00:57 Job
terminated.
(1) Normal termination (return value
-1073741502)
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
0 - Run Bytes Sent By Job
89463072 - Run Bytes Received By Job
0 -
Total Bytes Sent By Job
89463072 -
Total Bytes Received By Job
********************************my submit file is as
follows;
Executable
= run-excel.bat
Universe
= vanilla
#run_as_owner
= true
Requirements
= OpSys == "WINNT51" || OpSys
=="WINNT52"
should_transfer_files =
YES
when_to_transfer_output = ON_EXIT
#noop_job_exit_code
= 0
transfer_input_files =
n:\kva\condor\condor-test2.xlsm, n:\kva\condor\condor-test3.xlsm,
n:\kva\condor\condor-test4.xlsm, n:\kva\condor\condor-test5.xlsm,
n:\kva\condor\condor-test6.xlsm,
n:\kva\condor\condor-test7.xlsm
log
= job.log
Output
= out.log
Error
= error.log
getenv
= True
Arguments
= condor-test2.xlsm
Queue
Arguments
=
condor-test3.xlsm
Queue
Arguments
= condor-test4.xlsm
Queue
Arguments
= condor-test5.xlsm
Queue
priority
= 5
Arguments
= condor-test6.xlsm
Queue
priority
= 6
Arguments
= condor-test7.xlsm
Queue
Kurt Vandenberg
Chief
Technology Officer
Financial Security Assurance, Inc.
31 West 52nd
Street
New York, New York 10019
O: +1 212 339 0826
C: +1 917 378
4527
www.fsa.com
"Ian Chesal"
<ICHESAL@xxxxxxxxxx> Sent by:
condor-users-bounces@xxxxxxxxxxx
05/27/2007 09:42 PM
Please respond
to Condor-Users Mail List
<condor-users@xxxxxxxxxxx> |
|
To
| "Condor-Users Mail
List" <condor-users@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: [Condor-users]
USE_VISIBLE_DESKTOP stops working after a
while |
|
> > Tony: good idea. This
could be close to the problem. We
> don't enable
> >
Windows Terminal Services on these machines. But we do keep them
>
> logged in as a domain user that's been given Administrator
>
access to
> > the box and check on their GUI sessions with VNC.
I'll see
> if logging
> > the machine out has any effect
(although then there wouldn't be a
> > visible desktop to use
which might not work).
>
> VNC (and its clones and commercial
ports) use a very similar
> hooking mechanism as remote desktop to
the extent that use on
> one while the other is active tends to kill
one or both of
> them. I would treat your VNC client as the most
likely candidate.
I'll test with VNC disabled and see if that solves
the problem then.
Thanks Matt and Tony!
-
Ian
_______________________________________________
Condor-users
mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can
also unsubscribe by
visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The
archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
____________________________________
This e-mail message
is for the sole use of the intended recipient(s) and
may contain
proprietary, confidential and/or privileged information. Any
unauthorized
review, use, disclosure or distribution is prohibited. If you
are
not the intended recipient (or an employee or agent responsible
to
deliver it to the intended recipient), you may not copy or deliver
this
message to anyone. In such case, you should destroy this message and
kindly
notify the sender by reply e-mail._______________________________________________
Condor-users
mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can
also unsubscribe by
visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The
archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
____________________________________
This
e-mail message is for the sole use of the intended recipient(s) and
may
contain proprietary, confidential and/or privileged information.
Any
unauthorized review, use, disclosure or distribution is prohibited.
If you
are not the intended recipient (or an employee or agent
responsible to
deliver it to the intended recipient), you may not copy or
deliver this
message to anyone. In such case, you should destroy this
message and kindly
notify the sender by reply
e-mail.