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

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

Also found this: Support | "Error: File Protocol Error Occurred ..." messages when using Storage, Archive Versioning, File Protocols, and Clustering Plug-Ins for iManager.

Investigate CIMOM (/tmp/owcimomd.log) debug file.
Check to see that the CIMOM is receiving connections from iManager.
You'll see something like this:
[47430440190288] Received connection on 151.155.188.5:5989 from 137.65.59.11:58376
If you don't see this, iManager is not connecting to the CIMOM. Check IP addresses, firewalls, other usual suspects. If you are receiving connections, look for authentication failures, or other instances of the word "fail" or "Fail" that may be related to the NSS admin volume provider. "
If you are on a 64 bit server then you could possibly not have the owcimomd providers that you need.
The fix is to creae a symbolic link "ln -s /opt/novell/lib64/openwbem/c providers/libNovell_NSS_AdminSession.so
/opt/novell/lib/openwbem/c providers/"
If you see the following in the owcimod debug log then you have this problem.

[1149274432] XMLExecute::processSimpleReq caught CIM exception:


Code: 11


File: OW_InstanceRepository.cpp


Line: 328

Investigate iManger (/var/opt/novell/iManager/nps/WEB-INF/logs/debug.html) debug file.
Search for "CIMOM” or "NSS”. Then look for specific errors when it tries to login.
Trying CIM/XML protocol
11/10/06 [11:26:37.077] VirtualFile...........-1 Exception caught trying CIMOM protocol: 30602
11/10/06 [11:26:37.078] VirtualFile...........-1 Trying NCP protocol
11/10/06 [11:26:37.080] VirtualFile...........-1 Exception caught trying NCP protocol: 30602

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

After restarting the server, I filtered out the nss-corresponding messages from /var/log/messages. There were error messages in the result as listed below.

---------------------------------

Sep 5 07:42:59 SERV-Sel-1 dbus-daemon-launch-helper: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:42:59 SERV-Sel-1 hald[2841]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:42:59 SERV-Sel-1 hald[2841]: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:43:06 SERV-Sel-1 id: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:43:12 SERV-Sel-1 id: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:43:18 SERV-Sel-1 su: nds_nss_GetGroupsbyMember: Failed to init socket, status = 0
Sep 5 07:43:29 SERV-Sel-1 nss: Starting Novell Storage Services (NSS)
Sep 5 07:43:30 SERV-Sel-1 nss: Start up eDir and LUM
Sep 5 07:43:31 SERV-Sel-1 nss: Start up NSS modules
Sep 5 07:43:32 SERV-Sel-1 kernel: [ 56.109661] libnss loaded
Sep 5 07:43:32 SERV-Sel-1 kernel: [ 56.349003] nsslnxlib loading...
Sep 5 07:43:32 SERV-Sel-1 kernel: [ 56.458370] nsslnxlib loaded
Sep 5 07:43:33 SERV-Sel-1 kernel: [ 57.003638] NSS::/usr/src/packages/BUILD/nss/modules-build/nss/nssLKM.c[254]
Sep 5 07:43:33 SERV-Sel-1 kernel: [ 57.003641] NSS::/usr/src/packages/BUILD/nss/modules-build/nss/nssLKM.c[256]
Sep 5 07:43:33 SERV-Sel-1 kernel: [ 57.054318] now open config files: /etc/opt/novell/nss/nssstart.cfg
Sep 5 07:43:33 SERV-Sel-1 kernel: [ 57.156133] NSS::/usr/src/packages/BUILD/nss/modules-build/nss/nssLKM.c[336]
Sep 5 07:43:36 SERV-Sel-1 kernel: [ 60.182555] COMN::/usr/src/packages/BUILD/nss/modules-build/comn/comnLKM.c[198]
Sep 5 07:43:36 SERV-Sel-1 kernel: [ 60.478563] COMN::/usr/src/packages/BUILD/nss/modules-build/comn/comnLKM.c[200]=0
Sep 5 07:43:36 SERV-Sel-1 kernel: [ 60.788919] ZLSS::/usr/src/packages/BUILD/nss/modules-build/zlss/zlssLKM.c[233]
Sep 5 07:43:36 SERV-Sel-1 kernel: [ 60.953406] ZLSS::/usr/src/packages/BUILD/nss/modules-build/zlss/zlssLKM.c[235]
Sep 5 07:43:37 SERV-Sel-1 kernel: [ 61.143240] MANAGE::/usr/src/packages/BUILD/nss/modules-build/manage/manageLKM.c[239]
Sep 5 07:43:37 SERV-Sel-1 kernel: [ 61.143589] MANAGE::/usr/src/packages/BUILD/nss/modules-build/manage/manageLKM.c[241]
Sep 5 07:43:37 SERV-Sel-1 kernel: [ 61.181748] Opening trustee file: /etc/opt/novell/nss/trustees.xml
Sep 5 07:43:37 SERV-Sel-1 kernel: [ 61.445054] LSA::/usr/src/packages/BUILD/nss/modules-build/lsa/lsaLKM.c[538]
Sep 5 07:43:45 SERV-Sel-1 nss: NSS started

----------------------------------

I would gess, some of these messages especially in the first part of the result may causing my problems.

--Ferdi

On Mon, 03 Sep 2012 20:16:02 0000, fgiese wrote:

fgiese,

I think you need to update your server to latest patches to resolve this
particular issue. This seems to be described in TID 7005336.

This was addresed in the "June 2012 OES11 Hot Patch for NCP - 6385"

Thanks
Hans

HvdHeuvel;2217210 wrote:
On Mon, 03 Sep 2012 20:16:02 0000, fgiese wrote:

I think you need to update your server to latest patches to resolve this
particular issue. This seems to be described in TID 7005336.

This was addresed in the "June 2012 OES11 Hot Patch for NCP - 6385"

Thanks
Hans

Dear Hans,

thanks for Your reply. To update with OES-SP1 would also be a solution? What do You think?

--Ferdi