topic Shared Library Error in Operating System - HP-UX

Shared Library Error

Ian Foster_2 — Mon, 17 Jul 2006 09:31:05 GMT

Anybody come across this at login before (HP-UX 11.23 - just as a connection to the server is established):

/usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage:
/usr/lib/libpthread.1
/usr/lib/dld.sl: Exec format error

Just seems to have started happening since I implemented CIFS with Kerberos client, LDAP-UX and ADS support; though I can't think for the life of me what I have installed or configured which may have resulted in this error ?

Re: Shared Library Error

Kent Ostby — Mon, 17 Jul 2006 09:48:06 GMT

Sometimes a reboot will fix this.

I have also seen an issue like this if its an FTP type of login and you have Kerberos on one side, but not the other.

Re: Shared Library Error

Ian Foster_2 — Mon, 17 Jul 2006 10:21:30 GMT

Hi. The problem would appear to persist across reboots. Anybody have any other ideas ?

Re: Shared Library Error

Arunvijai_4 — Mon, 17 Jul 2006 10:47:18 GMT

Hi Ian,

Check for the latest patch updates in ITRC patch database.

a) pthread
b) Dynamic loader
c) Kerberos and CIFS

-Arun

Re: Shared Library Error

Steven E. Protter — Mon, 17 Jul 2006 11:27:40 GMT

Shalom,

I agree with the patch strategy. The June 2006 or March 2006 patch set, whichever it is thats current will work toward fixing this problem.

This is a problem that is typical of the configuration. You should be able to give the error message to HP under a support contract and get the exact patch you need if you want to hurry things along.

Have you checked all the relavent log files for other possible issues?

SEP

Re: Shared Library Error

Ian Foster_2 — Tue, 18 Jul 2006 09:25:10 GMT

Thanks for the responses guys. FYI I think I have identified the cause. I implemented an /etc/nsswitch.conf file on the systems for winbindd as part of the CIFS implementation (it bleats and won't start if it doesn't exist). I had it configured with hosts: files dns wins

Removing the pointer to wins seems to have got rid of the error message and everything else still seems to work ok. Needless to say we are still going to follow up on the patching strategy (we are due to do this as a matter of routine anyway).