Re: printing binary UUIDs

[Aaron Richton <richton@nbcs.rutgers.edu>]

Well, I spoke too soon; the syncrepl wrongly deleting MODs is still
present, just less frequent, in 2.3.20. My previous simple reproduction IS
fixed (it now takes TWO replication cycles), but the issue as a whole is
not gone.

So I find myself back to wanting to track UUIDs for debugging purposes. I
have -d -1 of a syncrepl slave going wrong:

ber_dump: buf=0x00737b30 ptr=0x00737b30 end=0x00737b6a len=58
  0000:  02 01 03 79 35 80 18 31  2e 33 2e 36 2e 31 2e 34   ...y5..1.3.6.1.4
  0010:  2e 31 2e 34 32 30 33 2e  31 2e 39 2e 31 2e 34 81   .1.4203.1.9.1.4.
  0020:  19 a3 17 01 01 ff 31 12  04 10 fd 32 58 62 98 b7   ......1....2Xb..
  0030:  10 29 8d 09 ac 51 70 9f  7b dd                     .)...Qp.{.

and I'm pretty sure that there's a UUID set in there somewhere. If I'm
understanding the I-D correctly, this part has the UUID set:

ber_scanf fmt ([W]) ber:
ber_dump: buf=0x005d7150 ptr=0x005d7155 end=0x005d7169 len=20
  0000:  31 12 04 10 fd 32 58 62  98 b7 10 29 8d 09 ac 51   1....2Xb...)...Q
  0010:  70 9f 7b dd                                        p.{.


Once again, my question is how to get from there to
"fd325862-98b7-1029-8d09-ac51709f7bdd" (i.e. the form output by slapcat).
I've tried using the perl snippet that Luke mailed the last time I asked
this, but everything I get out of it has no match in my database, which
either means slapd is sending complete garbage (very unlikely given the
context in the debug log) or I'm doing it wrong. So, I apologize for
asking for a brute force "I don't get it," but......I don't get it.
(And I'm pretty sure this isn't in the Admin Guide. :)
How do I correlate my entries in slapcats to these ber_dumps?