X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=doc%2Fguide%2Fadmin%2Ftroubleshooting.sdf;h=d1b0215682fcdedd5b12ef9976084621d4df5ca3;hb=d534e1149505c44f6ff2c0631e56c1c11d687c5d;hp=05eced633596d92793e73f8f0c09421a2449bd80;hpb=1ebe5a93ff208925b3e94559ef4dadf6df428385;p=openldap diff --git a/doc/guide/admin/troubleshooting.sdf b/doc/guide/admin/troubleshooting.sdf index 05eced6335..cbf9619b12 100644 --- a/doc/guide/admin/troubleshooting.sdf +++ b/doc/guide/admin/troubleshooting.sdf @@ -1,13 +1,15 @@ # $OpenLDAP$ -# Copyright 2007 The OpenLDAP Foundation, All Rights Reserved. +# Copyright 2007-2013 The OpenLDAP Foundation, All Rights Reserved. # COPYING RESTRICTIONS APPLY, see COPYRIGHT. H1: Troubleshooting If you're having trouble using OpenLDAP, get onto the -OpenLDAP-Software mailing list. +OpenLDAP-Software mailing list, or: -Browse the list archives at {{URL:http://www.openldap.org/lists/}} +* Browse the list archives at {{URL:http://www.openldap.org/lists/#archives}} +* Search the FAQ at {{URL:http://www.openldap.org/faq/}} +* Search the Issue Tracking System at {{URL:http://www.openldap.org/its/}} Chances are the problem has been solved and explained in detail many times before. @@ -16,14 +18,7 @@ H2: User or Software errors? More often than not, an error is caused by a configuration problem or a misunderstanding of what you are trying to implement and/or achieve. -Sometimes you may encounter an actual OpenLDAP bug, in which case please visit -our Issue Tracking system {{URL:http://www.openldap.org/its/}} and report it there, -providing as much information as possible. - -Note: Our Issue Tracking system is {{B:NOT}} for OpenLDAP {{B:Support}}, please join our -mailing Lists: {{URL:http://www.openldap.org/lists/}} for that - -We will now attempt to discuss common user errors +We will now attempt to discuss common user errors. H2: Checklist @@ -51,6 +46,25 @@ posting to the list, or in the rare circumstances of reporting a bug. .{{S: }} +{{B: Have your certificates expired?}} +H2: OpenLDAP Bugs + +Sometimes you may encounter an actual OpenLDAP bug, in which case please visit +our Issue Tracking system {{URL:http://www.openldap.org/its/}} and report it. +However, make sure it's not already a known bug or a common user problem. + +* bugs in historic versions of OpenLDAP will not be considered; +* bugs in released versions that are no longer present in the Git master branch, +either because they have been fixed or because they no longer apply, +will not be considered as well; +* bugs in distributions of OpenLDAP software that are not related to the +software as provided by OpenLDAP will not be considered; in those cases please +refer to the distributor. + +Note: Our Issue Tracking system is {{B:NOT}} for OpenLDAP {{B:Support}}, please join our +mailing Lists: {{URL:http://www.openldap.org/lists/}} for that. + +The information you should provide in your bug report is discussed in our FAQ-O-MATIC at +{{URL:http://www.openldap.org/faq/data/cache/59.html}} H2: 3rd party software error @@ -76,18 +90,11 @@ H2: Debugging {{slapd}}(8) After reading through the above sections and before e-mailing the OpenLDAP lists, you might want to try out some of the following to track down the cause of your problems: -* Loglevel 256 is generally a good first loglevel to try for getting +* Loglevel stats (256) is generally a good first loglevel to try for getting information useful to list members on issues * Running {{slapd -d -1}} can often track down fairly simple issues, such as missing schemas and incorrect file permissions for the {{slapd}} user to things like certs - -For those of you so inclined, a great LDAP Protocol Dissector is available in {[PRD:Wireshark}} -and is discussed at: - -{{URL:http://wiki.wireshark.org/LDAP}} - -It's very interesting to look inside the LDAP Protocol, but please do not try to use this tool -in debugging normal problems. +* Check your logs for errors, as discussed at {{URL:http://www.openldap.org/faq/data/cache/358.html}} H2: Commercial Support