Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Jeff-seattle
New Member.
224 views

IDM v4.72 non-root won't start

I am having some issues getting a non-root v4.72 on top of a non-root eDirectory tarball to start under Rhel7. v7.6.

I get no errors on either the eDirectory config, or the IDM non-root install. I install from v4.7 ISO first using the non-root script, then I ran the v4.72 patch.

On 1 iteration I install the netiq-jrex rpm as root, but was pretty sure that was fixed on the v.4.72 patch.

Anyway vrdim will just not load.
load vrdim: vrdim module could not be loaded: (-5984)

I also seem to be missing a library.
Loader Failed:for /apps/eDirectory/opt/novell/eDirectory/lib64/nds-modules/libvrdim.so,error libIDMCEFProcessor.so: cannot open shared object file: No such file or directory,errno 0

As this shows in ndsd.log when trying to load vrdrim from ndstrace. I do not have libIDMCEFProcessor.so, and I cant find any information on that.

I have a ticket in, but no luck so far. I am about to give up on this. We are required to run both of these as non-root now. So not what will happen if cant.

We have the Advanced license, so I chose advanced. I know that used to break non-root if you didn't have the naudit rpm installed. But I think was fixed in some previous v4.6x. I have not install that platform agent as root, because we do not run it.

Thank you any direction you may have.
Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: IDM v4.72 non-root won't start

First, if your requirement is to run as non-root, then do that, but that's
a non-root instance, not a non-root install. You should use the root
install (RPM-based) for eDir and IDM, then configure a non-root instance
(as any old user) to run eDirectory, etc. The way you are doing it,
perhaps motivated by a desire for more security because "non-root" is
often equated with better security (when it means a non-root process),
actually decreases security because the running instance, though owned by
a non-root user perhaps, is also probably the user-owner of the files and
directories extracted from the tarball, meaning the process can modify
them, which it would not be able to do if using a non-root instance and a
root install.

Otherwise, I'd check your 'env' file under /etc/opt/novell/eDiretcory/conf
to be sure it is there, and an env-idm probably too, setting up paths for
you. The CEF library probably comes from a similarly-named RPM as part of
eDirectory, but that's a guess I have not verified.

--
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
Jeff-seattle
New Member.

Re: IDM v4.72 non-root won't start

Thank you. I have gone down the road with a root eDirectory install and a non-root eDirectory instance. And then a non-root IDM install. The non-root IDM install is not supported, and even support told me that when we had issues. They cleary stated to us a A root install of eDirectory requires a root install of IDM. No matter if the eDirectory instance is root or non-root.
0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM v4.72 non-root won't start

On 04/22/2019 12:44 PM, mtsjej wrote:
>
> Thank you. I have gone down the road with a root eDirectory install and
> a non-root eDirectory instance. And then a non-root IDM install. The
> non-root IDM install is not supported, and even support told me that
> when we had issues. They cleary stated to us a A root install of
> eDirectory requires a root install of IDM. No matter if the eDirectory
> instance is root or non-root.


Yes, that's true; a root install of eDirectory requires a root install of
IDM, but then you can still run a non-root instance of eDirectory within
that root install. The installs are matched up, RPMs for eDir and IDM
(for root installs), but there is no hard and fast link between types of
installs and types of instances, so you could potentially have a non-root
install and a root instance (though I have no idea why that would be
attempted) or, as I'm suggesting, a root install and a non-root instance.

--
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
Jeff-seattle
New Member.

Re: IDM v4.72 non-root won't start

Hi. I am not sure I tried that way. I will try for sure today. We get some different answers from support a lot. Lots of confusion on types of non-root. Thanks,,,
0 Likes
Jeff-seattle
New Member.

Re: IDM v4.72 non-root won't start

And also this is the other mess you get when you try the approach that you said. Root eDirectory binary install, non-root config. Root IDM install. The IDM schema doesn't get extended and when you try to run the IDM install script manually (idm-install-schema) you get this error.
/idm-install-schema
This script only works with eDirectory 8.8 and above.

Of course we are at v9.13
Binary Version: 40104.06
Root Most Entry Depth: 0
Product Version: eDirectory for Linux x86_64 v9.1.3 [DS]

Maybe Im the only who ever runs into issues with this, but it seems Root installs with eDir/IDM are really the only combination ever addressed or tested. Which is a shame, at some point the group I am attempting to help are going to switch products when we cant get this working.
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.