[389-users] Bad Ber tag encountered and IO block timeout logconv.pl

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: Bad Ber tag encountered and IO block timeout logconv.pl
Hello all,

We have been experiencing some ldap timeout errors in a multi-master setup.

My setup looks close to this one but there is _NO_ M32 and M41 i.e consumers don;t replicate to masters
http://www.redhat.com/docs/manuals/dir-server/8.1/deploy/Deployment_Guide-Designing_the_Replication_Process-Common_Replication_Scenarios.html#Deployment_Guide-Multi_Master_Replication-Multi_Master_Replication_Configuration_A_Four_Suppliers

* 2 Supplier servers with multi-master setup between the two.
* 2 consumer servers with multi-master setup between the two.
* Each supplier server has replication setup to each of the two consumer servers.(for redundancy)
* M1 & M2 authenticate users via PAM-PTA plugin to Active Directory.
* M3 & M4 use PTA plugin via SSL to authenticate via M1 & M2 in a redundant fashion.

BIGGEST ISSUE: Clients connecting to M3 and M4 are having “pam_ldap: ldap_result Timed out” error. Any ideas, how we can improve/fix this?

Configuration:
nsslapd-sizelimit: 16384
nsslapd-idletimeout: 7200
nssslapd-maxbersize: 0


Q1. Should I increase my nsslapd-maxbersize?

Q2. How do I restrict the ldap clients to bind only using LDAP v3? (I remembert reading it somewhere)
      LDAP v2 Binds:               1006
      LDAP v3 Binds:               9324

Q3.  I use “uniquemember” as group membership attribute, but logs show filters like this. As far as I know, we don;t have any hard coded filters on any hosts. How to remove filter like this.

(|(member=uid=kcapell,ou=people,dc=domain,dc=com)(uniquemember=uid=kcapell,ou=people,dc=domain,dc=com)(memberuid=kcapell))


I ran logconv.pl on M2 and here is what I found
============================================================================
B1                    75045    Bad Ber Tag Encountered                 
U1                    13456    Cleanly Closed Connections              
T2                      160    IO Block Timeout Exceeded or NTSSL Timeout
T1                       22    Idle Timeout Exceeded                   


69409  10.1.1.2   [ M1 ]     
                 37611 -  B1   Bad Ber Tag Encountered
                   3968 -  U1   Cleanly Closed Connections
                    160 -  T2   IO Block Timeout Exceeded or NTSSL Timeout

55326  10.1.1.3    [ M2 ]      
                  27886 -  B1   Bad Ber Tag Encountered
                      7 -  U1   Cleanly Closed Connections

18096  10.1.0.7     [old ldap server which was using pen-ldap to pass connection during migration ]           
                  9531 -  B1   Bad Ber Tag Encountered
                   8564 -  U1   Cleanly Closed Connections

26     10.101.1.16     [ M3 ]
                    20 -  T1   Idle Timeout Exceeded
                      1 -  B1   Bad Ber Tag Encountered

*      Unknown Host     
                     16 -  B1   Bad Ber Tag Encountered
                     13 -  U1   Cleanly Closed Connections
                      2 -  T1   Idle Timeout Exceeded

 1.  You have unindexed searches, this can be caused from a search on an unindexed attribute, or your returned results exceeded the allidsthreshold.  Unindexed searches are not recommended. To refuse unindexed searches, switch 'nsslapd-require-index' to 'on' under your database entry (e.g. cn=UserRoot,cn=ldbm database,cn=plugins,cn=config).

 2.  You have some connections that are are being closed by the idletimeout setting. You may want to increase the idletimeout if it is set low.

 3.  You have some coonections that are being closed by the ioblocktimeout setting. You may want to increase the ioblocktimeout.

 4.  You have a significant difference between binds and unbinds.  You may want to investigate this difference.

 5.  You have more abnormal connection codes than cleanly closed connections.  You may want to investigate this difference.


===============================================================

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux