Skip Menu |

To: krb5-bugs@MIT.EDU
Subject: kdb5_util load now fails if db doesn't exist [workaround]
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Fri, 30 Jun 2006 21:40:09 -0400
After the recent quick hacks to make kdb5_util load work with an
existing database (and thus make kpropd work), it looks like loading
from a dump file doesn't work if the database hasn't already been

load: cannot create database /tmp/aa/principalx (KADM5 administration database lock file missing)

I think it's also likely to leave things in a state where temporary
files are left around and may cause it to get even less far the next

The workaround is simple: Use "kdb5_util create" to create a database
(populated with the basics like K/M), then load your dump file. And
if you've got a bunch of temporary files like "principal~.kadm5", just
delete them and try again.

This was fixed in 1.8 as a side-effect of the account lockout support.
(Account lockout touched on dump/load in order to avoid loading non-
replicated attributes.)