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

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




Hi,

ok now I tried the job:

universe = vanilla
environment = path=C:\WINDOWS\system32
executable = test_win.bat
#output = printname.out.$(Process)
#error = printname.err
#log = printname.log
Arguments  = -arg1 -arg2
should_transfer_files = yes
transfer_executable = true
WhenToTransferOutput = ON_EXIT
requirements = Activity=="idle" && Arch=="INTEL" && OpSys=="WINNT51"
queue

which is basically a slightly modified condor sample.
test_win.bat is in the same directory in the linux/submit machine.

And obtain:
6/27 17:04:08 ******************************************************
6/27 17:04:08 ** condor_starter (CONDOR_STARTER) STARTING UP
6/27 17:04:08 ** C:\condor\bin\condor_starter.exe
6/27 17:04:08 ** $CondorVersion: 6.7.20 Jun 21 2006 $
6/27 17:04:08 ** $CondorPlatform: INTEL-WINNT50 $
6/27 17:04:08 ** PID = 416
6/27 17:04:08 ** Log last touched time unavailable (No such file or directory)
6/27 17:04:08 ******************************************************
6/27 17:04:08 Using config source: C:\condor\condor_config
6/27 17:04:08 Using local config sources:
6/27 17:04:08    C:\condor/condor_config.local
6/27 17:04:08 DaemonCore: Command Socket at <####:2933>
6/27 17:04:08 Setting resource limits not implemented!
6/27 17:04:08 Communicating with shadow <####:36343>
6/27 17:04:08 Submitting machine is "####"
6/27 17:04:09 File transfer completed successfully.
6/27 17:04:10 Starting a VANILLA universe job with ID: 137.0
6/27 17:04:10 IWD: C:\condor/execute\dir_416
6/27 17:04:10 Output file: C:\condor/execute\dir_416\printname.out.0
6/27 17:04:10 Error file: C:\condor/execute\dir_416\printname.err
6/27 17:04:10 Renice expr "10" evaluated to 10
6/27 17:04:10 About to exec C:\WINDOWS\system32\cmd.exe condor_exec.exe /Q /C condor_exec.bat -arg1 -arg2
6/27 17:04:10 Create_Process succeeded, pid=592
6/27 17:04:10 Process exited, pid=592, status=0
6/27 17:04:10 Got SIGQUIT.  Performing fast shutdown.
6/27 17:04:10 ShutdownFast all jobs.
6/27 17:04:10 **** condor_starter (condor_STARTER) EXITING WITH STATUS 0

And it wors!!! many thanks

Just a note: This and the problem with the windows installer cost me several days.
If the documentation would clearly state, that it implicitely changes the IWD behaviour
when using file transfer, I might have been faster...



Regards, Thomas



matthew.hope@xxxxxxxxx
Gesendet von: condor-users-bounces@xxxxxxxxxxx

27.06.2006 15:35

Bitte antworten an
condor-users@xxxxxxxxxxx

An
condor-users@xxxxxxxxxxx
Kopie
Thema
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
one?)

> 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.

Also
_______________________________________________
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