Re: [Condor-users] DAGMan 6.7.6 and network drives

[filipdef@xxxxxxxxxxxxxxxxx]

Hi Pawel,

I just added support for mapped network drives to the gui:
as the first part of the job it'll test the drive connection
you set up in the preferences, and if it fails it will try
to map it. If and only if the map succeeds it puts it in
a list of drives to be unmapped at the end of the job;
this is important: if the drives are not unmapped, and
remain mapped by condor-vm1, when a regular user tries
to log in, the drives will not be accessible.

Just do an svn update on the GDI|Queue sources and you
can take a look at this stuff. You set up the mappings
you want in preferences -> condor -> network mappings.

The new stuff is not yet in the zip you download from
the site, but I'll cut a new release somewhere later
this week.

As far as submitting jobs from a newwork share itself,
afaik this cannot be done. I have to copy all dependencies
locally first, and then put the local proxies in
transfer_input_files otherwise DAGMan indeed behaves
very odd and doesn't even run the DAG. This is actually
one of the main things I would *love* to see fixed in
condor: being able to have the condor logs, submit files,...
on a network share..

Hope this helps,
- Filip


> Yes, I agree.
> If I wanted to use the network drive letters from workers I need to map
> them first.
> But this is a simple job that does not require network resources to
> complete.
> Also, DAGMan doesn't even get as far as submitting the actual condor job.
>
> Thanks,
> Pawel
>
>
>
>
>
> John Wheez <john@xxxxxxxxxx>
> Sent by: condor-users-bounces@xxxxxxxxxxx
> 04/07/2005 03:17 PM
> Please respond to john; Please respond to Condor-Users Mail List
>
>
>         To:     Condor-Users Mail List <condor-users@xxxxxxxxxxx>
>         cc:
>         Subject:        Re: [Condor-users] DAGMan 6.7.6 and network drives
>
>
> For mapped drives to work with condor you need to be sure to have a.bat
> file as your executable....int he first lines of this ..bat file you
> need to manually map the drive..you will need to specify a user and
> password which exiists....this is needed because teh condor_vm user is
> dynamically created and erased so it doens;lt know about X: at all!!!
> the solution was to manually map it in the .bat file which condor will
> execute...
>
> I've not tested this with dagman though!!!! This is how I solved teh
> problem with regular condor submit jobs with windows adn mapped
> drives....if you use UNC this is not a problem.....
>
> JW
>
>
>
> Pawel.Micun@xxxxxxxxxxxxxxxx wrote:
>
>>
>> Hello,
>>
>> In the spirit of testing DAGMan on windows... there seems to be an
>> issue with network drives.
>>
>> I mounted \\server\share as X: and placed condor files under X:\test
>> X:\test>condor_submit_dag condor.dag
>>
>> In condor.dag.lib.out I get:
>> '\\server\share\test'
>> CMD.EXE was started with the above path as the current directory.
>> UNC paths are not supported.  Defaulting to Windows directory.
>>
>> ERROR: Failed to open command file
>>
>>
>> From condor.dag.dagman.out:
>> 4/7 14:23:42 DAG Lockfile will be written to condor.dag.lock
>> 4/7 14:23:42 DAG Input file is condor.dag
>> 4/7 14:23:42 Rescue DAG will be written to condor.dag.rescue
>> 4/7 14:23:42 All DAG node user log files:
>> 4/7 14:23:42   \\server\share\test/job.log
>> 4/7 14:23:42 Parsing condor.dag ...
>> 4/7 14:23:42 Dag contains 1 total jobs
>> 4/7 14:23:42 Deleting any older versions of log files...
>> 4/7 14:23:42 Bootstrapping...
>> 4/7 14:23:42 Number of pre-completed jobs: 0
>> 4/7 14:23:42 Registering condor_event_timer...
>> 4/7 14:23:43 Submitting Condor Job A ...
>> 4/7 14:23:43 submitting: condor_submit  -a "dag_node_name = A" -a
>> "+DAGManJobID = 74.0" -a "submit_event_notes = DAG Node:
>> $(dag_node_name)" Foo.sub
>> 4/7 14:23:44 failed while reading from pipe.
>> 4/7 14:23:44 Read so far:
>> 4/7 14:23:44 condor_submit try failed
>> 4/7 14:23:44 submit command was: condor_submit  -a "dag_node_name = A"
>> -a "+DAGManJobID = 74.0" -a "submit_event_notes = DAG Node:
>> $(dag_node_name)" Foo.sub
>> 4/7 14:23:44 Job submit try 1/6 failed, will try again in >= 1 second.
>>
>>
>> My guess is that the path gets resolved to a UNC path and cmd doesn't
>> like it.
>> This is under XP SP1 and Condor 6.7.6
>>
>> Files involved:
>>
>> condor.dag:
>> JOB        A        Foo.sub
>>
>> foo.sub:
>> Universe = vanilla
>> Executable     = foo.bat
>> output  = foo.out
>> error   = foo.error
>> log = job.log
>> Queue
>>
>> foo.bat:
>> echo test
>>
>>
>> Thank You,
>> Pawel
>>
>>
> *************************************************************************
>> PRIVILEGED AND CONFIDENTIAL: This communication, including attachments,
> is
>> for the exclusive use of addressee and may contain proprietary,
>> confidential and/or privileged information. If you are not the intended
>> recipient, any use, copying, disclosure, dissemination or distribution
> is
>> strictly prohibited. If you are not the intended recipient, please
> notify
>> the sender immediately by return e-mail, delete this communication and
>> destroy all copies.
>>
> *************************************************************************
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Condor-users mailing list
>>Condor-users@xxxxxxxxxxx
>>https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
>
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users