TSchmauch Absent Member.
Absent Member.
757 views

IDM engine and java issue

I have an environment setup with RHEL 7.4, eDir 9.1.1, IDM 4.7.1. On the linux side I am unable to get drivers to run. After doing some digging, I went to ndstrace and manually unloaded and loaded vrdim. The result of this is the following output:


jar:/opt/novell/eDirectory/lib64/nds-modules/jre/lib//plugin.jar:/opt/novell/eDi
rectory/lib64/nds-modules/jre/lib//resources.jar:/opt/novell/eDirectory/lib64/nd
s-modules/jre/lib//rt.jar
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Dfile.encoding=UTF-8
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Dsun.jnu.encoding=UTF-8

2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Djava.ext.dirs=/opt/nov
ell/eDirectory/lib64/nds-modules/jre/lib/ext
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Djava.endorsed.dirs=/op
t/novell/eDirectory/lib64/nds-modules/jre/lib/endorsed
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Xverify:none
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: exit
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: extra info = 0x7
f93844e8eed
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Xmx512M
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: -Xms128M
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: dlopen() error: libjvm.so: c
annot open shared object file: No such file or directory
2214926080 MISC: [2018/09/05 11:46:43.879] jvmload: No JVM module found
2214926080 DVRS: [2018/09/05 11:46:43.879] DirXML JVM interface initialization f
ailed <failed, -299 (0xfffffed5)>, unloading DIRXML
2214926080 DVRS: [2018/09/05 11:46:43.879] DirXML shutting down.


Does anyone have any suggestions for what else I can try to pinpoint this error? I found a few tid's with similar errors, but most are from IDM 3.x and 4.0. I did verify that the file being referenced does exist. This is a root install.
Thanks
Tom
Labels (1)
0 Likes
9 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: IDM engine and java issue

Do you have libjv.so somewhere under /opt/novell/eDirectory?


find /opt/novell/eDirectory -name 'libjvm.so*'


Specifically I would expect it to be present at
/opt/novell/eDirectory/lib64/nds-modules/embox/jre/lib/amd64/server/libjvm.so
(via symlink at the 'jvm' level). You may also get a hit for the
real-jvm-directory version of the path, but I believe the system looks for
it via that symlink so that Java version changes are easier to handle.

--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
TSchmauch Absent Member.
Absent Member.

Re: IDM engine and java issue

I found it under here:
/opt/netiq/common/jre/lib/amd64/server/libjvm.so
, however I do not see anywhere in an eDirectory subdirectory. Do i just need to create a symlink for it under the modules. Do i just create the symlink for it under /opt/novell/eDirectory/lib64/nds-modules? I see symlinks for libjvmload.la libjvmload.so libjvmload.so.3 libjvmload.so.3.0.700.

FYI, I am seeing this on multiple servers built the same way, so I am guessing I ran across a bug.

Thanks again for your help,
Tom
0 Likes
TSchmauch Absent Member.
Absent Member.

Re: IDM engine and java issue

For some reason it put https://novell.com in the path. I tried changing it like 10 times... lol
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: IDM engine and java issue

Try this just for fun, though to be fair I do not have a 4.7 environment
to use for comparison:


ln -s /opt/netiq/common/jre /opt/novell/eDirectory/lib64/nds-modules/


Also the previous path I posted was wrong, as that was for embox, so boo
to me. The correct path was more like
/opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
though again for an older install of IDM.

As a bit of background, NetIQ/Micro Focus moved to consolidate JREs
because everything had its own and that was a pain, so the idea now is to
have one common JRE for everything on a box that ships from Micro Focus.
Hooray! It seems like the system may just need to know how to point to
that, which is what I hope the symlink above does, though then the
question of "Why is that not already there in your system?" remains, but
let's get there after we test this.

--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Highlighted
TSchmauch Absent Member.
Absent Member.

Re: IDM engine and java issue

The path you mentioned seems like the correct place. Under there i have a broken symlink for libjvm.so --> libjvm.so

lrwxrwxrwx. 1 root root 9 Sep 5 13:41 libjvm.so -> libjvm.so

