I'm guessing you are hitting a new bug, specifically Bug# 1038018, and I
only believe so because I've been poking at it the past two evenings for
many hours in order to find the best way to fix it.

First, any reason you are not trying 9.0 SP3 rather than SP2? SP2 had a
few not-so-fun bugs necessitating the hotfixes you may have seen out
there, and SP3 is better, though it has the same issue, if you're seeing
what I think you are.

In summary, directories like /opt/novell and /etc/opt/novell may already
be owned by another package, for example novell-zenworks-ruby (ZCM Agent
for Linux). If so, then the novell-NDSbase package chokes and says, "Oh
no, already owned by something else" and stops the install. If you do
have these directories already, you can see what owns them (if not others)
with the following command:

rpm -qf /opt/novell
rpm -qf /etc/opt/novell

If you want to find out which directories are conflicting, you can run the
following BEFORE you do the install shown after that:

rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm

Please share the output as I'm curious what other packages may interfere
with eDirectory's install. If not zenworks something-or-another, please
share the permissions and ownership of the relevant files/directory as
shown below, but with whatever paths are applicable to you:

ls -ld /opt/novell

I know I am asking for a lot, and I hope you can provide the output from
the stuff above as it may help verify this big is squashed once and for all.

The fix is easy: install eDirctory before whatever else. Alternatively,
you can modify nds-install so that it moves past this particular error.
make a backup of nds-install if you want and then modify line 3559 in it
so that the following:

if ! rpm -Uvh --nodeps  $NOSCRIPTS --dbpath $NDSHOME/var/lib/rpm
$rpmforce $1 >> $log_file 2>

On 5/10/2017 14:12, ab wrote:
> I'm guessing you are hitting a new bug, specifically Bug# 1038018, and I
> only believe so because I've been poking at it the past two evenings for
> many hours in order to find the best way to fix it.
>
> First, any reason you are not trying 9.0 SP3 rather than SP2? SP2 had a
> few not-so-fun bugs necessitating the hotfixes you may have seen out
> there, and SP3 is better, though it has the same issue, if you're seeing
> what I think you are.
>
I missed seeing that release. I'll switch to 9.03.


> In summary, directories like /opt/novell and /etc/opt/novell may already
> be owned by another package, for example novell-zenworks-ruby (ZCM Agent
> for Linux). If so, then the novell-NDSbase package chokes and says, "Oh
> no, already owned by something else" and stops the install. If you do
> have these directories already, you can see what owns them (if not others)
> with the following command:

> rpm -qf /opt/novell
"file /opt/novell is not owned by any package".

> rpm -qf /etc/opt/novell
"error: file /etc/opt/novell: no such file or directory".

> If you want to find out which directories are conflicting, you can run the
> following BEFORE you do the install shown after that:
>
>

> rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm
> 

>

Bingo!
"file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-NOVLjvmlx-4.5.0-0.x86_64
file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-DXMLbasex-4.5.0-0.x86_64
file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-DXMLengnx-4.5.0-0.x86_64"

Apparently there was an attempt to install IDM 4.5 on this system too.

Instead of the workaround you detailed below, could/should I simply
uninstall the conflicting RPMs (or every RPM that begins with "novell")
and start over?



Thanks









> Please share the output as I'm curious what other packages may interfere
> with eDirectory's install. If not zenworks something-or-another, please
> share the permissions and ownership of the relevant files/directory as
> shown below, but with whatever paths are applicable to you:
>
>

> ls -ld /opt/novell
> 

>
> I know I am asking for a lot, and I hope you can provide the output from
> the stuff above as it may help verify this big is squashed once and for all.
>
> The fix is easy: install eDirctory before whatever else. Alternatively,
> you can modify nds-install so that it moves past this particular error.
> make a backup of nds-install if you want and then modify line 3559 in it
> so that the following:
>
>

>     if ! rpm -Uvh --nodeps  $NOSCRIPTS --dbpath $NDSHOME/var/lib/rpm
> $rpmforce $1 >> $log_file 2>

Black, Douglas wrote:

