Honored Contributor.
Honored Contributor.
1556 views

Red Hat Enterprise Linux Server release 7.2

We seem to be having some issues on getting drivers to start on Red Hat Enterprise Linux Server release 7.2.
- IDM SE 4.5.3.0

All our other servers are Red Hat Enterprise Linux Server release 6.7 and the SAME driver seems to run fine on that version.

The error is:

[05/12/16 07:10:46.654]:prt2ext PT:Startup policies completed execution. Starting cache processing.
[05/12/16 07:10:46.655]:prt2ext PT:: Creating an NTLSServerSocket
[05/12/16 07:10:46.655]:prt2ext PT:
DirXML Log Event -------------------
Driver: \SIC-PORTAL\com\SGExt-NWExt\PORTAL2EXTAUTH
Channel: Publisher
Status: Error
Message: Code(-9010) An exception occurred: java.lang.NoClassDefFoundError: Could not initialize class com.novell.nds.ntls.NTLSSocket
at com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:75)
at com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:180)
at com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFactory.createServerSocket(NTLSKmoFactory.java:106)
at com.novell.nds.dirxml.driver.nds.PublicationShimImpl.initListener(PublicationShimImpl.java:253)
at com.novell.nds.dirxml.driver.nds.PublicationShimImpl.start(PublicationShimImpl.java:298)
at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:549)
at java.lang.Thread.run(Thread.java:745)


Any ideas?

Thanks
-jim
Labels (1)
Tags (2)
0 Likes
6 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Red Hat Enterprise Linux Server release 7.2

Missing fundamental classes sounds like the issue covered in the readme in
section 4.4 or 4.5:

https://www.netiq.com/documentation/idm45/idm453-releasenotes/data/idm453-releasenotes.html

Maybe it is different enough that these steps will not help, but I'd
probably start there if you have not already; hopefully all of this will
be fixed in 4.5 SP4, but until then, those steps may help. If they do not
help enough, I'd probably figure out which JAR provides
com.novell.nds.ntls.NTLSSocket and be sure that is either present or
symlinked into a path that is known to hold eDirectory libraries, and of
course which is being read as such by eDirectory. The change to systemd
has led to some odd changes in eDirectory with that env_idm file that can
specify environment information for the ndsd process, and maybe that's
still being ironed out.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Red Hat Enterprise Linux Server release 7.2

Thanks for the input.

We had set the idm_env value as suggested in release notes.

So I find the Jar files that contain the NTLSSocket and then what?

How could I know what "is either present or symlinked into a path that is known to hold eDirectory libraries, and of course which is being read as such by eDirectory." ?

We opened an SR but not got any worthwhile information back yet.

-jim
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Red Hat Enterprise Linux Server release 7.2

On 05/13/2016 09:46 AM, jwilleke wrote:
>
> We had set the idm_env value as suggested in release notes.
>
> So I find the Jar files that contain the NTLSSocket and then what?


I only found one under dirxml/classes (warning: my system is still 4.0
SP2) and it was /opt/novell/eDirectory/lib/dirxml/classes/jntls.jar

> How could I know what "is either present or symlinked into a path that
> is known to hold eDirectory libraries, and of course which is being read
> as such by eDirectory." ?


Once when troubleshooting something similar I started ndsd without IDM
(renamed libvrdim.so.whatever.the.real.file.name.was) so that the symlinks
all broke, and then once eDirectory was up (sans IDM) I renamed the
libvrdim.whatever file back, went into ndstrace, and then loaded 'vrdim'
manually after turning on things like +TIME +TAGS +INIT +DXML because that
was fun. Before doing the load, I connected to ndsd with strace so that I
could watch everywhere it was trying to load JARs. There's probably a way
to get the classpath directly from /proc/$(pgrep ndsd) or something, but I
cannot think of how to do so definitely right now.


strace -ttt -ff -p $(pgrep ndsd) -e file


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Red Hat Enterprise Linux Server release 7.2

I find these two jars:

