This is interesting since I have a setup here with exactly the same
issue. Side notes :
The directory is ADAM, the problem only appears in large data sets
being returned over SSL (regular LDAP on 389 works OK). I'm beginning
to think that it's related to specific entries since a couple of
times it's died on the same object, but that may just be chance. But
the consistent signature is the 00 84 where I'm expecting a 30 84.
Entry that works :
Net::LDAPS=HASH(0x1db33b8) received:
30 84 00 00 01 B5 02 01 02 64 84 00 00 01 AC 04 0........d......
49 43 4E 3D 4E 61 73 73 69 72 61 20 43 68 69 6B ICN=Nassira Chik
68 2C 4F 55 3D 45 58 43 48 41 4E 47 45 32 30 30 h,OU=EXCHANGE200
but dies on the next entry:
Net::LDAPS=HASH(0x1db33b8) received:
00 84 00 00 01 A7 02 01 02 64 84 00 00 01 9E 04 .........d......
47 43 4E 3D 44 61 76 69 64 20 4C 75 63 61 73 2C GCN=David Lucas,
4F 55 3D 45 58 43 48 41 4E 47 45 32 30 30 30 2C OU=EXCHANGE2000,
I'm going to double check the ASN1 version, but I seem to remember
that it was updated relatively recently.
Cheers,
Erik
Le 16 juin 06 à 19:58, Si Smith a écrit :
OK, I got back to the rig and had a play with it again (I can
reproduce this error on another installation too - seems only
to affect large directory fetches and sometimes can be avoided
by using a small 'page' size ( say 5 entries ).
All libraries are up to date.
The SSLeay trace level was set to 4 (dump data). Unfortunately the
dump is in binary not text and it is difficult to correlate this
with the LDAP debug output. I will have a play and add some more
diagnostics to the code to see if I can get to the bottom of this
( 300Mb log files on a VM do not make for lightening fast
diagnostics :-) ).
Si
Chris Ridd wrote:
On 19/5/06 1:44, Simon P Smith <[EMAIL PROTECTED]> wrote:
Chris Ridd wrote:
On 15/5/06 3:26, Si Smith <[EMAIL PROTECTED]> wrote:
So instead of starting "30 84 00 00" the bad record
starts "00 84 00 00".
Does this make any sense?
It does, and it explains the LDAP_DECODING_ERROR. Now, why is it
happening...
What version of Convert::ASN1 are you using?
Perl 5.8.6 ( ActivState Win32 811 on one machine 816 on another )
Convert::ASN1 Version 0.18 ( CVS 1.29 )
(ahh, I see that there is a ppd for 0.20 I guess this is
a recommended action before carrying on?)
Yeah, there were some bugs fixed there relating to UTF-8 and
'bytes', which
*could* be what you're seeing. Graham's suggestion of getting
Net::SSLeay's
idea of the bytes is an excellent one too.
Cheers,
Chris
