grouper-users - Re: [grouper-users] Random ldappc failures
Subject: Grouper Users - Open Discussion List
List archive
- From: Tom Zeller <>
- To: Paul Engle <>
- Cc:
- Subject: Re: [grouper-users] Random ldappc failures
- Date: Tue, 21 Jul 2009 10:27:13 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=uMn04GC8VKLcXNgrbX3PBKsXSkHKhrgcDeaWFBSVU/1ceYh6JtYqBrcEkTeDFDXmGR wViBnGSR/u9EvewNiUgioMkwLzTEcFKP8912+4g1OtocDMfNLxO4UZy8DqkPc/OiCNuD fy2tHIT9hNSPnqi2ryr3Asr3HX5g/bk/DwUTs=
Obvious, but, you should see grouper querying postgres for the
groups-to-be-provisioned. I think you'll need log_statement = all in
postgresql.conf.
I (or you for that matter :-) could add extra logging statements to
the code and build a new jar. Does that sound interesting ?
On Tue, Jul 21, 2009 at 8:30 AM, Paul
Engle<>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> - --On Monday, July 20, 2009 1:21 PM -0500 Paul Engle
> <>
> wrote:
>
>> I'm not seeing any timeouts or other error indications in the
>> ldap error logs. The ldap access logs for the last failure
>> have already rolled off, but I'll try to catch the next one
>> and hold it to see if I'm getting any empty search results
>> or the like.
>>
>
> - From last night's logs, it sure looks like it's just not even
> talking to the ldap server before the failure, other than to do
> its initial auth.
>
> On a normal interval, I see the following ldap activity:
>
> 1. no-op bind/unbind as grouper user (presumably to check auth)
> 2. bind; search for (&(cn=GrouperSystem)) [no results]; unbind
> 3. bind; search for
> (&(uid=GrouperSystem)(objectClass=riceEduPerson)) [no results];
> unbind
> 4. bind;
> search for
> (!(|(objectClass=groupOfUniqueNames)(objectClass=organizationalUnit)))
> [no results];
> search for (objectClass=groupOfUniqueNames) [28242 results];
> search for (objectClass=organizationalUnit) [9541 results];
> unbind;
>
> On a failed run, I see only the first three binds. Not even an
> attempt to bind and search the provisioning base for the
> existing data.
>
> I don't know if that's at all helpful. I'll see if I can get
> anything from the postgresql logs.
>
> -paul
>
>
>
> - --
> Paul D. Engle | Rice University
> Sr. Systems Administrator | Information Technology - MS119
> (713)348-4702 | PO Box 1892
>
> | Houston, TX 77252-1892
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
>
> iD8DBQFKZcMHCpkISWtyHNsRAgxEAJ9p02z48oxUln9xQoCI5R/qw9aE2ACghoiJ
> bznqRCNMtXCLMYCMz04oKkw=
> =OQWb
> -----END PGP SIGNATURE-----
>
>
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/20/2009
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/20/2009
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/21/2009
- Message not available
- Message not available
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/21/2009
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/22/2009
- Re: [grouper-users] Random ldappc failures, Tom Barton, 07/22/2009
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/24/2009
- Message not available
- Message not available
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/25/2009
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/29/2009
- RE: [grouper-users] Random ldappc failures, Chris Hyzer, 07/29/2009
- RE: [grouper-users] Random ldappc failures, Paul Engle, 07/29/2009
- Message not available
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/29/2009
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/25/2009
- RE: [grouper-users] Random ldappc failures, Chris Hyzer, 07/31/2009
- Message not available
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/22/2009
- Re: [grouper-users] Random ldappc failures, Tom Zeller, 07/21/2009
- Message not available
- Re: [grouper-users] Random ldappc failures, Paul Engle, 07/20/2009
Archive powered by MHonArc 2.6.16.