Hi again!
The jobs are now running in the central manager. I added STARTD
to the daemon_list.
But the other machine of my condor pool is still not executing.
The CredLog looks like this,
09/03 13:38:20 Locale: English_United States.1252
09/03 13:38:20 WARNING: Config source is empty: C:\condor/condor_config.local
09/03 13:38:20 ******************************************************
09/03 13:38:20 ** condor_credd.exe (CONDOR_CREDD) STARTING UP
09/03 13:38:20 ** C:\condor\bin\condor_credd.exe
09/03 13:38:20 ** SubsystemInfo: name=CREDD type=DAEMON(11) class=DAEMON(1)
09/03 13:38:20 ** Configuration: subsystem:CREDD local:<NONE>
class:DAEMON
09/03 13:38:20 ** $CondorVersion: 7.4.1 Dec 17 2009 BuildID: 204351 $
09/03 13:38:20 ** $CondorPlatform: INTEL-WINNT50 $
09/03 13:38:20 ** PID = 756
09/03 13:38:20 ** Log last touched 9/3 12:38:13
09/03 13:38:20 ******************************************************
09/03 13:38:20 Using config source: C:\condor\condor_config
09/03 13:38:20 Using local config sources:
09/03 13:38:20 C:\condor/condor_config.local
09/03 13:38:20 DaemonCore: Command Socket at <10.110.44.212:1342>
09/03 13:38:20 Will use UDP to update collector
o2f-sth-lap-016.un.dr.dgcsystems.net <10.110.44.76:9618>
09/03 13:38:20 main_init() called
09/03 13:38:20 Trying to update collector <10.110.44.76:9618>
09/03 13:38:20 Attempting to send update via UDP to collector
o2f-sth-lap-016.un.dr.dgcsystems.net <10.110.44.76:9618>
09/03 13:38:20 File descriptor limits: max 1024, safe 820
09/03 13:38:20 Initialized the following authorization table:
09/03 13:38:20 Authorizations yet to be resolved:
09/03 13:38:20 allow NEGOTIATOR: */10.110.44.76
*/o2f-sth-lap-016.un.dr.dgcsystems.net
And the StartLog,
09/03 14:29:10 Locale: English_United States.1252
09/03 14:29:10 ******************************************************
09/03 14:29:10 ** condor_startd.exe (CONDOR_STARTD) STARTING UP
09/03 14:29:10 ** C:\condor\bin\condor_startd.exe
09/03 14:29:10 ** SubsystemInfo: name=STARTD type=STARTD(7) class=DAEMON(1)
09/03 14:29:10 ** Configuration: subsystem:STARTD local:<NONE>
class:DAEMON
09/03 14:29:10 ** $CondorVersion: 7.4.1 Dec 17 2009 BuildID: 204351 $
09/03 14:29:10 ** $CondorPlatform: INTEL-WINNT50 $
09/03 14:29:10 ** PID = 3424
09/03 14:29:10 ** Log last touched 9/3 13:29:01
09/03 14:29:10 ******************************************************
09/03 14:29:10 Using config source: C:\condor\condor_config
09/03 14:29:10 Using local config sources:
09/03 14:29:10 C:\condor/condor_config.local
09/03 14:29:10 DaemonCore: Command Socket at <10.110.44.212:1479>
09/03 14:29:10 my_popen: CreateProcess failed
09/03 14:29:10 Failed to run hibernation plugin 'C:\condor/libexec/power_state
ad'
09/03 14:29:16 my_popen: CreateProcess failed
09/03 14:29:16 Failed to execute C:\condor/bin/condor_starter.std.exe, ignoring
09/03 14:29:16 VM-gahp server reported an internal error
09/03 14:29:16 VM universe will be tested to check if it is available
09/03 14:29:16 History file rotation is enabled.
09/03 14:29:16 Maximum history file size is: 20971520 bytes
09/03 14:29:16 Number of rotated history files is: 2
09/03 14:29:16 New machine resource allocated
09/03 14:29:21 About to run initial benchmarks.
09/03 14:29:27 Completed initial benchmarks.
09/03 14:29:27 State change: IS_OWNER is false
09/03 14:29:27 Changing state: Owner -> Unclaimed
Do you believe that this machine is not executing due to the
problem with storing the credential or might be something else?
/Sónia
Från: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] För Sónia Liléo
Skickat: den 3 september 2010 12:24
Till: 'Condor-Users Mail List'
Ämne: Re: [Condor-users] Store a credential for a condor user
Thanks for your suggestions Ian and Michael!
The credential was now successfully stored in the central
manager but I am still getting the same error message in the execute machine (I
am just setting up a simple condor pool with 2 machines for the moment).
I have another question.
I have configured the central manager so that it should be able
to both submit and execute jobs (START = TRUE).
But when I submit a job the central manager does not execute it.
My “run.sub” file looks like this,
universe = vanilla
environment = path=C:\Windows;C:\Windows\System32
transfer_executable = true
requirements = LoadAvg < 0.3
executable = Run.bat
log = Run_condor.log
output = Run_condor.out
error = Run_condor.err
queue
What should happen when doing “condor_submit
run.sub”?
Is the job only queued or should it also be executed?
Condor_status gives the following,
Name
OpSys Arch
State Activity LoadAv Mem ActvtyTime
O2F-sth-LAP-002.un WINNT51 INTEL
Unclaimed Idle 0.000 1527 0+00:50:19
Total Owner Claimed Unclaimed Matched Preempting Backfill
INTEL/WINNT51 1
0
0
1 0
0 0
Total 1
0
0 1
0
0 0
O2F-sth-LAP-002.un is not the central manager but the other
machine that I am trying to add to the pool.
It is listed by condor_status although condor_store_cred still
gives the answer
Operation failed.
Make sure your ALLOW_WRITE setting includes this
host.
The activity status is “unclaimed”. What do this
mean?
Should the central manager also be listed in the condor_status since it is also
an execute machine?
Cheers,
Sónia
Från: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] För Michael O'Donnell
Skickat: den 2 september 2010 16:29
Till: Condor-Users Mail List
Ämne: Re: [Condor-users] Store a credential for a condor user
You
might also check your configuration settings for the cred security (e.g.,
CREDD.SEC_DEFAULT_AUTHENTICATION and others) and verify your settings are
correct for LOCAL_CREDD,. CREDD_HOST, CREDD_CACHE_LOCALLY.
Michael
From:
|
Sónia
Liléo <sonia.lileo@xxxxx>
|
To:
|
"'condor-users@xxxxxxxxxxx'"
<condor-users@xxxxxxxxxxx>
|
Date:
|
09/02/2010
04:22 AM
|
Subject:
|
[Condor-users]
Store a credential for a condor user
|
Sent by:
|
condor-users-bounces@xxxxxxxxxxx
|
Hi!
I am trying
to store the credentials for the users of a condor pool by using the command
Condor_store_cred add.
I get the
following error message,
Operation
failed.
Make sure your ALLOW_WRITE setting includes this host.
The command “condor_config_val
ALLOW_WRITE” gives the following output
C:\>condor_config_val
ALLOW_WRITE
*
When running condor_submit
I get the following error message,
ERROR:
No credential stored for o2f_sonlil@HO
Correct this by running:
condor_store_cred add
It seems that
the job I am trying to run requires that the condor users have stored
credentials but I am not able to store them.
Any
suggestions for how to solve this problem?
Best Regards,
Sónia
Sónia
Liléo
O2 Strandvägen 5B 114 51 Stockholm
Tel: +46 8 559 310 37 Mobile: +46 73 752 95 74
www.o2.se
_______________________________________________
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/