D.3 Troubleshooting the Issues with Multiple Instances of eDirectory

The following table lists the issues you might encounter and the suggested actions for working on these issues. If the problem persists, contact your NetIQ representative.


Suggested Actions

If the First Instance is Down, HTTP Does Not Work

On Linux, if eDirectory is configured on a box with multiple NIC cards and if HTTP is bound to more than one interface; if the first interface goes down, HTTP would not be accessible from the remaining interfaces.

This is because the remaining interfaces will redirect the request to the first one, but the first interface is down.

To resolve this issue, if the first interface goes down, restart eDirectory.

ndsd Falls Back to Default Port if the Interface Specified is Incorrect

When using ndsconfig new or ndsmanage to create a second instance of the directory, if the interface specified is incorrect, nds tries to use the default interface. If you specify non default port (for example 1524), the interface specified is incorrect, it uses the default interface and the default port of 524.

For n4u.server.interfaces, if the interface specified is incorrect, then ndsd will try to listen on the first interface and the port number would be the one specified in n4u.server.tcp-port.

How to Rebuild .edir Directory

The .edir directory is used for tracking multiple instances of eDirectory. To recreate the lost or corrupted instances file (instances.$uid file, where $uid specifies the user ID of the user in the system), you must create its individual instances file.

These files must contain the absolute location of the nds.conf files of all the instances configured by the user. For example, a user with uid as 1000 must create an /etc/opt/novell/eDirectory/conf/.edir/instances.1000 instances file with the following entries: