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

Re: [Condor-users] condor - testing errors



Hi bruce,
You're almost there. You need to give your master write/read writes in
all your condor_config files
So just specify your domain

For example 
UID_DOMAIN = domain.org
FILESYSTEM_DOMAIN = wurnet.nl
HOSTALLOW_READ = *.domain.org 
HOSTALLOW_WRITE = *.domain.org 

Jan

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of bruce
Sent: maandag 31 juli 2006 9:25
To: condor-users@xxxxxxxxxxx
Subject: [Condor-users] condor - testing errors

hi...

this is further continuance of my testing with condor.

i've been able to get a sample app running with a 2 node system. i can
do 'condor_submit' from both the master/child node and i see both
machines.

the condor_config file for both machines is pretty much the sample file,
with limited changes. using the sample, my test apps appear to have a
wait/delay of 5 mins. my goal is to be able to run as many apps as fast
as i possibly can, on the machines in the network.. i'd also like to be
able to see what machines the app(s) are actually running on...

i tried to run the test function listed in the 'condor_config' file,
using:

   ##  Replace UWCS_* with TESTINGMODE_* if you wish to do testing mode.

i also used the following:
  StartIdleTime		= 2 * $(MINUTE)
  ContinueIdleTime	=  $(MINUTE)
  MaxSuspendTime		= 1 * $(MINUTE)
  MaxVacateTime		= 1 * $(MINUTE)

in an attempt to try to run as fast as possible during the tests.

my test doesn't run, instead, the StartLog indicates that I have some
kind of an error. a sample of the StartLog contents is listed below. as
i indicated, the test submit app i'm running has run successfully with
the initial condor_config file, prior to my changes...

any thoughts/suggestions/help would be appreciated!!

thanks

-bruce


sample StartLog contents...
7/30 23:51:40 match_info called
7/30 23:51:40 Received match <192.168.1.33:42714>#1154324088#25
7/30 23:51:40 State change: match notification protocol successful 7/30
23:51:40 Changing state: Unclaimed -> Matched 7/30 23:51:41 DaemonCore:
PERMISSION DENIED to unknown user from host <192.168.1.55:33433> for
command 442 (REQUEST_CLAIM) 7/30 23:51:41 DaemonCore: PERMISSION DENIED
to unknown user from host <192.168.1.55:33062> for command 443
(RELEASE_CLAIM) 7/30 23:53:40 State change: match timed out 7/30
23:53:40 Changing state: Matched -> Owner 7/30 23:53:40 State change:
IS_OWNER is false 7/30 23:53:40 Changing state: Owner -> Unclaimed 7/30
23:56:41 DaemonCore: Command received via UDP from host
<192.168.1.55:33073> 7/30 23:56:41 DaemonCore: received command 440
(MATCH_INFO), calling handler
(command_match_info)
7/30 23:56:41 match_info called
7/30 23:56:41 Received match <192.168.1.33:42714>#1154324088#27
7/30 23:56:41 State change: match notification protocol successful 7/30
23:56:41 Changing state: Unclaimed -> Matched 7/30 23:56:41 DaemonCore:
PERMISSION DENIED to unknown user from host <192.168.1.55:33458> for
command 442 (REQUEST_CLAIM) 7/30 23:56:41 DaemonCore: PERMISSION DENIED
to unknown user from host <192.168.1.55:33073> for command 443
(RELEASE_CLAIM) 7/30 23:58:41 State change: match timed out 7/30
23:58:41 Changing state: Matched -> Owner 7/30 23:58:41 State change:
IS_OWNER is false 7/30 23:58:41 Changing state: Owner -> Unclaimed



_______________________________________________
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 either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR