Amanda-Users

Re: perl errors in taper debug files

2008-12-19 14:51:53
Subject: Re: perl errors in taper debug files
From: Jean-Francois Malouin <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca>
To: John Hein <jhein AT timing DOT com>
Date: Fri, 19 Dec 2008 14:46:14 -0500
* John Hein <jhein AT timing DOT com> [20081219 14:09]:
> Jean-Francois Malouin wrote at 14:00 -0500 on Dec 19, 2008:
>  > * Dustin J. Mitchell <dustin AT zmanda DOT com> [20081219 13:51]:
>  > > On Fri, Dec 19, 2008 at 1:28 PM, Jean-Francois Malouin
>  > > <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca> wrote:
>  > > > for module Amanda::Types: 
> /usr/local/share/perl/5.8.8/auto/Amanda/Types/libTypes.so: cannot open shared 
> object file: No such file or
>  > > > directory at /usr/lib/perl/5.8/DynaLoader.pm line 225.
>  > > 
>  > > > Should I be worried? I guess this is part of the new API
>  > > > and all the swig stuff which I'm totally clueless about.
>  > > > Is something not quite kosher in my local perl setup?
>  > > 
>  > > Yep.  Does that .so file exist?  Sometimes libdl gives "No such file
>  > > or directory" when it can't find the *dependencies* of a shared
>  > > object.  Assuming libTypes.so exists, what does 'ldd' tell you about
>  > > it?  What platform is this?  Was it installed from a package or from
>  > > source?
>  > 
>  > Dustin, 
>  > 
>  > Yes, it exists: see my other post about the output of ldd.
>  > 
>  > I think the problam might be related the having libglib dso's in
>  > /opt/lib64 (installed from source) and not having this in
>  > LD_LIBRARY_PATH.
>  > 
>  > This is on Debian/Etch running 2.6.26.5-i686-64-smp.
> 
> Did the ldd you ran have a different env than amanda (i.e., did your
> ldd run have LD_LIBRARY_PATH set?)?
> 
> If it is just an LD_LIBRARY_PATH issue, you may want to consider
> putting /opt/lib64 into your ldconfig config (/etc/ld.*conf* under
> linux).

tick!
That was it. I did a test with amtape (debug files shows the 
same 'cannot open shared object file' error messages) and after
adding /opt/lib64 to ld.so.conf and updating with ldconfig the
error message went away. 

thanks!
jf

> 
> Since you're on linux, you can run 'ldd -v ...' to chase down
> missing dependencies in the dependencies.

-- 
<° >< Jean-François Malouin          McConnell Brain Imaging Centre        
Systems/Network Administrator       Montréal Neurological Institute
3801 Rue University, Suite WB219, Montréal, Québec, H3A 2B4, Canada

<Prev in Thread] Current Thread [Next in Thread>