Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

18Miscellaneous
• Section 18.1, “Backing Up a Container,” on page 95
• Section 18.2, “Repeated eDirectory Logins,” on page 95
• Section 18.3, “TCP Connection not Terminating after Abnormal Logout,” on page 95
• Section 18.4, “NDS Error, System Failure (-632) Occurs When Doing ldapsearch for the User
Objects,” on page 96
• Section 18.5, “Disabling SecretStore,” on page 97
18.1 Backing Up a Container
While using ndsbackup to backup a container that has many objects (like a million), it might take
some time to get the list of the objects in the container and start their individual backup.
18.2 Repeated eDirectory Logins
Repeated eDirectory logins can use up the available memory. Disable the Login Update attribute
using ndsimonitor to overcome this problem.
18.3 TCP Connection not Terminating after
Abnormal Logout
Sometimes the OES Linux server fails to detect a client host that has gone down abruptly due to a
workstation crashing or a power outage. However, the connection is active for the default timeout
(about 12 to 15 minutes) before the connection is cleared.
If you have set the concurrent connections to 1, it is recommended that you either terminate the
connection manually, or wait for the estimated timeout before logging in again. This situation occurs
when the watchdog process fails to close the connection cleanly. So, if the concurrent connections
are set to 1 and the connection is not cleared by the watchdog, users cannot log in.
Linux kernel provides three parameters to change the way keepalive probes work from the server
side. Use these parameters to implement a workaround at the TCP level.
These parameters are available in /proc/sys/net/ipv4/ directory.
• tcp_keepalive_time: Determines the frequency of sending the TCP keepalive packets to keep a
connection alive if it is currently unused. This value is used only when keepalive is enabled.
The tcp_keepalive_time takes an integer value in seconds. The default value is 7200 seconds or
2 hours. This holds good for most of the hosts and does not require many network resources. If
you set this value to low, it engages your network resources with unnecessary traffic.
• tcp_keepalive_probes: Determines the frequency of sending TCP keepalive probes before
deciding a broken connection.
The tcp_keepalive_probes takes an integer value, recommended less than 50 depending on
your tcp_keepalive_time and the tcp_keepalive_interval values. The default is to set to 9 probes
before informing the application of the broken connection.
18
novdocx (en) 6 April 2007
Miscellaneous
95