find / -name "*.jar" -exec grep -Hls "NTLSSocket" {} \;
/opt/novell/eDirectory/lib/dirxml/classes/pwdexpjob.jar
/opt/novell/eDirectory/lib/dirxml/classes/jntls.jar


Which I assume are supplied by these two Packages:
rpm -qa |grep 'ntls'
novell-ntls-8.8.8.7-160111.x86_64
novell-DXMLjntlsx-4.5.3-0.x86_64


An 0035 server - Works
- Red Hat Enterprise Linux Server release 6.7 (Santiago)
- 4.5.2.0
- NetIQ eDirectory Agent Statistics- Diagnostic utility to get NetIQ eDirectory Agent statistics for NetIQ eDirectory 8.8 SP8 v20805.07 (eDirectory 8.8.8 Patch4)
- novell-ntls-8.8.8.3-140901.x86_64
- novell-DXMLjntlsx-4.5.2-0.x86_64


The 0051 server - FAILS
- Red Hat Enterprise Linux Server release 7.2 (Maipo)
- 4.5.3.0
- NetIQ eDirectory Agent Statistics- Diagnostic utility to get NetIQ eDirectory Agent statistics for NetIQ eDirectory 8.8 SP8 v20808.02 (eDirectory 8.8.8 Patch7)
- novell-ntls-8.8.8.7-160111.x86_64
- novell-DXMLjntlsx-4.5.3-0.x86_64

Thanks
-jim
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Red Hat Enterprise Linux Server release 7.2


Once edir is started and IDM loaded use dxcmd -> opt 8 and get the full
jvm stats .. that should show what jars are set under java.class.path





jwilleke;267770 Wrote:
> Thanks for the input.
>
> We had set the idm_env value as suggested in release notes.
>
> So I find the Jar files that contain the NTLSSocket and then what?
>
> How could I know what "is either present or symlinked into a path that
> is known to hold eDirectory libraries, and of course which is being
> read
> as such by eDirectory." ?
>
> We opened an SR but not got any worthwhile information back yet.
>
> -jim
>
>
> --
> jwilleke
> ------------------------------------------------------------------------
> jwilleke's Profile: https://forums.novell.com/member.php?userid=11492
> View this thread: https://forums.novell.com/showthread.php?t=498335



--
vivekbm
------------------------------------------------------------------------
vivekbm's Profile: https://forums.netiq.com/member.php?userid=528
View this thread: https://forums.netiq.com/showthread.php?t=55873

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Red Hat Enterprise Linux Server release 7.2

The dxcmd command also fails.

Enter choice: 8

Select a JVM Stat option

1: All Statistics
2: Memory
3: Thread
4: Runtime
5: Classloader
6: Operation System
7: Garbage Collector
99: Exit

Enter choice: 1
LDAPException: Protocol Error (2) Protocol Error
LDAPException: Server Message: 2 (0x2)
LDAPException: Matched DN:
at com.novell.ldap.LDAPResponse.getResultException(Unknown Source)
at com.novell.ldap.LDAPResponse.chkResultCode(Unknown Source)
at com.novell.ldap.LDAPConnection.chkResultCode(Unknown Source)
at com.novell.ldap.LDAPConnection.extendedOperation(Unknown Source)
at com.novell.ldap.LDAPConnection.extendedOperation(Unknown Source)
at com.novell.nds.dirxml.util.DxCommand.sendLDAPRequest(DxCommand.java:1181)
at com.novell.nds.dirxml.util.DxCommand.getJVMStats(DxCommand.java:2448)
at com.novell.nds.dirxml.util.DxCommand.access$12800(DxCommand.java:56)
at com.novell.nds.dirxml.util.DxCommand$GetJVMStatsHandler.run(DxCommand.java:6230)
at com.novell.nds.dirxml.util.Menu.run(Menu.java:354)
at com.novell.nds.dirxml.util.DxCommand.mainMenu(DxCommand.java:3161)
at com.novell.nds.dirxml.util.DxCommand.commandLine(DxCommand.java:526)
at com.novell.nds.dirxml.util.DxCommand.main(DxCommand.java:476)


But it also fails on our other servers (even those that are working fine?). Not sure what is up with that.

-jim
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.