> Apparently there was an attempt to install IDM 4.5 on this system too.
>
> Instead of the workaround you detailed below, could/should I simply uninstall
> the conflicting RPMs (or every RPM that begins with "novell") and start over?

IDM 4.5 and Edir 9.0x only work together in certain versions and updating from
Edir 8.8.x to 9.0x with IDM installed requires updating to IDM 4.5.4 first.
Make sure to read the upgrade notes for both products if you want to run IDM
with Edir 9.

If you do not need IDM, uninstall IDM first, then install/upgrade Edir 9

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)

On 05/11/2017 07:00 AM, Black, Douglas wrote:
> On 5/10/2017 14:12, ab wrote:
>> If you want to find out which directories are conflicting, you can run the
>> following BEFORE you do the install shown after that:
>>
>>

>> rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm
>> 

>>
>
> Bingo!
> "file /opt/novell/eDirectory/lib64 from install of
> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
> novell-NOVLjvmlx-4.5.0-0.x86_64
> file /opt/novell/eDirectory/lib64 from install of
> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
> novell-DXMLbasex-4.5.0-0.x86_64
> file /opt/novell/eDirectory/lib64 from install of
> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
> novell-DXMLengnx-4.5.0-0.x86_64"
>
> Apparently there was an attempt to install IDM 4.5 on this system too.
>
> Instead of the workaround you detailed below, could/should I simply
> uninstall the conflicting RPMs (or every RPM that begins with "novell")
> and start over?

Yes, please remove at least those that are causing conflicts and I think
you'll be fine. I suspect that they are probably doing more-normal
default ownership of 'root:root' for those directories, and eDirectory is
probably doing 'root:sys', and if so then fixing the eDirectory side may
eventually avoid these conflicts. In the meantime, removing these RPMs
that you cannot have with eDirectory 9.x anyway is the best course.

rpm -e novell-NOVLjvmlx novell-DXMLbasex novell-DXMLengnx

I just checked a system of mine with eDir 8.x and IDM 4.x and found the
following conflicts which all seem to support the theory that eDir stuff
uses root:sys for ownership (not verified, but likely) and IDM (and Zen)
are using root:root.

root@mybox0:~# for i in $(rpm -qf /opt/novell/eDirectory/lib64); do echo
${i} ; rpm -Vv ${i} | grep '\.G\.'; done
novell-NDSbase-8.8.8.8-0
novell-DXMLbasex-4.0.2-0
.......G.    /opt/novell/eDirectory/lib64
novell-DXMLeventx-4.0.2-7
.......G.    /opt/novell/eDirectory/lib64
.......G.    /opt/novell/eDirectory/lib64/nds-modules
NOVLdump-8.8-1
novell-edirectory-expat-8.8.8-1
novell-NDSimon-8.8.8.8-0
novell-AUDTedirinst-8.8.8.8-53
novell-NOVLsnmp-8.8.8.8-0
novell-edirectory-xdaslog-8.8.8.8-0
novell-ncpenc-1.2.2.0-9
novell-edirectory-jclnt-8.8.8.8-0
novell-DXMLengnx-4.0.2-7
.......G.    /opt/novell/eDirectory/lib64
.......G.    /opt/novell/eDirectory/lib64/nds-modules
novell-NOVLjvmlx-4.0.2-3
.......G.    /opt/novell/eDirectory/lib64
.......G.    /opt/novell/eDirectory/lib64/nds-modules
novell-edirectory-xdasinstrument-8.8.8.8-0

Thank-you for posting back your progress; I am excited to hear the results.

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

On 5/11/2017 10:16, ab wrote:

>>> If you want to find out which directories are conflicting, you can run the
>>> following BEFORE you do the install shown after that:
>>>
>>>

>>> rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm
>>> 

