Re: [Condor-users] Condor Problem with Environment

[Douglas L Thain <dthain@xxxxxxxxxx>]

Senthil -

You can solve that with the -H option to Parrot.
Let's continue this conversation off of the mailing list...

Doug



On Mon, 15 May 2006, Natarajan, Senthil wrote:

> Doug,
> I tried like that but I got some error. Here is the job description. Can
> you point out how to fix this.
>
> universe = vanilla
> executable = first
> Arguments = run1.tgz
> GetEnv = True
> output = first.out
> error = first.err
> log = first.log
> should_transfer_files = YES
> when_to_transfer_output = ON_EXIT
> transfer_input_files = run1.tgz
> environment = LD_LIBRARY_PATH=/chirp/server.name.pitt.edu/library
> queue
>
>
> first.err
> *********
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
> ERROR: ld.so: object
> '/usr/local/GridComputing/software/cctools-2_1_1-i686-linux-2.4/bin/parr
> ot_helper.so' from LD_PRELOAD cannot be preloaded: ignored.
>
>
>
> -----Original Message-----
> From: Douglas L Thain [mailto:dthain@xxxxxxxxxx]
> Sent: Monday, May 15, 2006 11:40 AM
> To: Natarajan, Senthil
> Cc: Condor-Users Mail List
> Subject: RE: [Condor-users] Condor Problem with Environment
>
>
> Senthil -
>
> You do not have to install Parrot everywhere.
>
> As the HOWTO document shows, you can install Parrot on your submit node,
> and then tell Condor to send a copy along with each job.
>
> Doug
>
>
> On Mon, 15 May 2006, Natarajan, Senthil wrote:
>
> > Hi Doug,
> > Thanks for the Info. I have a quick question does Parrot needs to be
> > installed in all the execution nodes, in order for jobs to connect to
> > file server(chirp) and get the shared library. Please let me know.
> > Thanks,
> > Senthil
> >
> >
> > -----Original Message-----
> > From: condor-users-bounces@xxxxxxxxxxx
> > [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Douglas L Thain
> > Sent: Friday, May 12, 2006 2:35 PM
> > To: Condor-Users Mail List
> > Subject: Re: [Condor-users] Condor Problem with Environment
> >
> >
> > Senthil -
> >
> > If there are too many libraries to copy them around manually,
> > another option is to do remote dynamic linking with Parrot.
> > Essentially, this allows your LD_LIBRARY_PATH to point
> > to libraries stored elsewhere on the network.
> >
> > Here is a short how-to document:
> >
> > http://www.cse.nd.edu/~ccl/software/howto/remotelink.shtml
> >
> > Cheers -
> > Doug
> >
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
>