[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [condor-users] jobs don't start
In my previous message I meant
"This will answer the question, whether Condor has or has no write
access to the submission DIRECTORY (not file)."
On Thu, 2003-07-31 at 15:43, Thomas Bauer wrote:
> Yes, I have write-access to this directory. But it seems to me, that the
> "condor-software" has not.
> It makes me wonder, that the manual says, that with Windows, there is no
> need for a user "condor" as in the unix-systems.
> But Condor creates a local user named "condor-reuse-vm1" Do you know, what
> this is for? Maybe this user needs full privilegs or something?
> Thomas Bauer
> On Thu, 31 Jul 2003 13:35:48 +0100, Alexander Klyubin
> <A.Kljubin@xxxxxxxxxxx> wrote:
> > Condor copies all the files produced by your job back to the directory
> > from where the job was submitted *on the machine from where the job was
> > submitted*. This means you should have write access to the directory from
> > where you submit the job.
> > Regards,
> > Alexander Klyubin
> > On 07/31/2003 01:29 PM, Thomas Bauer wrote:
> >> On Thu, 31 Jul 2003 12:35:40 +0100, Alexander Klyubin
> >> <A.Kljubin@xxxxxxxxxxx> wrote:
> >>> I wonder why the ShadowLog you sent earlier references some checkpoint
> >>> file which it allegedly fails to transfer:
> >>> C:\Condor\spool\cluster7.ickpt.subproc0. You aren't using any
> >>> checkpointing -- Vanilla universe does not support it...
> >> That's right, I'm not using the checkpoint-feature
> >>> I hope trapezregel.exe was compiled *without* Condor checkpointing?
> >> Yes trapezregel.exe is a fortran-compiled executable. It runs for a few
> >> seconds and writes as output three files: fort.19, fort.20 and fort.21
> >>> If trapezregel.exe is just a normal executable, which runs perfectly on
> >>> any of those machines if you install it there manually, then may be you
> >>> should try explicitly telling Condor which files to transfer and when.
> >>> Try adding following to the submission file:
> >>> transfer_input_files = trapezregel.exe
> >>> should_transfer_files = YES
> >>> when_to_transfer_output = ON_EXIT_OR_EVICT
> >> I added these lines to the submission file and the job ran for a few
> >> seconds, but it did not finish.
> >> But I found in the Shadowlog, that the error-message has changed. The
> >> error-message is now, that the output-file (fort.19) could not be
> >> written to the directory c:\condor\batch. I'm not sure, if condor tries
> >> to write this output-file directly to the computer, from which I started
> >> this job, or to the computer, on which the job is running in the moment.
> >> I think I'll have to talk to my administrator. Somewhere must be a lock,
> >> which denies condor to write the output files to the harddisk.
> >> Greetings,
> >> Thomas
> > Condor Support Information:
> > http://www.cs.wisc.edu/condor/condor-support/
> > To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
> > unsubscribe condor-users <your_email_address>
Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>