Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

23.13 NDS Server Does Not Start Automatically
in the Virtual SLES 10
After adding packages, if you do not configure eDirectory by using YaST, you need to run the
following command at the command line.
chkconfig -a ndsd
novdocx (en) 22 June 2009
23.14 ndsd Does Not Start After a System Crash
In some situations, eDirectory services (ndsd) doesn't start after a system crash or a power failure.
To start the eDirectory again, do the following:
1 Delete /var/opt/novell/eDirectory/data/ndsd.pid file.
2 Enter /etc/init.d/ndsd start command.
23.15 Do not Execute ndstrace With All Tags
Enabled on UNIX Systems
With all tags enabled, ensure you do not run ndstrace on the following:
• A loaded system in Journal mode: It tends to build up ndsd memory.
• Servers in inline mode: It crashes ndsd.
23.16 LDAP is Not RFC Compliant For
Anonymous Search Requests
If a client performs an unauthenticated search operation when anonymous binds are disabled, the
LDAP server responds with the bind result of inappropiate authentication instead of the search
result, operationsError.
23.17 Troubleshooting Ports with Custom
eDirectory 8.8 Instances
In eDirectory 8.8, if you configure a new instance in a custom location when the default instance
server is down, it takes the default instance ports. The default instance does not come up, because
the ports of the default instance are alloted to the custom location instance.
Follow the procedure in Troubleshooting Ports with Custom eDirectory 8.8 Instances (http://
www.novell.com/coolsolutions/feature/17933.html) before rebooting the host.
23.18 Rebooting the Host
Only the default instance created through using the default instance binaries is started after reboot.
You can set the paths and use ndsmanage to start the other instances.
114 Novell eDirectory 8.8 Troubleshooting Guide