I just wanted to note that in my environment, this is happening many times a day. I run the kdc through runit, so things get restarted immediately, but something is clearly wrong:
2011-05-27_11:21:32.11310 krb5kdc: starting... 2011-05-27_11:22:01.99218 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_11:22:02.01489 krb5kdc: starting... 2011-05-27_11:22:34.82072 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_11:22:34.84385 krb5kdc: starting... 2011-05-27_11:23:04.85051 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_11:23:04.87166 krb5kdc: starting... 2011-05-27_13:41:47.11749 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:41:47.13390 krb5kdc: starting... 2011-05-27_13:42:15.83151 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:42:15.84522 krb5kdc: starting... 2011-05-27_13:42:17.12465 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:42:17.14709 krb5kdc: starting... 2011-05-27_13:42:47.15550 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:42:47.16933 krb5kdc: starting... 2011-05-27_13:42:59.14972 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:42:59.17231 krb5kdc: starting... 2011-05-27_13:43:21.32805 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:43:21.33698 krb5kdc: starting... 2011-05-27_13:43:29.18399 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:43:29.20055 krb5kdc: starting... 2011-05-27_13:43:51.35396 krb5kdc: ../../../../../src/plugins/kdb/ldap/libkdb_ldap/lockout.c:178: krb5_ldap_lockout_audit: Assertion `!locked_check_p(context, stamp, max_fail, lockout_duration, entry)' failed. 2011-05-27_13:43:51.38001 krb5kdc: starting...
Any idea what the assertion is trying to prevent? Should I contact the upstream developers?
I just wanted to note that in my environment, this is happening many times a day. I run the kdc through runit, so things get restarted immediately, but something is clearly wrong:
2011-05- 27_11:21: 32.11310 krb5kdc: starting... 27_11:22: 01.99218 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_11:22: 02.01489 krb5kdc: starting... 27_11:22: 34.82072 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_11:22: 34.84385 krb5kdc: starting... 27_11:23: 04.85051 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_11:23: 04.87166 krb5kdc: starting... 27_13:41: 47.11749 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:41: 47.13390 krb5kdc: starting... 27_13:42: 15.83151 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:42: 15.84522 krb5kdc: starting... 27_13:42: 17.12465 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:42: 17.14709 krb5kdc: starting... 27_13:42: 47.15550 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:42: 47.16933 krb5kdc: starting... 27_13:42: 59.14972 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:42: 59.17231 krb5kdc: starting... 27_13:43: 21.32805 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:43: 21.33698 krb5kdc: starting... 27_13:43: 29.18399 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:43: 29.20055 krb5kdc: starting... 27_13:43: 51.35396 krb5kdc: ../../. ./../.. /src/plugins/ kdb/ldap/ libkdb_ ldap/lockout. c:178: krb5_ldap_ lockout_ audit: Assertion `!locked_ check_p( context, stamp, max_fail, lockout_duration, entry)' failed. 27_13:43: 51.38001 krb5kdc: starting...
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
2011-05-
Any idea what the assertion is trying to prevent? Should I contact the upstream developers?