Novell eDirectory 8.8 SP4 for Linux, Solaris, and AIX

September 30, 2008

1.1.1 Linux
1.1.2 Solaris
1.1.3 AIX
2.6.1 Schema
2.6.4 Options
3.3.1 iManager

1.0 Installation

1.1 Prerequisites

NOTE:Check the currently installed Novell and third party applications to determine if eDirectory™ 8.8 SP4 is supported before upgrading your existing eDirectory environment. You can find out the current status for Novell products in the TID - What products are supported with Novell eDirectory 8.8 SP4?. It is also highly recommended to backup eDirectory prior to any upgrades.

1.1.1 Linux

  • 32-bit

    • SUSE Linux Enterprise Server 9 SP4

    • SUSE® Linux Enterprise Server 10 SP1 and SP2

    • SUSE® Linux Enterprise Server (SLES) 10 SP1 XEN

    • Red Hat Advanced Server 4

    • Red Hat 5.0

    • Red Hat 5.0 AP

    • Red Hat 5.1 AP Virtualization

  • 64-bit

    • SUSE Linux Enterprise Server (SLES) 9 SP4

    • SUSE® Linux Enterprise Server (SLES) 10 SP1 and SP2

    • SUSE® Linux Enterprise Server (SLES) 10 SP1 XEN

      IMPORTANT:eDirectory 8.8 SP4 is supported on the SLES 10 XEN* virtualization service that runs the SLES 10 guest OS. The updates are available at

      To determine the version of SUSE Linux you are running, see the /etc/SuSE-release file.

    • Red Hat Advanced Server 4

    • Red Hat 5.0

    • Red Hat 5.0 AP

    • Red Hat 5.0 AP Virtualization

      Ensure that the latest glibc patches are applied from Red Hat Errata on Red Hat systems. The minimum required version of the glibc library is version 2.1.

  • 64-bit eDirectory Supported Platform

    • SLES 10 SP1 64-bit

    • SLES 10 SP2 64-bit

  • 256 MB RAM minimum

  • 90 MB of disk space for the eDirectory™ server

  • 25 MB of disk space for the eDirectory administration utilities

  • 74 MB of disk space for every 50,000 users

  • Ensure that gettext is installed. To install gettext, search the rpmfind Web site for gettext.

NOTE:The net-snmp-32-bit RPM should be installed on 64-bit SLES or OES Linux.

  • For OES1 servers, apply hotpatch ZLM6.6.2 HP4 before upgrading to eDirectory 8.8 SP4. On servers running SLES 10 or SLES 10 SP1, the client package rcd and rcd-devel (if not present earlier) should be upgraded to the latest patch level by using the YaST online update.

1.1.2 Solaris

  • Any one of the following:

    • Solaris 9 on Sun* SPARC*

    • Solaris 10 on Sun* SPARC*

  • Solaris Express Developer Edition

  • All latest recommended patches available on the SunSolve* Web page. If you do not update your system with the latest patches before installing eDirectory, you might have problems while installing and configuring eDirectory.

  • A minimum of 128 MB RAM

  • 120 MB of disk space for the eDirectory server

  • 32 MB of disk space for the eDirectory administration utilities

  • 74 MB of disk space for every 50,000 users

1.1.3 AIX

  • AIX* 5L Version 5.3

  • All recommended AIX OS patches, available at the IBM* Tech Support Web site Web site

  • 128 MB RAM minimum

  • 190 MB of disk space for the eDirectory server

  • 12 MB of disk space for the eDirectory administration utilities

  • 74 MB of disk space for every 50,000 users

1.2 Installing eDirectory on Linux, Solaris, and AIX

Use the nds-install command in the setup directory for installing eDirectory:


If you download Novell® eDirectory 8.8 SP4 from, use gunzip downloaded file name to extract the downloaded file to a tar file. Then use tar xvf eDirectory file name.tar to get packages and RPMs with the eDirectory installation and uninstallation scripts.

For more information on installing eDirectory, refer to the Novell eDirectory 8.8 SP4 Installation Guide.

1.3 Interoperability Between eDirectory and Nsure Audit 1.0.x

eDirectory 8.8 SP4 does not function properly with Nsure™ Audit 1.0.x. For full functionality with eDirectory 8.8 SP4, upgrade to Nsure Audit 2.0.

1.4 iManager Plug-Ins Installation

2.0 Known Issues

2.1 Installation and Configuration Issues

2.1.1 Error While Loading Shared Libraries:

eDirectory installation fails if the library is not installed on SLES 9.

To resolve this issue, download this library from Recommended update for LSB.

