pabloecipi
New Member.
1655 views

namdiagtool lum conflicts gid

I have problem with the LUM. Namdiagtool reports conflict of gid. I add the result

##########################################################################
Full Mode
This mode reports conflicts for the entire tree
##########################################################################
############################################
conflict report for wks: cn=UNIX Workstation - ecipi,o=ecipi
--------------------------------------------------------------------
gid YU has conflicts
fdn: cn=www,o=ecipi .
fdn: cn=novlxtier,o=ecipi .
fdn: cn=admingroup,o=ecipi .
############################################
conflict report for wks: cn=UNIX Workstation - lnxecipi3,o=ecipi
--------------------------------------------------------------------
gid YU has conflicts
fdn: cn=www,o=ecipi .
fdn: cn=novlxtier,o=ecipi .
fdn: cn=admingroup,o=ecipi .
############################################
conflict report for wks: cn=UNIX Workstation - oes1,o=ecipi
--------------------------------------------------------------------
gid T has conflicts
fdn: cn=www,o=ecipi .
fdn: cn=novlxtier,o=ecipi .
fdn: cn=admingroup,o=ecipi .
##########################################################################
##########################################################################
Full Mode
This mode reports conflicts for the entire tree
##########################################################################

####################################
Working on unix config object: cn=UNIX CONFIG,o=ecipi
Uco range for cn=UNIX CONFIG,o=ecipi
uidstartid: 0 uidendid: 65535
gidstartid: 0 gidendid: 65535
Wkslist:
####################
Checking for wks cn=UNIX Workstation - ecipi,o=ecipi

Groups:
cn=www,o=ecipi, cn=novlxtier,o=ecipi, cn=admingroup,o=ecipi, .

-------------------------------------------------------------------------------------------------------
Inserting Groups :
cptr: www
name_hash_index is 1
www, adding new hashentry

name_hash_index is 104
YU, adding new hashentry

cptr: novlxtier
name_hash_index is 106
novlxtier, adding new hashentry

name_hash_index is 104
hashentry: YU already exists
comparing cn=www,o=ecipi and cn=novlxtier,o=ecipi
conflict here !
cptr: admingroup
name_hash_index is 8
admingroup, adding new hashentry

name_hash_index is 104
hashentry: YU already exists
comparing cn=www,o=ecipi and cn=admingroup,o=ecipi
comparing cn=novlxtier,o=ecipi and cn=admingroup,o=ecipi
conflict here !



Checking for wks cn=UNIX Workstation - lnxecipi3,o=ecipi

Groups:
cn=www,o=ecipi, cn=novlxtier,o=ecipi, cn=admingroup,o=ecipi, .

Inserting Groups :
cptr: www
name_hash_index is 1
www, adding new hashentry

name_hash_index is 104
YU, adding new hashentry

cptr: novlxtier
name_hash_index is 106
novlxtier, adding new hashentry

name_hash_index is 104
hashentry: YU already exists
comparing cn=www,o=ecipi and cn=novlxtier,o=ecipi
conflict here !
cptr: admingroup
name_hash_index is 8
admingroup, adding new hashentry

name_hash_index is 104
hashentry: YU already exists
comparing cn=www,o=ecipi and cn=admingroup,o=ecipi
comparing cn=novlxtier,o=ecipi and cn=admingroup,o=ecipi
conflict here !

-------------------------------------------------------------------------------------------------------
Inserting users :
----------------------------------------------------------
Users in group cn=www,o=ecipi
----------------------------------------------------------
----------------------------------------------------------
Users in group cn=novlxtier,o=ecipi
----------------------------------------------------------
----------------------------------------------------------
Users in group cn=admingroup,o=ecipi
----------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Checking for Group conflicts now
--------------------------------------------------------------------
cn: www has no conflicts
--------------------------------------------------------------------
cn: admingroup has no conflicts
--------------------------------------------------------------------
cn: novlxtier has no conflicts
Checking for user conflicts now
Checking for uid conflicts now
Checking for gid conflicts now
####################
Checking for wks cn=UNIX Workstation - oes1,o=ecipi

Groups:
cn=www,o=ecipi, cn=novlxtier,o=ecipi, cn=admingroup,o=ecipi, .

-------------------------------------------------------------------------------------------------------
Inserting Groups :
cptr: www
name_hash_index is 1
www, adding new hashentry

