Software compiliation options

• List of current software
• OpenSSL Build parameters
• Heimdal Build parameters
• Berkeley BDB Build parameters
• Cyrus-SASL Build parameters
• OpenLDAP Build parameters

Configuration pages

• Hardware Configuration
• Base LDIF file used for preload setup
• Master slapd Configuration
• Replica slapd Configuration
• BDB Configuration
• syslog Configuration
• Example Schema
• Example ACL's
• Monitoring Types

Related pages

• Directory Service page
• OpenLDAP History and Configuration Overview

• QUICK LINKS
  • answers.stanford.edu
  • apple.stanford.edu
  • computing.stanford.edu
  • courses.stanford.edu
  • datarates.stanford.edu
  • dell.stanford.edu
  • departmentphone.stanford.edu
  • email.stanford.edu
  • ess.stanford.edu
  • helpsu.stanford.edu
  • myitserviceshelp.stanford.edu
  • orderithelp.stanford.edu
  • software.stanford.edu
  • studentphone.stanford.edu
  • techtraining.stanford.edu
  • tools.stanford.edu
  • unixcomputing.stanford.edu
  • vpn.stanford.edu
  • web.stanford.edu
  • windows.stanford.edu
• SERVICES
  • IT Services Only
  • All Campus Providers
    → computing.stanford.edu
• GETTING HELP
  • Stanford Answers
  • HelpSU: IT Help Desk
  • Training
• PROJECTS
• ABOUT US
  • What We Do
  • Organization Chart
  • Strategic Plan
  • Jobs
  • Contact info
  • Service & System Metrics
• INTERNAL
• SEARCH

  • Search IT Services:
     

Directory

We currently use Nagios to monitor our OpenLDAP server.

Default Nagios plugins:

• Disk usage
• LDAP queries (via anonymous query)
• Load average (5,10,and 15 minute
• Swap usage

Custom scripts run on the local machine via a remote Nagios call:

• Size of Berekeley DB (via db_stat -m)
• Size of slurpd replog
• Size of slapd's memory footprint
• Size of slurpd's memory footprint
• Creation of reject files by slurpd
• Verification that slurpd is running
• Total memory usage

In addition, we also gather statistics on how OpenLDAP is operating via the use of Cricket:

OpenLDAP statistics in Cricket

Here is the ldapmon script we use, which is called via the Cricket Defaults file. It was graciously provided by Andrew Tristan from UC Riverside, and then updated here to include support for the OpenLDAP 2.2 or later releases.