2.1.2 eDirectory 8.8 SP4 Fails on SLES10 and RHEL 5.0

  • SLES 10: While adding eDirectory 8.8 SP4 server from a SLES 10 host (or to SLES 10) to an existing tree running on different host, the process might fail to add the server if the firewall is enabled.

    Enable SLP services and an NCP™ port (the default is 524) in the firewall to allow the secondary server addition.

  • RHEL 5.0: When you configure eDirectory on RHEL 5.0, it fails because libstdc++6.0 is automatically installed with Red Hat 5.0. Because the embox, pkiinst, and pkiserver modules are linked to libstdc++5, the incorrect compat library causes the eDirectory configuration to fail.

    To work around this issue, install the compat-libstdc++-33-3.2.3-61.i386.rpm library manually.

    On a Red Hat system, while adding a secondary server to an eDirectory tree, ndsconfig hangs during schema synchronization. However, you can add it if you open the port 524 in the firewall.

2.1.3 eDirectory packages marked for deletion while upgrading from SLES9 to SLES10

The upgrade causes eDirectory packages to be marked for deletion. You can deselect this option to avoid eDircetory deletion.

If eDirectory is accidentally deleted, there is no data loss and it can be reinstalled.

2.1.4 ndsd Dumps the Core while Accessing the NDS Server

ndsd dumps the core in the dib directory of eDirectory because of a failed install while shutting down the server. This can be ignored because it does not corrupt data or disrupt services.

2.1.5 nds-install Script Fails if eDirectory Installation is Aborted on AIX

If eDirectory installation is stopped midway, the fileset might be installed, but in an uncommitted state. This fileset must be removed completely to reinstall eDirectory.

Use the following command to clean the fileset:

installp -ug <fileset>

Example: installp -ug NDS.NDSserv

2.1.6 eMBox GUI Element Result Inconsistent with the Command Printed

When you select a radio button from the eMBox graphical interface, the command line window does not match with the result of the button selection. It shows it as selected, but if executed it works fine and the selected buttons get executed.

2.2 eDirectory Behavior on SElinux enabled Red Hat Systems

  • New Tree: When you add a server to a new eDirectory tree, the following error displays:

    ndsconfig: error while loading shared libraries: /opt/novell/lib/
    cannot restore segment prot after reloc: Permission denied.
  • Existing Tree: When you add a server to an existing eDirectory tree, ndsconfig does not respond while synchronizing schema because SELinux is enabled on the system.

    To disable the SELinux for an application and continue the configuration, refer to the Redhat documentation.

2.3 Uninstallation Issues

2.3.1 Uninstallation Fails if Installation Was Not Successfully Completed

If eDirectory installation fails, nds-uninstall can't remove eDirectory.

To resolve this, install eDirectory again in the same location and then uninstall it.

2.3.2 nds-uninstall -s option Fails to Retain Configuration and DIB Files

You must not use -s option to retain the nds.conf and the DIB. Ensure you backup them before performing nds-uninstall operation.

2.4 Upgrade Issues

2.4.1 Duplicate Files Created after Upgrading from eDirectory 8.8.2 to eDirectory 8.8.3

After upgrading eDirectory, the new configuration files get .new extension. If there are any changes to these files, they can be absorbed in your files.

2.4.2 Upgrading OES1 / SLES9 Servers from eDirectory 8.7.3.x to eDirectory 8.8.x Fails When IDM 3.x is Installed

When you run ndsconfig upgrade, the following error message displays:

n4u_send_command failed.

To work around this issue: Ensure you reinstall IDM before executing ndsconfig upgrade.

For more information on upgrading to eDirectory 8.8.3, refer to the Upgrading to eDirectory 8.8.3.

2.4.3 Upgrading Simple Password Bind from an Older Version to 64-bit 8.8.3 Version

After upgrading eDirectory from 32-bit to 64-bit, ensure you update NMAS Simple Password method, for simple password binds to work.

If you are installing simple password method for the first time, do the following:

  1. Add simple password method from the NMAS folder.

  2. If bind does not work, add it again to refresh the NMAS policy.

2.5 Multiple Instances Issues

2.5.1 Default Instance Path

While configuring the second instance of eDirectory on your host, you are prompted for the default path. Select a different path and proceed.

2.6 ldif2dib Limitations

2.6.1 Schema

The LDIF file should mention all the object classes that an entry belongs to. You should also include the classes that an entry belongs to because of inheritance of classes. For example, an entry of type inetOrgPerson has following syntax in the LDIF file:

  • objectclass: inetorgperson

  • objectclass: organizationalPerson

  • objectclass: person

  • objectclass: top

