Ah, forgot to add some logs:
/var/log/syslog | grep krb5 (for the time writing the bug report):
Jan 9 20:34:56 hel krb5kdc[354]: Unable to access Kerberos database -
while initializing database for realm MGR
Jan 9 20:34:56 hel krb5kdc[354]: Unable to access Kerberos database -
while initializing database for realm MGR
Jan 9 20:36:03 hel krb5kdc[682]: setting up network...
Jan 9 20:36:03 hel krb5kdc[682]: setting up network...
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 11: udp 127.0.0.1.88
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 11: udp 127.0.0.1.88
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 12: udp 127.0.0.1.750
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 12: udp 127.0.0.1.750
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 13: udp 172.16.6.3.88
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 13: udp 172.16.6.3.88
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 14: udp 172.16.6.3.750
Jan 9 20:36:03 hel krb5kdc[682]: listening on fd 14: udp 172.16.6.3.750
Jan 9 20:36:03 hel krb5kdc[682]: set up 4 sockets
Jan 9 20:36:03 hel krb5kdc[682]: set up 4 sockets
Jan 9 20:36:03 hel krb5kdc[683]: commencing operation
Jan 9 20:36:03 hel krb5kdc[683]: commencing operation
Jan 9 21:13:09 hel krb5kdc[683]: Interrupted system call - while
selecting for network input(1)
Jan 9 21:13:09 hel krb5kdc[683]: Interrupted system call - while
selecting for network input(1)
Jan 9 21:13:09 hel krb5kdc[683]: shutting down
Jan 9 21:13:09 hel krb5kdc[683]: shutting down
I guess the first two entries are the reason, why the autostart fails.
After a short look to /etc/rc3.d this is clear: S18krb5-kdc, S19slapd
(same problems would arise with bind9 and LDAP backend). Is this
something to report to the LDAP maintainers?
Interestingly none of the entries relate to the offending process 687. I
checked the situation now, after restarting the KDC. This suggests that
683 had been /usr/sbin/krb5kdc, and 682 was not running. Now I have the
following situation:
Jan 9 21:13:09 hel krb5kdc[843]: set up 4 sockets
Jan 9 21:13:09 hel krb5kdc[843]: set up 4 sockets
Jan 9 21:13:09 hel krb5kdc[844]: commencing operation
Jan 9 21:13:09 hel krb5kdc[844]: commencing operation
844 ? Ss 0:00 /usr/sbin/krb5kdc -4none
858 ? Ss 0:00 /usr/sbin/krb524d -m
krb524d 858 root 130u IPv4 163255 TCP
hel.mgr:35084->hel.mgr:ldaps (ESTABLISHED)
(105 sockets at 21:33: 5 sockets per minute!)
/var/log/messages:
nothing in the relevant interval
/var/log/auth.log:
Jan 9 20:36:03 hel krb524d[685]: No dictionary file specified,
continuing without one.
Jan 9 20:36:03 hel krb524d[685]: service entry `krb524' not found,
using 4444
Regards,
- lars.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
