2.1 Installation

This section discusses various problems you may encounter during the eDirectory 8.8 installation along with troubleshooting tips.

2.1.1 Fatal Error Occurs in Schema Sync When Installing a Second eDirectory Server into the Tree on a SLES 11 Machine

Configure an eDirectory tree and Install another server into the tree. In both the cases, select the option to use all the available interfaces. Use the same interfaces for both the servers. For example, 127.0.0.2. Start DSTrace on the first server with SCMA, SKLK and SYNC options.

2.1.2 Installation Not Successful

  • Check for the following error message in the /var/adm/messages directory:

    Unable to bind to SLP Multicast Address. Multicast route not added? 
    

    This message is displayed if the Linux or Solaris machine is not configured for a multicast route address.

    Add the multicast route address and restart the slpuasa daemon.

  • If the -632: Error description System failure error message appears during installation, exit from the installation process.

    Set the n4u.base.slp.max-wait parameter to a larger value, such as 50, in the /etc/opt/novell/eDirectory/conf/nds.conf file, then restart the installation process.

  • During installation, if the Tree Name Not Found error message is displayed, do the following:

  1. Check whether multicast routing is enabled on the Solaris host that you are installing the product on.

  2. Specify the IP address of the master server of the Tree partition.

2.1.3 Installation Takes a Long Time

When you are installing eDirectory into an existing tree and the installation takes a long time to complete, look at the DSTrace screen on the server. If the -625 Transport failure message appears, you need to reset the address cache.

To reset the address cache, enter the following command at the system console:

set dstrace = *A

2.1.4 eDirectory Install Fails for Container Administrators

The eDirectory 8.8 installation program supports installations by administrators who have supervisor rights to the container that the server resides in. In order to handle this, the first server that eDirectory 8.8 is installed into must have supervisor rights to [Root] to extend the schema. From that point on, subsequent servers do not have to have rights to [Root]. However, with eDirectory 8.8, depending on the platform that eDirectory 8.8 is installed in to first, all schema might not be extended, requiring supervisor rights to [Root] for subsequent server installations on different platforms.

If eDirectory 8.8 will be installed on multiple platforms, make sure that you have supervisor rights to [Root] for the first server eDirectory will be installed on for EACH platform. For example, if the first server that eDirectory 8.8 is going to be installed on is running Linux, and eDirectory 8.8 will also be installed on Solaris, the first server for each platform must have supervisor rights to [Root]. Subsequent servers on each platform will only have to have container administrator rights to the container where the server is being installed.

For additional information, see solution NOVL83874 in the eDirectory 8.7.x Readme Addendum.

2.1.5 NICI Installation Failed - 1497

A message warning that the NetIQ International Cryptographic Infrastructure (NICI) initialization failed means that the NFK file is not right. Ensure that you have the right NFK file. This problem might not occur on Linux platforms, as by default the NFK file is part of the NICI package.

2.1.6 Naming Objects

When you use special characters while naming objects, the -671 No Such Parent error message appears. Avoid using any of the following special characters when naming objects:

\ /, * ? .

2.1.7 NICI Does Not Get Installed in the Server Mode on Windows

In the Properties dialog box of the NICIFK file there is a tab called Security. If there are no names in the Group or user names field, then this issue occurs.

To work around this problem, do the following:

  1. Remove the NICIFK file.

    This is present in C:/Windows/system32/novell/nici if the system root is C:/Windows/system32. If the system root is F:/Windows/system32 then this file is present in F:/Windows/system32/novell/nici.

  2. Install eDirectory.

2.1.8 Tarball Upgrade Fails With "Cannot open or remove a file containing a running program" Error Message

While doing Tarball Upgrade in AIX, in the file copying stage if you get Cannot open or remove a file containing a running program error message, perform the following steps to resolve the issue:

  1. Run /usr/sbin/slibclean as a root user.

  2. Continue the upgrade from file copying stage.

2.1.9 Issue with eDirectory and YUM

If you install eDirectory 8.8 SP6 or later on a Red Hat Enterprise Linux server with the YUM package manager installed, you may encounter an issue when using YUM.

YUM and eDirectory 8.8 both use the libexpat.so.0 library, and when you run YUM with one or more options, YUM returns an error in the console. To work around this error, use a text editor to comment out the following line in the /etc/ld.so.conf.d/novell-NDSbase.conf file and then run ldconfig:

/opt/novell/eDirectory/lib64

After commenting out the line and running ldconfig, ensure that you run the following command in a terminal window each time you start eDirectory:

source /opt/novell/eDirectory/bin/ndspath

Restart eDirectory using the same terminal. ndspath resolves the necessary path dependencies.

2.1.10 Performance Issues When Running eDirectory with BTRFS

If you install eDirectory on a SLES server within a BTRFS filesystem, you may experience performance issues when performing LDAP operations or using the NetIQ Import Conversion Export Utility (ICE). For performance reasons, it is recommended that you use the ext3 filesystem for your eDirectory server.