2.6.2 ACL Templates

Objects that are bulkloaded with the ldif2dib utility are not added with ACLs that are specified in the ACL templates for the object class of the object.

2.6.3 Signal Handler

You can temporarily suspend the offline bulkload operation by pressing the s or S key. You can use Escape key (Esc) to stop the bulkload operation.

2.6.4 Options

On Linux, if the -b option is used, the statistics display menu disappears after the bulkload is complete.

2.6.5 Ldif2dib Might Fail to Upload Objects Beyond Several Millions on RHEL 5.0

When you attempt uploading millions of objects to eDirectory using ldif2dib, and the checkpoint interval is explicitly specified, the operation might halt with an error stating that the directory is full.

To work around this issue, skip the checkpoint interval (Use -i option with ldif2dib command).

2.7 Viewing French and Japanese Manpages

To view the French man page on Red Hat Linux, export the following:

export MANPATH=/opt/novell/man/frutf8:/opt/novell/eDirectory/man/frutf8

To view the man pages on AIX, use English locale.

2.8 Executing edirutil Utility Displays Error

When 32-bit Linux eDirectory is installed on 64-bit Linux eDirectory running edirutil, it displays the following error:

Exception in thread 'main' java.lang.NoClassDefFoundError: embox

edirutil is a command line utility and fails to execute for embox; however, embox works fine by using iManager.

To resolve it, you must change line 14 of edirutil script from

test -d /usr/lib64


test -d $NDSHOME/opt/novell/eDirectory/lib64

2.9 Unable to Limit the Number of Concurrent Users on Non-NetWare Platforms

The concurrent connection limit behavior of non-NetWare platforms is changed to match that of Netware. To resort to the old behavior (strict port based checking), set following parameter in nds.conf file.


2.10 Catalog Services with eDirectory 8.8 SP4

Catalog services running with eDirectory 8.8 SP4 are not supported. This is an old technology and has been largely replaced by the contextless login feature in the 4.9 Novell Client.

2.11 Localhost Issues in /etc/hosts

If you have a loopback address alias to the hostname of the system in /etc/hosts entry, that must be changed to the hostname or IP address. That is, if you have an entry similar to the one below in your /etc/hosts file, it needs to be changed to the correct entry given in second example below.

The following example has problems when any utility tries to resolve to ndsd server: test-system localhost.localdomain localhost

The following is a correct example entry in /etc/hosts: localhost.localdomain localhost test-system

If any third-party tool or utility resolves through localhost, then it needs to be changed to resolve through a hostname or IP address and not through the localhost address.

2.12 LDAP TCP and TLS Ports Issue with Large DIBs

When the DIB is large, the DS takes time to come up and wrongly displays the following errors:

LDAP TCP Port is not listening
LDAP TLS Port is not listening

In this scenario, the ports are not disabled but eDirectory services are slow to come up. To check the status of LDAP, refer to the ndsd.log file or enter the following command and grep for the LDAP TCP/TLS ports:

netstat -na

2.13 Deletion of a Moved Object Fails (error -637)

Deletion of a moved object can fail in a tree with two or more servers.

2.14 Issues with running Identity Manager with eDirectory on AIX

For proper functioning of Identity Manager with eDirectory, increase the max stack size of the ndsd by using the following command:

ldedit -b maxstack=0x10000000 /opt/novell/eDirectory/sbin/ndsd

Ensure that ndsd is not running when you execute this command.

3.0 Documentation

3.1 Viewing eDirectory Documentation

Novell eDirectory 8.8 SP4 has the following documentation:

  • Novell eDirectory 8.8 What's New Guide

  • Novell eDirectory 8.8 Installation Guide

  • Novell eDirectory 8.8 Administration Guide

  • Novell eDirectory 8.8 Troubleshooting Guide

These documents are available at the Novell eDirectory 8.8 online documentation Web site.

3.2 Readme Information

The latest version of this readme is available at the Novell eDirectory 8.8 online documentation Web site.

3.3 Additional Documentation

3.3.1 iManager

3.3.2 NMAS 3.3.0

For NMAS information, refer to the NMAS online documentation.

3.3.3 Certificate Server 3.3.1

For Certificate Server information, refer to the Certificate Server online documentation.

3.3.4 NICI 2.7.4

For NICI information, refer to the NICI online documentation.

4.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (® , TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.

5.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.

For a list of Novell trademarks, see the Novell Trademark and Service Mark list at

All third-party trademarks are the property of their respective owners.