I found the file
opt/netiq/common/i686/jre/lib/i386/server/libjvm.so


I am wondering if i should modify the symlink to point there and see what happens. Unless you have another idea?

Thanks
Tom
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: IDM engine and java issue

Sure, if you found a broken symlink then fix it. It is a little
surprising that is how it would be done anyway, but let's try it.


--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
TSchmauch Absent Member.
Absent Member.

Re: IDM engine and java issue

Baby steps, but I'm starting to get there...so I did this since this was the only copy of libjvm.so i could find on either server. The second one made the error change.
ln -s /opt/netiq/common/openssl/i686/jre/lib/i386/server/libjvm.so /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
ln -s /opt/netiq/common/openssl/i686/jre/lib/i386/server/libjvm.so /opt/novell/eDirectory/lib64/nds-modules/libjvm.so


3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: -Djava.endorsed.dirs=/op
t/novell/eDirectory/lib64/nds-modules/jre/lib/endorsed
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: -Xverify:none
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: exit
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: extra info = 0x7
fefeb48deed
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: -Xmx512M
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: -Xms128M
3685971712 MISC: [2018/09/05 15:23:41.673] jvmload: dlopen() error: //opt/novell
/eDirectory/lib64/nds-modules/libjvm.so: file too short

File too short which i assume means this isn't the right version of the file...but where do i find the correct version. Any suggestions? I guess i can bring up a VM and try doing a clean install on SLES and see if the file shows up somewhere else?

Thanks
Tom
0 Likes
TSchmauch Absent Member.
Absent Member.

Re: IDM engine and java issue

Got it working! If anyone else runs into this, here is what I had to do. I've only see this file missing on RHEL.
1) Install IDM 4.7 on SLES....you don't have to configure it, just copy off /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
2) Copy the file to the RHEL server to here:
/opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
3) Create a symlink for eDir:
ln -s /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so /opt/novell/eDirectory/lib64/nds-modules/libjvm.so
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: IDM engine and java issue

On 09/05/2018 04:54 PM, TSchmauch wrote:
>
> Got it working! If anyone else runs into this, here is what I had to
> do. I've only see this file missing on RHEL.
> 1) Install IDM 4.7 on SLES....you don't have to configure it, just copy
> off
> /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
> 2) Copy the file to the RHEL server to here:
> /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
> 3) Create a symlink for eDir:
> ln -s
> /opt/novell/eDirectory/lib64/nds-modules/jre/lib/amd64/server/libjvm.so
> /opt/novell/eDirectory/lib64/nds-modules/libjvm.so


Thanks fro sharing what you found that worked.

Out of curiosity, how did this box get into this state? I assumed,
previously, that this was a fresh install of everything, but perhaps that
is incorrect. The more details the better, especially if you have other
boxes that do work.

The RPM which installs the JRE link to the engine (which used to install
the JRE itself back before the shared one came to be) is coded to create a
symlink in the way I described above:


###############################################################
#invoke the JRE installation
echo Installing the Java Virtual Machine "(JVM)"...
curdir=`pwd`
cd $BASEDIR/lib64/nds-modules

if [ "$osname" = "Linux" ]
then
arch=`uname -i`
if [ "lib64" = "lib" ]
then
arch=i386
fi
if [ "$arch" = "i386" ]
then
ln -sf /opt/netiq/common/i686/jre jre
else
ln -sf /opt/netiq/common/jre jre
fi
fi



The result is that you SHOULD be able to simply have the 'jre' symlink
point as shown above. As you can see, you need the eDirectory
architecture to match that of the system, but that is probably because the
install assumes that the eDirectory install matches that of the host OS,
which is guaranteed since eDirectory 9.1 is x86_64 only and x86_64 will
not work on x86_32.

Still, if you already have a JRE directory in place then the symlink
creation will likely fail, leaving you with a less-than-fully-installed
engine. I wonder if that was possibly what happened, if this particular
install was upgraded in some way from an earlier version of IDM. It's
just a theory, but nothing else makes much sense to me, including the
workaround.

--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
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.