slapd should start before kerberos kdc and admin servers, possibly others

Bug #445619 reported by Andreas Hasenack on 2009-10-07
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
openldap (Ubuntu)
Low
Unassigned

Bug Description

slapd 2.4.18-0ubuntu1
krb5-kdc-ldap 1.7dfsg~beta3-1
bind9 1:9.6.1.dfsg.P1-3
dhcp3-server 3.1.2-1ubuntu5

Currently in Karmic, we have slapd starting at 19 and the mit kerberos admin and kdc servers at 18.

If the kerberos server is using the openldap backend, it will fail to start:
Oct 7 11:54:15 maestro kadmind[1101]: Unable to access Kerberos database while initializing, aborting
Oct 7 11:54:15 maestro krb5kdc[1112]: Can't contact LDAP server - while initializing database for realm EXAMPLE.COM

slapd started slightly after (only 1s resolution in the logs):
Oct 7 11:54:15 maestro slapd[1133]: @(#) $OpenLDAP: slapd 2.4.18 (Sep 8 2009 17:46:15) $#012#011buildd@palmer:/build/buildd/openldap-2.4.18/debian/build/servers/slapd
Oct 7 11:54:15 maestro slapd[1133]: PROXIED attributeDescription "OU" inserted.
Oct 7 11:54:15 maestro slapd[1133]: PROXIED attributeDescription "DC" inserted.
Oct 7 11:54:16 maestro slapd[1134]: slapd starting

While we are at it, the same could happen with bind9 if using the ldap dynamic zone (dlz), but I don't know if it would prevent bind from starting (as was the case with kerberos):
root@maestro:~# l /etc/rc*.d/S*bind*
lrwxrwxrwx 1 root root 15 2009-09-09 17:18 /etc/rc2.d/S15bind9 -> ../init.d/bind9
lrwxrwxrwx 1 root root 15 2009-09-09 17:18 /etc/rc3.d/S15bind9 -> ../init.d/bind9
lrwxrwxrwx 1 root root 15 2009-09-09 17:18 /etc/rc4.d/S15bind9 -> ../init.d/bind9
lrwxrwxrwx 1 root root 15 2009-09-09 17:18 /etc/rc5.d/S15bind9 -> ../init.d/bind9

dhcp seems fine (it can also use ldap):
root@maestro:~# l /etc/rc*.d/S*dhcp*
lrwxrwxrwx 1 root root 22 2009-09-09 17:18 /etc/rc2.d/S40dhcp3-server -> ../init.d/dhcp3-server
lrwxrwxrwx 1 root root 22 2009-09-09 17:18 /etc/rc3.d/S40dhcp3-server -> ../init.d/dhcp3-server
lrwxrwxrwx 1 root root 22 2009-09-09 17:18 /etc/rc4.d/S40dhcp3-server -> ../init.d/dhcp3-server
lrwxrwxrwx 1 root root 22 2009-09-09 17:18 /etc/rc5.d/S40dhcp3-server -> ../init.d/dhcp3-server

summary: - [karmic] slapd should start before kerberos kdc and admin server
+ [karmic] slapd should start before kerberos kdc and admin servers
summary: - [karmic] slapd should start before kerberos kdc and admin servers
+ [karmic] slapd should start before kerberos kdc and admin servers,
+ possibly others

Agreed. The init script will be probably be moved to upstart jobs, which should make these dependencies easy to support.

Changed in openldap (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Ro (robert-markula) wrote :

Hmm, this problem is still present in Lucid. One can easily change the order manually though, e.g:

update-rc.d -f krb5-admin-server remove
update-rc.d -f krb5-kdc remove
update-rc.d krb5-admin-server start 20 2 3 4 5 . stop 18 0 1 6 .
update-rc.d krb5-kdc start 20 2 3 4 5 . stop 18 0 1 6 .

Andreas Ntaflos (daff) wrote :

This is still a problem, both in Lucid and Precise.

summary: - [karmic] slapd should start before kerberos kdc and admin servers,
- possibly others
+ slapd should start before kerberos kdc and admin servers, possibly
+ others
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers