Hello Tom, yes correct, Kadmin.local will get database lock only after restarting KDC.
But I can see KDC issues tickets, but "kadmin.local" fails. kadmin.local fails with message "Cannot lock database while changing password for" (I saw this for create/delete priciple operations swell ) Thanks, Abhilash On Tue, Aug 14, 2012 at 10:04 AM, Tom Yu <[email protected]> wrote: > Abhilash S <[email protected]> writes: > > > Hello Tom, > > > > Version and OS: > > we have kerberos 1.9.2 version. > > It is running under Linux (x86_64 GNU/Linux). > > > > KDC Traffic : > > we do have heavy kadmin traffic. > > we used to get avg or 4-7 Authentication request per > second > > For updating kerberos database , we have a java code which forks > > "kadmin.local" utility , and uses kdc commands to > > create/modify/delete principals, > > > > This doesn't happens regularly but we gets this error at least 10 to 15 > per > > month. > > Principle file size will be around 1.3G. > > Thanks. You sent another message that contained the following: > > > I am seeing this occurring quite frequently, only workaround is to > restart > > the kris deamons > > is there any patch or workaround available to get rid of this error. > > > > I saw few update on this bug over here, > > https://bugzilla.redhat.com/show_bug.cgi?id=586032 > > When you say you have to restart the daemon, is this because > subsequent runs of kadmin.local couldn't get a database lock until > after you restart the KDC? > -- Thanks & Regards, Abhilash.S ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