name_hash_index is 74
T, adding new hashentry

cptr: novlxtier
name_hash_index is 106
novlxtier, adding new hashentry

name_hash_index is 74
hashentry: T already exists
comparing cn=www,o=ecipi and cn=novlxtier,o=ecipi
conflict here !
cptr: admingroup
name_hash_index is 8
admingroup, adding new hashentry

name_hash_index is 74
hashentry: T already exists
comparing cn=www,o=ecipi and cn=admingroup,o=ecipi
comparing cn=novlxtier,o=ecipi and cn=admingroup,o=ecipi
conflict here !

##########################################################################

How to solve this conflict?
Labels (2)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: namdiagtool lum conflicts gid

Have you ever had an OES1 server in your tree? If you have had then did you follow the documentation before adding or upgrading to OES2 into your tree: Novell Doc: OES 2 SP2: Planning and Implementation Guide - Caveats to Consider Before You Install ?

It might be related since the conflicts you have is with novlxtier.

Thomas
0 Likes
Highlighted
pabloecipi
New Member.

Re: namdiagtool lum conflicts gid

Thanks for your reply.
I have a Linux OES1 in eDirectory.
The OES2 SP3 already installed.
LUM error prevents the operation of some services.
Corrected gid of the groups that are erroneous but the confict still exists.

In all the groups I have a second NAME_HASH_INDEX generated by this conflict, there is no way to correct ???

Inserting Groups :
cptr: novlxtier
name_hash_index is 106
novlxtier, adding new hashentry

name_hash_index is 53
pgU, adding new hashentry

cptr: admingroup
name_hash_index is 8
admingroup, adding new hashentry

name_hash_index is 53
hashentry: pgU already exists
comparing cn=novlxtier,o=ecipi and cn=admingroup,o=ecipi
conflict here !
cptr: www
name_hash_index is 1
www, adding new hashentry

name_hash_index is 53
hashentry: pgU already exists
comparing cn=novlxtier,o=ecipi and cn=www,o=ecipi
comparing cn=admingroup,o=ecipi and cn=www,o=ecipi
conflict here !
0 Likes
Knowledge Partner
Knowledge Partner

Re: namdiagtool lum conflicts gid

pabloecipi;2063187 wrote:
Thanks for your reply.
I have a Linux OES1 in eDirectory.
The OES2 SP3 already installed.
LUM error prevents the operation of some services.
Corrected gid of the groups that are erroneous but the confict still exists.

In all the groups I have a second NAME_HASH_INDEX generated by this conflict, there is no way to correct ???

Inserting Groups :
cptr: novlxtier
name_hash_index is 106
novlxtier, adding new hashentry

name_hash_index is 53
pgU, adding new hashentry

cptr: admingroup
name_hash_index is 8
admingroup, adding new hashentry

name_hash_index is 53
hashentry: pgU already exists
comparing cn=novlxtier,o=ecipi and cn=admingroup,o=ecipi
conflict here !
cptr: www
name_hash_index is 1
www, adding new hashentry

name_hash_index is 53
hashentry: pgU already exists
comparing cn=novlxtier,o=ecipi and cn=www,o=ecipi
comparing cn=admingroup,o=ecipi and cn=www,o=ecipi
conflict here !


No idea sry, you might want to open an Service Request with Novell on this issue.

Thomas
0 Likes
pabloecipi
New Member.

Re: namdiagtool lum conflicts gid

Continue investigating.
The "ldapsearch-x-h ip-bo = ecipi" (objectClass = uamPosixUser) "uidNumber gidNumber-D user-w password" only returns the uid, but not the gid.
Delete and recreate the LDAP Server - MyServer and LDAP Group - MyServer configure and restart the service ndsd.
The namdiagtool not report more conflict,
The id admin begin to return uid gid correctly.
Again thank you very much.
0 Likes
Knowledge Partner
Knowledge Partner

Re: namdiagtool lum conflicts gid

pabloecipi;2079553 wrote:
Continue investigating.
The "ldapsearch-x-h ip-bo = ecipi" (objectClass = uamPosixUser) "uidNumber gidNumber-D user-w password" only returns the uid, but not the gid.
Delete and recreate the LDAP Server - MyServer and LDAP Group - MyServer configure and restart the service ndsd.
The namdiagtool not report more conflict,
The id admin begin to return uid gid correctly.
Again thank you very much.


Glad you got it working...

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