SuSE Linux 9 SP3 - LDAP - SMH not getting started while server boot

[Dreams_unlimited]

Hi All,

I am new to this fourm

I have one issue regarding SLES 9 SP3 - LDAP - HP system management homepage 2.1.5-146

cu has updated the PSP 7.52 on DL740 server & now the hpsmh is not getting started it is giving the error massage in /var/spool/opt/hp/hpsmh/logs/error_log:
hpsmhd: cyrus.c:439: ldap_int_sasl_open: Assertion `lc->lconn_sasl_ctx == ((void *)0)' failed.

We discovered that hpsmh can't be started using '/etc/init.d/hpsmhd
start' if nscd is not running. Unfortunately hpsmhd is started just
before nscd during system boot. If we start it manually afterwards (
/etc/init.d/hpsmhd start) all is fine.

This error is seen only if nscd is not running, so it seems to be
somehow related to ldap.

So we dived deeper into it. In our setup we use LDAP to manage users
and groups. If nscd is running, LDAP is handled transparently.
However, if nscd is *not* running, libnss_* is handling LDAP on behalf
of the calling application *inside* the calling application.

We started capturing the packets from the host to our LDAP-servers,
and yes: SSL handschake failed if nscd was not running.

We assume this to be the problem. Running strace, we can observe the
following:

- /opt/hp/hpsmh/sbin/smhstart is called somewhere in the startup of
hpsmh. This binary is linked against it's own set of SSL libraries
(namely libssl.so.0.9.7 ) found in /opt/hp/hpsmh/lib. These
libraries are loaded through ld.so.
- If nscd is not running, /opt/hp/hpsmh/sbin/smhstart loads
libnss_ldap later, which in turn is linked against libldap.so
(system library from /usr/lib) which is finally linked against
/usr/lib/libssl.so.0.9.6. So we end up with two different version of
libssl dynamically loaded into the same process.

The symbol table of the process is obviously garbled afterwards,
finally resulting in SSL errors (maybe due to one libssl calling
functions from the other libssl?).


need help......

[Steven E. Protter]

Shalom,

Welcome to the forums. I think you will find your answer here.

I think you may be able to resolve this by changing the value in LD_LIBARY_PATH in the startup script.

It seems that the utility is getting a different version of openssl that it needs to function properly.

Do also check with HP support and see if this specific OS/software combination is supported. IF not, you may not be able to run this service.

SEP

[Dreams_unlimited]

Thanks for your quick reply

I have checked the support matrix of hp system management homepage & it stats that SLES 9 SP3 + LDAP is supported

could you please tell me what exact changes we have to do in above mention file & where

as i am not expert in linux scripting

[Dreams_unlimited]

there was some issue with LADP setting , customr doe that & issue got resolved.