That output looks fine. No, running the same command on the client, will get you the results on the client. The # ldd command is in no way network aware.
Saw another email, JL suggested a package to check, that would also be on the client if this was a client side issue. On Thu, Jan 12, 2012 at 08:19:26AM -0600, Neil Carter wrote: > Greetings: > > Here's the output of 'ldd /usr/local/libexec/amanda/amandad': > > /# ldd /usr/local/libexec/amanda/amandad > libamandad-3.3.0.so => /usr/local/lib/amanda/libamandad-3.3.0.so > libamanda-3.3.0.so => /usr/local/lib/amanda/libamanda-3.3.0.so > libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 > libm.so.2 => /usr/lib/libm.so.2 > libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 > libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 > libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 > libsocket.so.1 => /usr/lib/libsocket.so.1 > libnsl.so.1 => /usr/lib/libnsl.so.1 > libresolv.so.2 => /usr/lib/libresolv.so.2 > libintl.so.1 => /usr/lib/libintl.so.1 > libthread.so.1 => /usr/lib/libthread.so.1 > libc.so.1 => /usr/lib/libc.so.1 > libmp.so.2 => /usr/lib/libmp.so.2 > libmd5.so.1 => /usr/lib/libmd5.so.1 > libscf.so.1 => /usr/lib/libscf.so.1 > libdoor.so.1 => /usr/lib/libdoor.so.1 > libuutil.so.1 => /usr/lib/libuutil.so.1 > /platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1 > /platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1/ > > This seems to indicate that amandad knows where to find the > libcrypto.so.0.9.7 file, as this IS one of two locations it's located in. > > Is there some syntax I can run on the client manually to test? > > Thanks! > > Neil > > > On 2012.01.12 8:09 AM, Brian Cuttler wrote: > > > >Neil, > > > >I'm a big believer in # ldd as in > > > >ie > ># ldd /usr/local/libexec/amanda/amandad > > > >On Wed, Jan 11, 2012 at 07:37:11PM -0600, Neil Carter wrote: > >>Greetings: > >> > >>I found the article 361http://network.zmanda.com/lore/article.php?id=361 > >>and it > >>seemed to fit perfectly, as I get the same error: > >> > >>Amanda Backup Client Hosts Check > >>-------------------------------- > >>WARNING: horus-iflex: selfcheck request failed: tcpm_recv_token: invalid > >>size: > >>"ld.so.1: amandad: fatal: libcrypto.so.0.9.7: open failed: No such file or > >>directory\n" Client check: 1 host checked in 0.042 seconds. 1 problem > >>found. > >> > >>However, upon checking, it looks like the client DOES have the OpenSSL > >>installed: > >> > >>root@horus-iflex# pkginfo|grep ssl > >>system SUNWopenssl-commands OpenSSL Commands (Usr) > >>system SUNWopenssl-include OpenSSL Header Files > >>system SUNWopenssl-libraries OpenSSL Libraries (Usr) > >>system SUNWopenssl-man OpenSSL Manual Pages > >>system SUNWopensslr OpenSSL (Root) > >>root@horus-iflex# > >> > >>Yes, this is a Sun SPARC client, Solaris 10. The Amanda server is on > >>Linux, > >>and > >>it's Amanda 3.3.0. > >> > >>The libcrypto.so.0.9.7 file DOES exist on the server in two separate > >>locations. Can someone tell me where amanda wants to find it? > >> > >>Am I reading this wrong? Any other suggestions? > >> > >>Thanks! > >> > >>Neil > >> > >--- > > Brian R Cuttler brian.cutt...@wadsworth.org > > Computer Systems Support (v) 518 486-1697 > > Wadsworth Center (f) 518 473-6384 > > NYS Department of Health Help Desk 518 473-0773 > > > > > > > >IMPORTANT NOTICE: This e-mail and any attachments may contain > >confidential or sensitive information which is, or may be, legally > >privileged or otherwise protected by law from further disclosure. It > >is intended only for the addressee. If you received this in error or > >from someone who was not authorized to send it to you, please do not > >distribute, copy or use it or any attachments. Please notify the > >sender immediately by reply e-mail and delete this from your > >system. Thank you for your cooperation. > > > > > > --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
