ldapi PATH oddity

[Rich Graves <rcgraves@brandeis.edu>]

openldap 2.2.14 on Linux RedHat Enterprise 3.

I'm doing anonymous simple binds over ldapi:///. On my test machine, 
everything including an ACL based on peername.path="/var/run/ldapi" work.

When I moved it to a production machine, the ACL failed, and logs show 
gibberish IPC PATH like the below.

As far as I can tell, the only difference between the machines is that the
production machine has multiple CPUs. The running binaries, slapd.conf, and
kernel versions seem to be the same.

Jul 29 14:26:38 blanca slapd[22123]: conn=141 fd=19 ACCEPT from PATH=§o\201@c£ (PATH=/var/run/ldapi)
Jul 29 14:28:07 blanca slapd[22123]: conn=157 fd=10 ACCEPT from PATH=¨$\201@c£ (PATH=/var/run/ldapi)
Jul 29 14:51:41 blanca slapd[22123]: conn=466 fd=10 ACCEPT from PATH=´;\201@c£ (PATH=/var/run/ldapi)
Jul 29 15:14:46 blanca slapd[22123]: conn=805 fd=21 ACCEPT from PATH=À®\201@c£ (PATH=/var/run/ldapi)
Jul 29 15:14:51 blanca slapd[22123]: conn=807 fd=22 ACCEPT from PATH=À¹\201@c£ (PATH=/var/run/ldapi)
Jul 29 15:18:33 blanca slapd[22351]: conn=3 fd=10 ACCEPT from PATH=Âç\201@c£ (PATH=/var/run/ldapi)
-- 
Rich Graves <rcgraves@brandeis.edu>
UNet Systems Administrator