No difference in the symptoms, even after confirming the path is set, and on a box I haven't tried this yet.

and those ldd commands don't work for me either syntax

ds2:~ # ldd diagpwd
ldd: ./diagpwd: No such file or directory
ds2:~ # ldd ./diagpwd
ldd: ./diagpwd: No such file or directory

ahh, that KB needs updating to include the path.    and both with or without that environment path set, both show
   libnmasext.so => /opt/novell/eDirectory/lib64/libnmasext.so (0x00007f9011a00000)

something else is afoot.

I'll update the KB.  the libnmasext.so; which mistakenly got highlighted during formatting, isn't the issue on OES 23 & 24.  It's the version libldap_r-2.4.so.2 which is placed in /usr/lib64

Adding /opt/novell/eDirectory/eDir-exclusive/lib64 to the LD_LIBRARY_PATH

OES243:/opt/novell/eDirectory/bin # export LD_LIBRARY_PATH=/opt/novell/eDirectory/eDir-exclusive/lib64:$LD_LIBRARY_PATH

changes the output of ldd <path>/diagpwd

from:  libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2

to:  libldap_r-2.4.so.2 => /opt/novell/eDirectory/eDir-exclusive/lib64/libldap_r-2.4.so.2

The core stack for the core I can duplicate shows:

 Stack trace of thread 77892:

                #0  0x00007fafacc5bf22 __pthread_rwlock_wrlock (libpthread.so.0 + 0xff22)

                #1  0x00007fafab6f1149 CRYPTO_THREAD_write_lock (libcrypto.so.1.1 + 0x230149)

                #2  0x00007fafac5adc0c SSL_CTX_flush_sessions (libssl.so.1.1 + 0x4cc0c)

                #3  0x00007fafac5a4183 SSL_CTX_free (libssl.so.1.1 + 0x43183)

                #4  0x00007fafaccc8ec5 ldap_int_tls_destroy (libldap_r-2.4.so.2 + 0x39ec5)

                #5  0x00007fafacd259b3 _dl_fini (ld-linux-x86-64.so.2 + 0x119b3)

                #6  0x00007fafac856bd9 __run_exit_handlers (libc.so.6 + 0x4dbd9)

                #7  0x00007fafac856d6a exit (libc.so.6 + 0x4dd6a)

                #8  0x00007fafac83e254 __libc_start_main (libc.so.6 + 0x35254)

                #9  0x0000000000401d2a _start (diagpwd + 0x1d2a)

If you stack trace is different, please post it for me to review.

Core traces are a bit beyond me at this time without more detailed instructions. I am so not a dev guy.

The cores are just over a quarter Megabyte in size, so should easily be able to post the most recent one and the matching PuTTY log to the case (02974596).

One thing that is catching my eye in the strace, a bunch of (No such file or directory) referencing /opt/novell/eDirectory/eDir-exclusive/lib64/tls/  which doesn't exist.

and I see a typo in today's exports,  a double colon.   fixing that has it working now
if export is the correct syntax, that would be a good addition to the KB article.

as well as some consistency on which certs to use.  Local server cert vs CA's public, and pem vs der

I am getting in with the local server cert to talk to itself.

Please check a small addition for validity.. In the field I always have the issue that /etc/ssl/servercerts/ the certifcates have a problem for whatever reason. Please include in the KM to check the certificates with openssl that are in the path and also to check the certificates in the /kmocache directory before starting the diagnosis.

Thanks

George

. /opt/novell/eDirectory/bin/ndspath

modify LD_LIBRARY_PATH variable :

LD_LIBRARY_PATH=/opt/novell/eDirectory/eDir-exclusive/lib64:/opt/novell/eDirectory/lib64:/opt/novell/eDirectory/lib64/nds-modules:/opt/novell/lib64:$LD_LIBRARY_PATH

cd /opt/novell/eDirectory/bin
./diagpwd ...

If I have understood the ndspath script correctly, it is determined at the beginning whether it is a 32 bit or 64 bit operating system. Depending on the version, a libdir path is defined (example linux.mak)

With the help of awk an export for the ndspath is provided from the result of the check. If I understand this correctly, an export for the corresponding path is then created below for each operating system. With the specification from above to change the path is rewritten by hand. Do I understand something wrong? Have any effects been observed?

from the script: if [ $OS = “Linux” ] ; then

        export LD_LIBRARY_PATH=$base_dir/opt/novell/eDirectory/lib64:$base_dir/opt/novell/eDirectory/lib64/nds-modules:$base_dir/opt/novell/

lib64:$LD_LIBRARY_PATH.

Now I'm not sure if this is dynamically rewritten after each patch or if the export is a static thing after the first installation of eDir.

the exact export path results from uname, ndsconifg and ndspath and .mak

My recommendation here is to open a call in conjunction with the experiences you have made in your post. This is the only way to ensure that no side effects occur. It was clear from the beginning after the strace where the rabbit runs.


George

This article has the answer after some clarifications. The most important bit is the export command, i.e.

#  export LD_LIBRARY_PATH=/opt/novell/eDirectory/eDir-exclusive/lib64:/opt/novell/eDirectory/lib64:/opt/novell/eDirectory/lib64/nds-modules:/opt/novell/lib64:$LD_LIBRARY_PATH

as without that export, it doesn't do anything for diagpwd.  A little step that is likely obvious to the dev types, but not to the rest of us who didn't go that path in IT.