Andrew Reid <[EMAIL PROTECTED]> writes:
> I've had a chance to experiment a little more, and it's
> clear that what is crashing the kadmind is a second or
> subsequent kpasswd attempt for a given principal a short
> time after a (successful) first change.
> It's as though there's some time window after a kpasswd
> invocation on a principal during which additional kpasswd
> invocations will crash the server's admin daemon. It
> seems to be independent of the particular principal or
> client machine.
Apologies for the delay in responding to this bug report.
The next step would be to see if you can get a core dump from kadmind so
that we can figure out just where it's dying. Unfortunately the syslog
messages don't help much there. Can you make sure that core dumps are
enabled and core dump size is unlimited (with ulimit -c unlimited) and
restart kadmind to try to get a core dump from the next time this happens?
Then:
gdb /usr/sbin/kadmind core
backtrace
should at least give us an idea of where this is going wrong, although
unfortunately since the kadmind in Debian is stripped, we won't get full
symbol information.
I can also forward this bug upstream and see if the upstream developers
have any idea what might be causing it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
