Dsrepair shows cluster resource as unknown, or like a normal server

  • 3692509
  • 24-Jan-2008
  • 07-May-2014


Novell eDirectory for All Platforms
Novell eDirectory 8.8 for All Platforms
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Formerly TID 10101125


dsrepair/ndsrepair sometimes shows cluster resource as unknown or included as an NDS server (i.e. in a Report Time Synchronization).  As cluster resources aren't really eDirectory servers, we don't want/need to see them on repair reports.


This issue has been resolved with an update to eDirectory and eDirectory 8.8.3 (or later).

Additional Information

This issue is cosmetic and will only slow the given report while it attempt to connect & times out.
As background, ndsrepair/dsrepair code works off the list of ncp server objects when it does server object related work.  As clustered resources have a virtual ncp server object, they are included.  To avoid including cluster objects, the repair tool was updated to look for the NCS:Volumes attribute on server objects.  If it exists, it will skip that object and move on to the next.
Therefore, if your clustered resource objects are proper, you should not see cluster objects in dsrepair/ndsrepair logs or output.
If they do appear, you will want to ensure the NCS:Volumes attribute is properly populated on the object.  To so do:
  1. log into iManager
  2. click the spyglass icon (on top)
  3. click on the Search tab
  4. enter the object name in question in the search box (instead of the default *) and click search
  5. identify the proper object in the search results, right click the object and select "modify object"
  6. On the General tab, click Options -- this will display the populated and non-populated attributes.
  7. If the NCS:Volumes attribute is not in the list populated, then add it and point it to the corresponding *_SERVER object -- which is contained/below the Cluster object (i.e. 3 red balls icon) in eDirectory.

Change Log

7-May-2014 - KKlemm:
  • updated to include OES 2/11 in the products area
  • revamped the situation, resolution and additional information sections
  • added steps to check & resolve if still occurring with latest code
  • removed internal comments as ndsrepair/dsrepair should now handle this properly
  • retired similar, but older TID 10101125