>>>
>>
>> Bingo!
>> "file /opt/novell/eDirectory/lib64 from install of
>> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
>> novell-NOVLjvmlx-4.5.0-0.x86_64
>> file /opt/novell/eDirectory/lib64 from install of
>> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
>> novell-DXMLbasex-4.5.0-0.x86_64
>> file /opt/novell/eDirectory/lib64 from install of
>> novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
>> novell-DXMLengnx-4.5.0-0.x86_64"
>>
>> Apparently there was an attempt to install IDM 4.5 on this system too.
>>
>> Instead of the workaround you detailed below, could/should I simply
>> uninstall the conflicting RPMs (or every RPM that begins with "novell")
>> and start over?
>
> Yes, please remove at least those that are causing conflicts and I think
> you'll be fine. I suspect that they are probably doing more-normal
> default ownership of 'root:root' for those directories, and eDirectory is
> probably doing 'root:sys', and if so then fixing the eDirectory side may
> eventually avoid these conflicts. In the meantime, removing these RPMs
> that you cannot have with eDirectory 9.x anyway is the best course.
>
>

> rpm -e novell-NOVLjvmlx novell-DXMLbasex novell-DXMLengnx
> 

>
> I just checked a system of mine with eDir 8.x and IDM 4.x and found the
> following conflicts which all seem to support the theory that eDir stuff
> uses root:sys for ownership (not verified, but likely) and IDM (and Zen)
> are using root:root.
>
>

> root@mybox0:~# for i in $(rpm -qf /opt/novell/eDirectory/lib64); do echo
> ${i} ; rpm -Vv ${i} | grep '\.G\.'; done
> novell-NDSbase-8.8.8.8-0
> novell-DXMLbasex-4.0.2-0
> ......G.    /opt/novell/eDirectory/lib64
> novell-DXMLeventx-4.0.2-7
> ......G.    /opt/novell/eDirectory/lib64
> ......G.    /opt/novell/eDirectory/lib64/nds-modules
> NOVLdump-8.8-1
> novell-edirectory-expat-8.8.8-1
> novell-NDSimon-8.8.8.8-0
> novell-AUDTedirinst-8.8.8.8-53
> novell-NOVLsnmp-8.8.8.8-0
> novell-edirectory-xdaslog-8.8.8.8-0
> novell-ncpenc-1.2.2.0-9
> novell-edirectory-jclnt-8.8.8.8-0
> novell-DXMLengnx-4.0.2-7
> ......G.    /opt/novell/eDirectory/lib64
> ......G.    /opt/novell/eDirectory/lib64/nds-modules
> novell-NOVLjvmlx-4.0.2-3
> ......G.    /opt/novell/eDirectory/lib64
> ......G.    /opt/novell/eDirectory/lib64/nds-modules
> novell-edirectory-xdasinstrument-8.8.8.8-0
> 

>
> Thank-you for posting back your progress; I am excited to hear the results.
>


I issued an "rpm -e" against all packages beginning with 'novl', and
eDirectory 9.03 installed without any issues. I will now continue with
installing iManager and IDM 4.5.

Thanks for all your help.

Perfect; thank-you as well for reading through all of that mindless drivel
of mine and still coming back for more. In the end, this has been very
helpful for my understanding of the root cause and best solution too.

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

ab,

> Perfect; thank-you as well for reading through all of that mindless drivel
> of mine and still coming back for more. In the end, this has been very
> helpful for my understanding of the root cause and best solution too.
>

A win/win!


I did have two minor issues configuring eDirectory after installation
that I managed to resolve myself. I'll document them for the benefit of
anyone else who's reading all this.

1. The command 'ndsconfig' errored out, saying that the library file
libccs2.so was not found. Searching for that file, I found a symlink
under /usr/lib64 that pointed to /opt/novell/lib64/libccs2.so, but the
target file was not present in that folder. I copied libccs2.so from
the install media to /opt/novell/lib64 and it no longer gave that error,
but...

2. The command 'ndsconfig' now errored out with an Error -1471. The fix
for that was even easier: I followed TID 7011966 to force NICI to
update from the install media: rpm -Uvh --nodeps <nici rpm>

Onward!

even the post is old I got same problem 86bit version installed with edir 9.2 on sles 15. But came not forward, until I had the idea to look in the uninstall script where it checkes for 64bit. I found it checks just for one file in the lib64 directory. I created the path /opt/novell/eDirectory/lib64 ad the file touch libsal.so within and the uninstall runs fine.

Rainer