More information please. What is the name of the pool? Have you deleted the old pool and volume form NDS? Is this the root? Can all the servers talk to each other? Have you tried with iManager? Lots of details left out.

--El

fgiese;2216767 wrote:
After successfully reinstalling edirectory on OES11 server, I need to recreate nss-pool and volume object into edirectory. By using the nssmu-tool, we get the error

"Error -765: Error getting NDS name from pool" and "Error -765: -765 Error converting GUID to name"

during Update NDS (F4)

We were successful doing it this way all the times till now.

Before reinstalling edirectory, we deleted all server related objects including pool and volume object in NDS. After this successful operation, we used the yast2 nss command to recreate the local admin object as we did serveral times. After that the nssmu utility is listing pool and volume but updating NDS is failing. The server holds no replica of the root partition.

Viewing pool and volume during iManager produces following message:

"Error: CIMOM error occurred: could not seek in the management file."

Doing this on other servers works pretty good. Ndsrepair commands (-T, -E, -C -Ad -A) showed other servers in the tree and ended without any error message.

--Ferdi

Check Obituaries? ndsrepair -R -Ad -OT

Also, does your LUM work properly? How about SLP? Hosts file will be a work-around.

--El

fgiese;2216802 wrote:
Before reinstalling edirectory, we deleted all server related objects including pool and volume object in NDS. After this successful operation, we used the yast2 nss command to recreate the local admin object as we did serveral times. After that the nssmu utility is listing pool and volume but updating NDS is failing. The server holds no replica of the root partition.

Viewing pool and volume during iManager produces following message:

"Error: CIMOM error occurred: could not seek in the management file."

Doing this on other servers works pretty good. Ndsrepair commands (-T, -E, -C -Ad -A) showed other servers in the tree and ended without any error message.

--Ferdi

Thanks, El for Your patience with me. I checked the Unix Workstaion object and found out that there was no openwbem entry under LUN enabled services. And I didn't find any oportunity to make a change on that settings. If this may cause the error, it would be very nice if you can tell me how this can be done.

Thanks
--Ferdi

Thanks, El for Your patience with me. I checked the Unix Workstaion object and found out that there was no openwbem entry under LUN enabled services. And I didn't find any oportunity to make a change on that settings. If this may cause the error, it would be very nice if you can tell me how this can be done.

Thanks
--Ferdi

Sorry, this Unix Workstation object looks like any other (working!!) OES11 Server Unix Workstation object in our tree. The object I reflected on, was an OES2-SP3 Unix Workstation object. This couldn't be the source of our problem.

fgiese;2216997 wrote:
Thanks, El for Your patience with me. I checked the Unix Workstaion object and found out that there was no openwbem entry under LUN enabled services. And I didn't find any oportunity to make a change on that settings. If this may cause the error, it would be very nice if you can tell me how this can be done.

Thanks
--Ferdi