$ sudo dpkg-reconfigure krb5-kdc [interactive configuration prompts] debconf: warning: possible database corruption. Will attempt to repair by adding back missing question krb5-kdc/debconf.
So reconfiguring krb5-kdc would have and did fix it. I wonder if my diet-upgrade broke at some point and I didn't notice? As I recall, I was following this guide: https://www.linode.com/docs/security/upgrading/upgrade-to-debian-8-jessie And my upgrade failed first during this install: sudo apt-get install apt dpkg aptitude I *think* that I first had krb5-admin-server break during *that* install; but maybe I'm misremembering, and I lost an ssh session or something. I also *thought* that I had done this: dpkg-reconfigure debconf for pkg in $(dpkg-query --show | awk '{print $1}'); do echo ; echo "--> $pkg" ; echo ; dpkg-reconfigure --frontend=noninteractive --priority=critical $pkg < /dev/null ; done but thinking about it more now, there's no way I c/p'd that command into my terminal without parsing it thoroughly, and it doesn't seem familiar to me now. ~jonathon On Wed, May 13, 2015 at 11:36 AM, Benjamin Kaduk <ka...@mit.edu> wrote: > On Wed, 13 May 2015, Jonathon Anderson wrote: > >> Maybe I should have done debconf reconfigure on krb5-kdc? (In stead of >> admin?) > > Please try that, yes. > > We should still try to run the dist-upgrade on our end and see if we can > reproduce the breakage, too. > > -Ben Kaduk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
