Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.427 (Entity 5.427) From: tlyu@mit.edu Subject: git commit RT-Send-CC: X-RT-Original-Encoding: iso-8859-1 Content-Length: 840 Check for unstable ulog in ulog_get_entries If a process terminates in the middle of a logged database update, it will release its lock and leave the ulog in the KDB_UNSTABLE state. kadmind should notice this when it calls ulog_get_entries, but right now it only checks for the KDB_CORRUPT state (which is never set any more) and does not recover. Check for any state other than KDB_STABLE and recover by resetting the ulog and forcing full resyncs to slaves. (cherry picked from commit 91ef7d4c3f892b99630422a71780788f2d1c04d7) https://github.com/krb5/krb5/commit/ac93fc8f231f4dc152dcd24e7277dde12d595efe Author: Greg Hudson Committer: Tom Yu Commit: ac93fc8f231f4dc152dcd24e7277dde12d595efe Branch: krb5-1.12 src/lib/kdb/kdb_log.c | 10 ++++------ 1 files changed, 4 insertions(+), 6 deletions(-)