X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7E9BA.FD6765C8@onstor-exch02.onstor.net>; Tue, 28 Aug 2007 13:32:52 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E9BA.FD6765C8"
Content-class: urn:content-classes:message
Subject: RE: LDAP errors
Date: Tue, 28 Aug 2007 13:32:51 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E053A9DB4@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E053A9C23@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LDAP errors
Thread-Index: Acfpnn6Swc4WaI/ESa2gEZxF5U+YcQAHFc1Q
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Rich LaReau" <rich.lareau@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7E9BA.FD6765C8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As discussed in our cubicles, from the code I'm guessing this is
OpenLDAP choking on a value we got from the LDAP server.

> _____________________________________________=20
> From: 	Rich LaReau =20
> Sent:	Tuesday, August 28, 2007 11:09 AM
> To:	dl-cstech
> Subject:	LDAP errors
>=20
>=20
> We have a customer whose log files are filling up with these errors,
> preventing us from capturing other critical events.  Is there any way
> to suppress such logs?  Or better yet, can we tell from the errors
> what we could fix to keep them from happening?
>=20
> Thanks!
> Rich
>=20
> Aug 28 17:20:18 oponstor01a : 0:0:auth_agent:INFO:
> nfxldap_getValues[1476]: Failed to extract values for
> attribute=3DgidNumber. VS=3D3, err=3DDecoding error(-4)
>=20
> Aug 28 17:20:18 oponstor01a : 0:0:auth_agent:INFO:
> nfxldap_queryPrepareRsp[524]: No values returned for
> attribute=3DgidNumber. VS=3D3, qClass=3D125, qKey=3D*
>=20
>=20

------_=_NextPart_001_01C7E9BA.FD6765C8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: LDAP errors</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">As discussed in our cubicles, from the =
code I'm guessing this is OpenLDAP choking on a value we got from the =
LDAP server.</FONT></P>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Rich LaReau&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Tuesday, August 28, 2007 11:09 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-cstech</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">LDAP errors</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have a customer whose log files are =
filling up with these errors, preventing us from capturing other =
critical events.&nbsp; Is there any way to suppress such logs?&nbsp; Or =
better yet, can we tell from the errors what we could fix to keep them =
from happening?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks!</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Rich</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Aug 28 17:20:18 oponstor01a : =
0:0:auth_agent:INFO: nfxldap_getValues[1476]: Failed to extract values =
for attribute=3DgidNumber. VS=3D3, err=3DDecoding error(-4)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Aug 28 17:20:18 oponstor01a : =
0:0:auth_agent:INFO: nfxldap_queryPrepareRsp[524]: No values returned =
for attribute=3DgidNumber. VS=3D3, qClass=3D125, qKey=3D*</FONT></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C7E9BA.FD6765C8--
