[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Update: replog not created anymore ...
Hi all !
Let's see if I can get some variabled out of the way.
First: My 'broken' slave meant: slapcat return 0 lines of information but 1
line which contains an error message. (Yes: What message? ... I don't
remember, but I could retry this night when no users are actively using the
system).
Second: Location in the configuration file. This could be a problem, but it
might be a good idea if slaptest could verify possible broken setups?
bye,
Chris
--- Running slapd.conf ---
# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8 2003/05/24
23:19:14 kurt Exp $
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/cosine.schema
include /usr/local/etc/openldap/schema/nis.schema
include /usr/local/etc/openldap/schema/inetorgperson.schema
include /usr/local/etc/openldap/schema/qmail.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
schemacheck on
pidfile /var/run/slapd.pid
#argsfile //var/run/slapd.args
concurrency 10
threads 10
# Load dynamic backend modules:
# modulepath /usr/sbin/openldap
# moduleload back_bdb.la
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la
# The next three lines allow use of TLS for connections using a dummy test
# certificate, but you should generate a proper certificate by changing to
# /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it.
# TLSCACertificateFile /usr/share/ssl/certs/ca-bundle.crt
# TLSCertificateFile /usr/share/ssl/certs/slapd.pem
# TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem
# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64
# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
# by self write
# by users read
# by anonymous auth
#
# if no access controls are present, the default policy is:
# Allow read by all
#
# rootdn can always write!
#######################################################################
# ldbm and/or bdb database definitions
#######################################################################
loglevel 0
#loglevel 64
database bdb
suffix "o=Slave,c=nl"
rootdn "cn=admin,o=Slave,c=nl"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw password
# rootpw {crypt}ijFYNcSNctBYg
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /usr/local/var/lib/ldap
# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub
# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 tls=yes
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example.com@EXAMPLE.COM
lastmod on
# /*
# * Systeem monitoring aanzetten
# */
#database monitor
# /*
# * Replicatie instellingen naar slave-ldap server
# */
replogfile /usr/local/var/lib/ldap/replog
replica host=mail3.slave.nl bindmethod=simple binddn=cn=admin,o=slave,c=nl
credentials=password tls=no
# /*
# * ACL definities
# */
#access to attribute=userPassword
access to dn.regex="^cn=[^,]+,ou=BBO-People,o=slave,c=nl$"
attrs=userPassword
by dn="cn=admin,o=slave,c=nl" write
by self write
by anonymous auth
by * none
# The admin dn has full write access
access to dn.regex="^.*$"
by dn="cn=admin,o=slave,c=nl" write
by * read
# The admin dn can ask for statistics
#access to dn.subtree="cn=Monitor"
# by dn.exact="cn=admin,o=slave,c=nl" write
# by users read
# by * none
# End of config
----- Original Message -----
From: "Howard Chu" <hyc@symas.com>
To: "Quanah Gibson-Mount" <quanah@stanford.edu>
Cc: "Christiaan den Besten" <chris@scorpion.nl>;
<OpenLDAP-software@OpenLDAP.org>
Sent: Tuesday, October 26, 2004 11:06 AM
Subject: Re: Update: replog not created anymore ...
Quanah Gibson-Mount wrote:
--On Tuesday, October 26, 2004 12:16 AM -0700 "Kurt D. Zeilenga"
<Kurt@OpenLDAP.org> wrote:
I note that (in regards to 1) one cannot expect monitor backend
to create replog entries and (in regards to 2) its unclear exact
what is meant by "corruption" (could just be an out-of-date
slave). Doesn't seem to be enough information here to file
a good ITS yet.
However, in reading the man page for slapd.conf, "replogfile" is not a
per-db directive (at least not according to the 2.2.17 manpage), which
means that it shouldn't matter where in the configuration file the
"replogfile" statement is put, which sounds like a bug to me. Either the
documentation is wrong, or slapd isn't behaving correctly.
--Quanah
Hm, in my copy of the 2.2 manpage, replogfile is listed in the General
Database Options section, not the Global Configuration Options section.
That means it is indeed database-specific (but independent of database
type), and its position in the conf file is significant.
I agree with Kurt, there isn't enough context provided to see where the
real problems are, but it is doubtless an error in the config file.
--
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support