Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

Possible NetStorage Login Latency after Applying OES2 Updates

This document (7009568) is provided subject to the disclaimer at the end of this document.


Novell NetStorage
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3


After applying regular updates through the Novell Patch channels, in some instances users have experienced latency when logging in to NetStorage.  This could add several seconds up to several minutes to the amount of time required to login.


This is a known issue and has been reported to engineering.

One thing that has been discovered so far is that during the update, sometimes, certain registry entries needed for NetStorage get deleted.  To verify if this has happened on the server experiencing Latency run the following commands:

cd /opt/novell/xtier/bin
cd /local_machine/Software/Novell/XTier/Configuration/XSrv/Authentication Domains
ls                   NOTE:  the ls command should return an entry that has either the IP address or DNS Name of the authentication server, this will be referred to as <IP or DNS> in the next command
cd <IP or DNS>

After running the above commands, the output should display your search contexts, if so, this portion of the registry was NOT damaged during the update.  If  it is impossible to 'cd' this deep into the registry, then the registry was damaged during the update, and it will be necessary to recreate the xtier registry keys.

This issue is being analyzed by the NetStorage Developers.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7009568
  • Creation Date:14-OCT-11
  • Modified Date:27-APR-12
    • NovellNetStorage
      Open Enterprise Server

Did this document solve your problem? Provide Feedback