bobbintb Absent Member.
Absent Member.
462 views

error while loading shared libraries: libxi18n.so


I am trying to install IDM 4.5 using the stand alone method. I am doing
eDirectory 8.8 sp8 non-root RHEL and when trying to add a new tree I am
getting the following message:


Code:
--------------------
./ndsconfig: error while loading shared libraries: libxi18n.so: cannot open shared object file: No such file or directory
--------------------


I have installed the nici-2.7.7-0.02.i586, nici64-2.7.7-0.02.x86_64, and
novell-NOVLsubag-8.8.8-1.x86_64 packages. I'm not sure what I am
overlooking. Any ideas?


--
bobbintb
------------------------------------------------------------------------
bobbintb's Profile: https://forums.netiq.com/member.php?userid=5629
View this thread: https://forums.netiq.com/showthread.php?t=56011

Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: error while loading shared libraries: libxi18n.so

That shared library comes from the following package on the latest patch
of eDirectory (note: you should be trying Patch 7, not just 8.8 SP8
without patches):

novell-NOVLlmgnt-8.8.8.7-0

If the non-root installation does not have you install this RPM, then you
probably need to set your LD_LIBRARY_PATH environment variable to whatever
location the non-root installation puts a file starting with libx18n.so,
such as ./opt/novell/eDirectory/lib64, then try again. To do this
automatically, source the 'ndspath' command.

With that written, is there a reason you are using the non-root
installation of eDirectory? The root install is much easier, and if you
are security-conscious (as you should be) you can run non-root instances
within a root installation by running the various commands to manage
instances as some non-root user, which gives you the benefits of the
more-secure runtime (non-root) and also, in my opinion, better security by
running as a user that does NOT own the binaries, meaning a compromised
runtim cannot, as easily, become a persistent compromise across service
restarts. Also, of course, the root-based installation is easier to
install, works with more pieces of software, is much easier to patch, can
be managed by more common OS tools (RPM-managing software), etc.

--
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
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.