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

Re: [Condor-users] Antwort: Re: Several Issues With Condor 6.7.20 and Windows

On 6/27/06, thomas.t.hoppe@xxxxxxxxxxxxxxxxxxx
<thomas.t.hoppe@xxxxxxxxxxxxxxxxxxx> wrote:

Hi Matt,
I re-check permissions and even let the condor service run as local administrator.
I also allowec everyone to access everything below c:\condor
with no success.

the condor service should really run as local admin anyway.

Plus: C:\WINDOWS\system32\cmd.exe exists!

cool - I just wanted to check. it is the IWD that is the issue

Maybe the problem is caused by this the batch file condor_exec.bat
I'm not sure whether the file transmission is working (in condor.config I also configured a shared filesystem with
euqal domain).
I don't want this file to be transfered all the time anyway. Where would this file be located if
everything goes well?

this file has to get transferred since you are going to a windows
machine and thus the executing user has no privilidge to acess a
remote file system even if it was exposed...
(I am assuming you are not currently trying to use the new
functionality in the latest condor where you can store credentials
with a server so the remote user will be the same as the submitting

Regarding the absolute paths for output.txt and so on:
I have to say this is not possible. If I leave those paths relative, I get the following error on my executor:

6/27 14:25:28 ******************************************************
6/27 14:25:28 ** condor_starter (CONDOR_STARTER) STARTING UP
6/27 14:25:28 ** C:\condor\bin\condor_starter.exe
6/27 14:25:28 ** $CondorVersion: 6.7.20 Jun 21 2006 $
6/27 14:25:28 ** $CondorPlatform: INTEL-WINNT50 $
6/27 14:25:28 ** PID = 340
6/27 14:25:28 ** Log last touched 6/27 14:25:26
6/27 14:25:28 ******************************************************
6/27 14:25:28 Using config source: C:\condor\condor_config
6/27 14:25:28 Using local config sources:
6/27 14:25:28    C:\condor/condor_config.local
6/27 14:25:28 DaemonCore: Command Socket at <####:1655>
6/27 14:25:28 Setting resource limits not implemented!
6/27 14:25:28 Communicating with shadow <####:35832>
6/27 14:25:28 Submitting machine is "####"
6/27 14:25:28 Starting a VANILLA universe job with ID: 125.0
6/27 14:25:28 IWD: /home/hopptho/condor_test/test
6/27 14:25:28 Failed to open '/home/hopptho/condor_test/test\printname.out.0' as standard output: No such file or directory (errno 2)
6/27 14:25:28 Failed to open some/all of the std files...
6/27 14:25:28 Aborting OsProc::StartJob.
6/27 14:25:28 Failed to start job, exiting
6/27 14:25:28 ShutdownFast all jobs.
6/27 14:25:28 **** condor_starter (condor_STARTER) EXITING WITH STATUS 0

As you see, condor sets some IWD to the path on the submitting machine!
I cannot understand why condor is doing this it makes no sense from my perspective.
Is there no sound solution for this problem?

Try forcing file transfer (it may think that the shared file system is
available to the executing machine as you are submitting from linux)
Look at should_transfer_files in the condor_submit docs and try
leaving your paths relative.