[krbdev.mit.edu #7621] 1.10.5 - iprop full-resync can still result in bad ulog header (reporting current with old data)

[Richard Basch via RT]

Even with 1.10.5, I have just observed a case where a full database resync failed but still resulted in an erroneous setting of the ulog header state.

Apr 23 00:05:06 nyciqla201 kpropd[21900]: /opt/kerberos/current/sbin/kpropd: GSS-API (or Kerberos) error while initializing /opt/kerberos/current/sbin/kpropd interface, retrying
Apr 23 00:07:24 nyciqla201 kpropd[21900]: /opt/kerberos/current/sbin/kpropd: Bad file descriptor while accepting connection
Apr 23 00:07:26 nyciqla201 kpropd[22498]: Connection from nyciqla200.ny.fw.gs.com
Apr 23 00:07:50 nyciqla201 kpropd[22498]: /opt/kerberos/current/sbin/kpropd: /gns/software/infra/ci/kerberos/krb5-1.10.5-1/sbin/kdb5_util returned a bad exit status (2)
Apr 23 00:07:50 nyciqla201 kpropd[21900]: kpropd: Full resync, invalid return.

I will try to investigate other possible code paths which can lead to this condition.

______________________________________________________________________________
Richard Basch
VP, Technology - Critical Infrastructure
30 Hudson St.  24th Floor | Jersey City, NJ 07302
Goldman, Sachs & Co
richard.basch at gs.com<mailto:richard.basch at gs.com>  | +1 (917) 343-4071

P Save a tree: Please don't print this mail unless necessary.

The Goldman Sachs Group, Inc. All rights reserved.
See http://www.gs.com/disclaimer/global_email for important risk disclosures, conflicts of interest and other terms and conditions relating to this e-mail and your reliance on information contained in it.  This message may contain confidential or privileged information.  If you are not the intended recipient, please advise us immediately and delete this message.  See http://www.gs.com/disclaimer/email for further information on confidentiality and the risks of non-secure electronic communication.  If you cannot access these links, please notify us by reply message and we will send the contents to you.