[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [condor-users] File transfer failing on one box, odd problem
- Date: Thu, 10 Jun 2004 15:55:37 -0700 (PDT)
- From: Vahid Pazirandeh <vpaziran@xxxxxxxxx>
- Subject: RE: [condor-users] File transfer failing on one box, odd problem
What is the benefit of enabling copy_to_spool? Does it copy only the
executable or all transfer_input_files as well?
--- Carl Howard <carl.howard@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> I had a similar sort of problem that was caused by a lack of space in the
> temporary directory... the problem was solved by putting
> copy_to_spool = false
> in the submission script. I was shifting 250MB x 200 jobs to the workers
> -----Original Message-----
> From: owner-condor-users@xxxxxxxxxxx [mailto:owner-condor-users@xxxxxxxxxxx]
> On Behalf Of Alain Roy
> Sent: Thursday, 3 June 2004 2:47 AM
> To: condor-users@xxxxxxxxxxx
> Subject: Re: [condor-users] File transfer failing on one box, odd problem
> Sam Evans wrote:
> >The error I get in the StarterLog.vm1 is this:
> >6/1 21:49:18 Using config file: /home/condor/condor_config
> >6/1 21:49:18 Using local config files:
> >/home/condor/hosts/hostname.local 6/1 21:49:18 DaemonCore: Command
> >Socket at <x.x.x.x:33144> 6/1 21:49:18 Done setting resource limits 6/1
> >21:49:18 Starter communicating with condor_shadow <x.x.x.x:59870> 6/1
> >21:49:18 Submitting machine is "master.hostname.com" 6/1 21:49:18 File
> >transfer failed (status=0). 6/1 21:49:18 ERROR "Failed to transfer
> >files" at line 1232 in file jic_shadow.C
> >6/1 21:49:18 ShutdownFast all jobs.
> Do you get an errors in the ShadowLog on the submit host that shed some
> light on the problem?
> Are you out of disk space? Are the permissions not set up correctly on the
> directories used by Condor and/or the job? These are the most likely
> If these don't help, you can try increasing the debugging output in the log
> files, and seeing if it helps out at all.
> On the submit host, edit SHADOW_DEBUG to have an additional flag:
> SHADOW_DEBUG = D_FULLDEBUG
> If there are already things on that line, just add D_FULLDEBUG, with a
> space separating it from what it there.
> On the execution host, edit STARTER_DEBUG to also have D_FULLDEBUG. Then do
> a condor_reconfig on each of those computers to make them reread their
> configuration files, and recreate the problem. Hopefully we'll see some
> extra error messages that will be enlightening.
> After debugging the problem, you will want to turn off D_FULLDEBUG, since
> it fills up the log files with lots of extra information.
> 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>
< NPACI Education Center on Computational Science and Engineering >
"A friend is someone who knows the song in your heart and can sing it back to you when you have forgotten the words." -Unknown Author
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.