Home | News | Documentation | Download

[PROOF] PAR package with different sandbox location


#1

Hello everyone,

I am facing an issue when I change my ProofLite server location.
My $HOME/.proof does not contain enough space. So I wanted to start it on LXbatch.
When I start the job, I change the location of the sandbox using :

TString proof_sandbox = "./.proof/"
gEnv->SetValue("Proof.Sandbox", proof_sandbox);

Then in my ROOT code I use UploadPackage and EnablePackage.
to enable my package, but I get these errors:

Error in <TSystem::ExpandFileName>: input: $ŔOOT/bin/gunzip, output: $ŔOOT/bin/gunzip
# Enabling package.. DYOverview.par
Info in <TProofLite::BuildPackageOnClient>: DYOverview: version change (current: 6.06/08:v6-06-06-30-g3bae07b, build: :): cleaning ... 
Error in <TSystem::ExpandFileName>: input: $ŔOOT/bin/gunzip, output: $ŔOOT/bin/gunzip
gzip: proof-test/packages/DYOverview.par.gz: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
gzip: proof-test/packages/DYOverview.par.gz: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Error in <TProofLite::BuildPackageOnClient>: failure executing: /bin/gunzip -c proof-test/packages/DYOverview.par | (tar xf -)
-- BUILD.sh
--> event-BUILD: PROOF client
--> Library UIUC found in PAR archive : /afs/cern.ch/work/m/meyerma/Opt/escalade/proof-test/packages/DYOverview/lib/libUIUC.so
-- SETUP.C
--> Loading library libUIUC.so.. .

Nevertheless the package seems to be loaded and the content of my PAR archive is correctly untar so I don’t understand why this is not working properly ? Someone has an idea ?
NB: When I stay in the usual location $HOME/.proof, of course there is no problem and I correctly proccess my data with proof.

Thanks you very much !

ROOT: 6.06/08
GCC: 4.9


#2

Hi,

our PROOF expert will be back in a few days. We’ll address this item asap.

Cheers,
Danilo


#3

Hello Danilo,

Thank for the notification. I think I found the solution.
I used absolute link. It works much better :slight_smile:


#4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.