Re: ldap startup failure with FC3

On January 2, 2006 20:24, Craig White wrote:
> try chown -R ldap:ldap /var/lib/ldap
>
> add "loglevel 256" to slapd.conf
>
> echo "local4.*                  /var/log/slapd.log" > /etc/syslog.conf
>
> service syslog restart
>
> This will direct all ldap logging to /var/log/slapd.log so you can get a
> better idea
>
> My guess is the first line will solve it...most ldap newbies run slapadd
> as root and thus the data files are owned root:root and ldap will not
> run.
>
> Craig

Hi Again,

Did what you asked and this is the resulted entries in the /var/log/slapd:

[root@server1 openldap]# tail /var/log/slapd.log
Jan 2 21:30:48 server1 slapd[4404]: bdb(dc=example,dc=com): Ignoring log
file: /var/lib/ldap/log.0000000001: magic number 0, not 40988
Jan 2 21:30:48 server1 slapd[4404]: bdb(dc=example,dc=com): Invalid log file:
log.0000000001: Invalid argument
Jan 2 21:30:48 server1 slapd[4404]: bdb(dc=example,dc=com): PANIC: Invalid
argument
Jan 2 21:30:48 server1 slapd[4404]: bdb(dc=example,dc=com): PANIC:
DB_RUNRECOVERY: Fatal error, run database recovery
Jan 2 21:30:48 server1 slapd[4404]: bdb_db_open: dbenv_open failed:
DB_RUNRECOVERY: Fatal error, run database recovery (-30978)
Jan 2 21:30:48 server1 slapd[4404]: backend_startup: bi_db_open(0) failed!
(-30978)
Jan 2 21:30:48 server1 slapd[4404]: bdb(dc=example,dc=com): txn_checkpoint
interface requires an environment configured for the transaction subsystem
Jan 2 21:30:48 server1 slapd[4404]: bdb_db_destroy: txn_checkpoint failed:
Invalid argument (22)
Jan 2 21:30:48 server1 slapd[4404]: slapd stopped.
Jan 2 21:30:48 server1 slapd[4404]: connections_destroy: nothing to destroy.
[root@server1 openldap]#

Don't understand this magic number business... Should I rm the log file and
touch another? What db file is it referencing? This is the listing
of /var/lib/ldap:

[root@server1 ldap]# ls -lR /var/lib/ldap
/var/lib/ldap:
total 20
-rw------- 1 ldap ldap 460613 Jan 2 16:13 log.0000000001
drwxr-xr-x 2 ldap ldap 4096 Jan 2 16:41 replica

/var/lib/ldap/replica:
total 8
-rw-r--r-- 1 ldap ldap 0 Jan 2 16:41 slurpd.status
-rw-r--r-- 1 ldap ldap 0 Jan 2 16:43 slurpd.status.lock
[root@server1 ldap]#

I don't see a db here but I guess there should be one? As you can tell, I am
quit new to this.

Phil

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Does KMail work with LDAP?
    ... after giving the host and DN in LDAP Lookup. ... Additional info: invalid DN ... as both GQ and ldapbrowser can find the server and show its ... the DN field empty and query the server he gets the right DN and puts it in ...
    (comp.windows.x.kde)
  • RE: LDAP api ldap_set_option and LDAP_OPT_AUTO_RECONNECT parameter
    ... LDAP_PARAM_ERROR may be returned if the LDAP ... connection object was invalid. ... Could you also try calling ldap_get_option ...
    (microsoft.public.win32.programmer.networks)
  • Re: ldap_routing and local aliases
    ... Where I am currently is that I am making the LDAP query, ... However, if the address is invalid, the message is still being passed ... Messages to addresses in the local sendmail ...
    (comp.mail.sendmail)
  • ldap_routing and local aliases
    ... I'm running sendmail 8.13.8 on a Debian 3.1 box, and am in the process of implementing ldap_routing to reject mail sent to invalid addresses. ... For this, I'm doing full LDAP queries, and as far as I can tell so far, things are working the way I want them to. ... However, the one problem is that this one completely preempts my aliases list, and local admin addresses that have been defined there, including root, postmaster, mailer-daemon, etc. are being rejected unless defined in LDAP. ... This server has several domains, and I'd really rather not have to go through and have to list all the iterations of admin ids and domains in LDAP. ...
    (comp.mail.sendmail)
Loading