Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
23.2 Repeated <strong>eDirectory</strong> Logins<br />
Repeated <strong>eDirectory</strong> logins can use up the available memory. Disable the Login Update attribute<br />
using ndsimonitor to overcome this problem.<br />
23.3 Enabling Event System Statistics<br />
Time related statistics are maintained for every event thrown and consumed in <strong>eDirectory</strong>. This<br />
information is useful for troubleshooting event consumer issues. These statistics are not required for<br />
normal functioning of directory; therefore, they are disabled for performance reasons. Event<br />
statistics can be enabled at runtime by using iMonitor advanced configuration parameters.<br />
novdocx (en) 22 June 2009<br />
To view the event statistics, set the ENABLE_EVENT_STATISTICS parameter and restart the server . It<br />
is a permanent configuration parameter.<br />
23.4 Tracking Memory Corruption Issues on<br />
Linux<br />
On Linux platforms, <strong>eDirectory</strong> uses google malloc (libtcmalloc) as the default memory allocator.<br />
To track memory corruption issues, set the MALLOC_CHECK_ environment variable in the ndsd<br />
startup script. The startup script checks for this variable. If set, the default system malloc is used,<br />
else google malloc is loaded.<br />
MALLOC_CHECK Settings in ndsd<br />
• When MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored.<br />
• When MALLOC_CHECK_ is set to 2, abort is called immediately.<br />
This helps to identify the real cause of the memory corruption at early stages, which might be<br />
difficult to track later.<br />
23.5 TCP Connection not Terminating after<br />
Abnormal Logout<br />
Sometimes the OES Linux server fails to detect a client host that has gone down abruptly due to a<br />
workstation crashing or a power outage. However, the connection is active for the default timeout<br />
(about 12 to 15 minutes) before the connection is cleared.<br />
If you have set the concurrent connections to 1, it is recommended that you either terminate the<br />
connection manually, or wait for the estimated timeout before logging in again. This situation occurs<br />
when the watchdog process fails to close the connection cleanly. So, if the concurrent connections<br />
are set to 1 and the connection is not cleared by the watchdog, users cannot log in.<br />
Linux kernel provides three parameters to change the way keepalive probes work from the server<br />
side. Use these parameters to implement a workaround at the TCP level.<br />
110 <strong>Novell</strong> <strong>eDirectory</strong> <strong>8.8</strong> <strong>Troubleshooting</strong> <strong>Guide</strong>
Change language