Kerberos.umbc.edu was "Hung" for a time (still responding to pings, just not doing much) from 4pm on Dec 18 until approximatly 9:30pm. It is unknown why it was hung, just that it was -- no diagnostics on the console or logs. Services that required the backwards-compatible rxKa authentication for older AFS client installs, and password changes, did not work during this time. In addition, it was noticed that the principal database on the secondary KDC hadn't been updated in some time. Logs showed that it hadn't been updated since November 8; seems that 'cron' on kerberos2 had packed it in as well. Well, it has been up for 450+ days.