Example 1: One-Way Synchronization with Join

Understanding and Deploying LDAP Directory Services > 19. Troubleshooting > Troubleshooting Checklist

<  BACK CONTINUE  >
153021169001182127177100019128036004029190136140232051053054012005146028251061087063088

Troubleshooting Checklist

The following are checklists of items to note and information to gather when you have a problem with your directory.

Directory Outages

  • Are directory clients timing out, or are their connections being refused by the server?

  • Are all network components (routers, hubs, switches, cables) between the clients and the servers functional?

  • Is the directory server machine running? If not, has the hardware failed?

  • Are all hardware components on the directory server machine functioning properly? Are there any operating system logs that record hardware failures?

  • Is the directory server process running? If so, is it consuming any CPU time? Is it causing any disk activity?

  • If the directory server process is not running, did it fail when processing a particular client request? Does it fail each time it receives such a request? Such a request might represent a denial-of-service attack.

Performance Problems

  • Are specific types of directory operations performing poorly, or is the overall performance of the server poor?

  • Are appropriate attribute indexes being maintained on the directory server?

  • Is the size of the directory server process too large? Does it become too large immediately upon startup or gradually over time?

  • Are the cache sizes of the directory (if any) configured appropriately ( neither too small nor too large)?

  • Are there other processes running on the directory server machine that are causing the poor performance?

  • Is the directory under a particularly heavy load? Is this load expected? If it is excessive, is there one particular client or application accounting for most of the load?

Problems with Directory Data

  • Is data missing or incorrect?

  • Does the data appear to be corrupted in a catastrophic manner? Such damage indicates a serious hardware or software problem.

  • Is the data damaged in some specific way? For example, have certain entries been erroneously deleted? Can the source of the erroneous modifications be determined by examining directory server logs?

Security Problems

  • Are there telltale signs of a break-in, such as connections from an unexpected location or unexpected modifications to directory entries?

  • Do directory logs show unexpected client activity?

  • Is the directory experiencing a denial of service attack? Such an attack usually overwhelms available server resources. Is the source of the attack known?



Understanding and Deploying LDAP Directory Services,  2002 New Riders Publishing
<  BACK CONTINUE  >

2002, O'Reilly & Associates, Inc.



Understanding and Deploying LDAP Directory Services
Understanding and Deploying LDAP Directory Services (2nd Edition)
ISBN: 0672323168
EAN: 2147483647
Year: 1997
Pages: 245

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net