- openldap-bugs - openldap.org

Re: (ITS#7638) Handle connection loss in SQL backend
by pierre＠reactos.org 08 Jul '13

08 Jul '13

This is a cryptographically signed message in MIME format. --------------ms090404050901070205030703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Unfortunately, I don't see any other solution. I browsed everything I=20 could in ODBC doc, in order to be able to query link status, but there's = no way. And the other solution to redo the whole statement in case of failure=20 would be even more complex and would require too many code rewrites due=20 to a complete logic change. So, it seems to me to be the intermediate=20 solution. The overhead being limited on "decent" connection. Regards, On 07/07/2013 14:33, Michael Str=F6der wrote: > pierre(a)reactos.org wrote: >> With this patch, before preparing any req on the given connection=20 >> handle, the >> backend will first try to check whether the connection is active by=20 >> issue a >> dummy query. In case it's not, it will close the previous connection=20 >> and open a >> new one. And then, will prepare the req on the connection link. >> >> I made this choice of developement because, preparing statement,=20 >> executing it >> and then, only looking whether it fails to re-submit would have been=20 >> more >> complex, since it would have required to start over the whole process = >> for the >> query (statement preparation and such) while preparation & execution=20 >> aren't not >> in the same function. > > Hmm, so there's an extra dummy query for each real query. If the SQL=20 > DB is connected over network this means a synchronous extra round trip = > for each query. > > Ciao, Michael. > > --=20 Pierre Schweitzer<pierre at reactos.org> System Administrator ReactOS Foundation --------------ms090404050901070205030703 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMuTCC BjQwggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3 MTAyNDIxMDI1NVoXDTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOM KqANy9BV7V0igWdGxA8IU77L3aTxErQ+fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi 8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8M DP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHksw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y 2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHHtOkzUreG//CsFnB9+uaYSlR65cdG zTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd+q9rMfPIHeOsuzAfBgNV HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0 dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93 d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqp Jw3I07QWke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Mic c/NXcs7kPBRdn6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9Jphw UPTXwHovjavRnhUQHLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMc p+reg9901zkyT3fDW/ivJVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT +HBDYtbuvexNftwNQKD5193A7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1X hwby6mLhkbaXslkVtwEWT3Van49rKjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvO hNz/QplNa+VkIsrcp7+8ZhP1l1b2U6MaxIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC 0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqh AChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H75dVCV33K6FuxZrf09yTz+Vx/PkdRUYk XmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIGfTCCBWWgAwIBAgICKTswDQYJKoZIhvcNAQEF BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD bGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMjExMjEyMDMyNTZa Fw0xNDExMjMwNzI4NTRaMIGZMRkwFwYDVQQNExBBTUdwaXREYlFMMTNWNzBhMQswCQYDVQQG EwJGUjEYMBYGA1UECBMPSGF1dGUtTm9ybWFuZGllMRYwFAYDVQQHEw1Nb250aXZpbGxpZXJz MRowGAYDVQQDExFQaWVycmUgU2Nod2VpdHplcjEhMB8GCSqGSIb3DQEJARYScGllcnJlQHJl YWN0b3Mub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs6df8jj7p6qV61Nt KQTvsBSsxDKWF1artqGRgk4xj5wxuPcBn7Couffu1uoO/HE8gU6JIcac+Yy9gHnZmVak91qR 6BMXdMZmS4Pw42J1v9jUIps0uLCUL+ERIgC6Czrnr+RVGyL49ybXsUjq0SMGpM65K7W3hc6l 52R94XIDDZX5tSC8ykvnnsgDv8A4YubKhJYTO3G285Dw2gcIxf/Zg1AE7fBCAx+Eahqly7DP MEP1tH66Xs9jUXwWH/LuuHh1qCEOMeVf2QiiFVa1DqY5bWaRJFmOHsSJ/UVA+o/fF3MWpDZy xLnf2Ia4cUW4D0xP6po0BJLxg3J7Zz83K3dH1QIDAQABo4IC2DCCAtQwCQYDVR0TBAIwADAL BgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSj smXI/ofbH9TM2n4vCg+ffljF9jAfBgNVHSMEGDAWgBSuVYNv7DHKufcd+q9rMfPIHeOsuzAd BgNVHREEFjAUgRJwaWVycmVAcmVhY3Rvcy5vcmcwggFMBgNVHSAEggFDMIIBPzCCATsGCysG AQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9s aWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRo b3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8g dGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29tIENB IHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAr oCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFz czIvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0 cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFy dHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCFeXbRYRXSXj+qOhO84ZVGZXb6YQ9NEp2A 3nFDOJke+FH2id3lkuWYze89znDRekvta51EhuLtgpwK2AmWQqnN6NoCuAjJNRBZ+/NourxM S8nn+pyFFTXBbErFAHIO6iOZw0voScHJXfodxPfwc5aP5HTWasbszXzG1Q4uwtj6ZcTU5r0a 21Gt5bBb58II39yk8/mWuxI+gTUgbAt67cMvdJGH0aEZc9XTSKSYRp3kXtBeQ23LMJnxAjIo q/Q8vaCMb6EHJ6Kkz0Fdmxjxpqg+Dop1YtgaaDspSY0f2qkrxhwqGpSXfk+Du8YDXqD2nMCi qoQTrGpdI6q2d5i0PM2sMYICiTCCAoUCAQEwgZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRl IENsaWVudCBDQQICKTswCQYFKw4DAhoFAKCByzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB MBwGCSqGSIb3DQEJBTEPFw0xMzA3MDgxNzI5NDJaMCMGCSqGSIb3DQEJBDEWBBSp4weucVM5 IASlCKMvHRpm39/eKzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQME AQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIH MA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIIBAHaoWj/CjXJf1TfekN650kEwojD+ 0HYA3EV5/s6SYHeaOi8ZM1bd6ykJGEd6ehajWoW12jBXq+ibH5QcO6hv49nxMNGpZ5m1dF1w 7yTs3X1ZaZx0A5UfmYMS8Hk2nxgiO/IG0K07CEJiMfggEBP5JdeMdlhmdMJv5TmV+lnIiIeI jH06JJXDVq33qFRdFt0CbaOISDlddXp9/OEtHHp818TiD9Vh12v/jqzD8BxHQr0+zDFoPZPY 2f30Donz/mj/cWWBBmuVCrULgW8fL59BM02MaX6O9BdAb1paBVvAVXy/TkuwzlRPu4yo8rew H2iLVVcdyL+DGqCGqoZiLYAym4kAAAAAAAA= --------------ms090404050901070205030703--

1 0

(ITS#7639) test062-config-delete intermittently succeeds
by rsbx＠acm.org 07 Jul '13

07 Jul '13

Full_Name: Raymond S Brand Version: 60720f5d9cdc19092d0aad6b0a94e196e5525d1c OS: Debian Wheezy amd64 URL: Submission from: (NULL) (50.88.155.14) When run with the bdb, hdb, and mdb backends, test062-config-delete intermittently succeeds but more often than not it fails. It is the only test that has failed in my testing. Test system, a VirtualBox instance: Linux LDAP 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux 2 VCPUs; 1.5GB VirtualBox host system: Linux LDAP 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux 2 CPUs (Core 2 Duo); 8GB Both O/S's are current with respect to Debian updates. Build options: ../../configure --prefix=/tmp/ol --enable-perl --enable-overlays --enable-bdb When run with full logging, the last line of the server log file appeared to be corrupted. This is a sample run: XXXX$ ./run -b mdb test062-config-delete Cleaning up test run directory leftover from previous run. Running ../../../tests/scripts/test062-config-delete for mdb... running defines.sh Starting slapd on TCP/IP port 9011... /home/internet/Projects/OpenLDAP/openldap/BUILD/t2/tests Using ldapsearch to check that slapd is running... Waiting 5 seconds for slapd to start... Inserting syncprov overlay ... Starting a refreshAndPersist search in background Removing syncprov overlay again ... Waiting 2 seconds for RefreshAndPersist search to end ... Checking return code of backgrounded RefreshAndPersist search ... Exit code correct. Running a refreshOnly search, should fail... ldapsearch should have failed with Critical extension is unavailable (12)! ../../../tests/scripts/test062-config-delete: 164: kill: No such process XXXX$ The following is the output from valgrind for the above run. Valgrind was used specifically to aid in creating this bug report; it is not part of my normal testing of this software. ==2454== Memcheck, a memory error detector ==2454== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==2454== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==2454== Command: /home/internet/Projects/OpenLDAP/openldap/BUILD/t2/tests/../servers/slapd/slapd -s0 -F ./slapd.d -h ldap://localhost:9011/ -d 0x4105 ==2454== Parent PID: 2442 ==2454== ==2454== Thread 4: ==2454== Invalid read of size 8 ==2454== at 0x45006E: send_ldap_response (result.c:704) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== Address 0xa23cc80 is 0 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x450072: send_ldap_response (result.c:704) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== Address 0xa23ce30 is 432 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x45007F: send_ldap_response (result.c:705) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== Address 0xa23cc80 is 0 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x450083: send_ldap_response (result.c:705) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== Address 0xa23ce30 is 432 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x44FD85: send_ldap_response (result.c:716) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== Address 0xa23cdb8 is 312 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x450B28: slap_send_ldap_result (result.c:845) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23cc88 is 8 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x450CD1: slap_send_ldap_result (result.c:846) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23cc80 is 0 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 1 ==2454== at 0x7FA4CBA: vfprintf (vfprintf.c:1623) ==2454== by 0x7FCB6A1: vsnprintf (vsnprintf.c:120) ==2454== by 0x59D492: lutil_debug (debug.c:67) ==2454== by 0x450D03: slap_send_ldap_result (result.c:846) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== Address 0xa23ce38 is 440 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 1 ==2454== at 0x7FD4480: _IO_default_xsputn (genops.c:480) ==2454== by 0x7FA4B82: vfprintf (vfprintf.c:1623) ==2454== by 0x7FCB6A1: vsnprintf (vsnprintf.c:120) ==2454== by 0x59D492: lutil_debug (debug.c:67) ==2454== by 0x450D03: slap_send_ldap_result (result.c:846) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== Address 0xa23ce38 is 440 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 1 ==2454== at 0x7FD4492: _IO_default_xsputn (genops.c:479) ==2454== by 0x7FA4B82: vfprintf (vfprintf.c:1623) ==2454== by 0x7FCB6A1: vsnprintf (vsnprintf.c:120) ==2454== by 0x59D492: lutil_debug (debug.c:67) ==2454== by 0x450D03: slap_send_ldap_result (result.c:846) ==2454== by 0x5572BB: syncprov_db_close (syncprov.c:3178) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== Address 0xa23ce3a is 442 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x5572BC: syncprov_db_close (syncprov.c:3179) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== by 0x440C1D: connection_read_thread (connection.c:1291) ==2454== Address 0xa23cbc0 is 0 bytes inside a block of size 128 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 1 ==2454== at 0x555F78: syncprov_drop_psearch (syncprov.c:1099) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23cc00 is 64 bytes inside a block of size 128 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x555F86: syncprov_drop_psearch (syncprov.c:1102) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23cbe0 is 32 bytes inside a block of size 128 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x555F8A: syncprov_drop_psearch (syncprov.c:1102) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23cc80 is 0 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x555F8D: syncprov_drop_psearch (syncprov.c:1102) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0xa23ce00 is 384 bytes inside a block of size 758 free'd ==2454== at 0x4C27D4E: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2454== by 0x555F5B: syncprov_free_syncop (syncprov.c:814) ==2454== by 0x555FE5: syncprov_drop_psearch (syncprov.c:1109) ==2454== by 0x556141: syncprov_op_abandon (syncprov.c:1158) ==2454== by 0x45E0A6: fe_op_abandon (abandon.c:136) ==2454== by 0x43EBFB: connection_abandon (connection.c:747) ==2454== by 0x4403B8: connection_closing (connection.c:820) ==2454== by 0x440EBA: connection_read_thread (connection.c:1476) ==2454== by 0x573917: ldap_int_thread_pool_wrapper (tpool.c:688) ==2454== by 0x59BFB4F: start_thread (pthread_create.c:304) ==2454== by 0x8039A7C: clone (clone.S:112) ==2454== ==2454== Invalid read of size 8 ==2454== at 0x555FBB: syncprov_drop_psearch (syncprov.c:1104) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== Address 0x168 is not stack'd, malloc'd or (recently) free'd ==2454== ==2454== ==2454== Process terminating with default action of signal 11 (SIGSEGV) ==2454== Access not within mapped region at address 0x168 ==2454== at 0x555FBB: syncprov_drop_psearch (syncprov.c:1104) ==2454== by 0x5572C8: syncprov_db_close (syncprov.c:3180) ==2454== by 0x4A6B5A: overlay_remove_cb (backover.c:1189) ==2454== by 0x44F93A: slap_cleanup_play (result.c:525) ==2454== by 0x44FD99: send_ldap_response (result.c:717) ==2454== by 0x4508E5: slap_send_ldap_result (result.c:844) ==2454== by 0x42F7C4: config_back_delete (bconfig.c:6481) ==2454== by 0x4A75F2: overlay_op_walk (backover.c:691) ==2454== by 0x4A7734: over_op_func (backover.c:743) ==2454== by 0x45931F: fe_op_delete (delete.c:174) ==2454== by 0x45904C: do_delete (delete.c:95) ==2454== by 0x4407E2: connection_operation (connection.c:1155) ==2454== If you believe this happened as a result of a stack ==2454== overflow in your program's main thread (unlikely but ==2454== possible), you can try to increase the size of the ==2454== main thread stack using the --main-stacksize= flag. ==2454== The main thread stack size used in this run was 8388608. ==2454== ==2454== HEAP SUMMARY: ==2454== in use at exit: 6,002,487 bytes in 13,317 blocks ==2454== total heap usage: 22,504 allocs, 9,187 frees, 8,818,779 bytes allocated ==2454== ==2454== LEAK SUMMARY: ==2454== definitely lost: 0 bytes in 0 blocks ==2454== indirectly lost: 0 bytes in 0 blocks ==2454== possibly lost: 1,152 bytes in 4 blocks ==2454== still reachable: 6,001,335 bytes in 13,313 blocks ==2454== suppressed: 0 bytes in 0 blocks ==2454== Rerun with --leak-check=full to see details of leaked memory ==2454== ==2454== For counts of detected and suppressed errors, rerun with: -v ==2454== ERROR SUMMARY: 42 errors from 16 contexts (suppressed: 31 from 9) ~ ~

1 0

Re: (ITS#7638) Handle connection loss in SQL backend
by michael＠stroeder.com 07 Jul '13

07 Jul '13

This is a cryptographically signed message in MIME format. --------------ms060507090607040908080102 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable pierre(a)reactos.org wrote: > With this patch, before preparing any req on the given connection handl= e, the > backend will first try to check whether the connection is active by iss= ue a > dummy query. In case it's not, it will close the previous connection an= d open a > new one. And then, will prepare the req on the connection link. > > I made this choice of developement because, preparing statement, execut= ing it > and then, only looking whether it fails to re-submit would have been mo= re > complex, since it would have required to start over the whole process f= or the > query (statement preparation and such) while preparation & execution ar= en't not > in the same function. Hmm, so there's an extra dummy query for each real query. If the SQL DB i= s=20 connected over network this means a synchronous extra round trip for each= query. Ciao, Michael. --------------ms060507090607040908080102 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFfzCC BXswggNjoAMCAQICAwxOfTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMjEw MDIyMDE3MDlaFw0xNDEwMDIyMDE3MDlaMD8xGDAWBgNVBAMUD01pY2hhZWwgU3Ry9mRlcjEj MCEGCSqGSIb3DQEJARYUbWljaGFlbEBzdHJvZWRlci5jb20wggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDo2SKth5GhtaDrCyfGtyUG+/hAAa/J52L0NFN4SSRvTtdGf9HfWwwd NCtgae0TVGWk2lKDbXA9d5vmyIiRhuwxd90H6FLErhRBeB9G67qtw87E8WUoXt2DwPQEUTWV hqHpPadlmgFw3+i3TGQQTe3O3W9MMMd4GJNhObem2VGRuCD37OXnzBksTcq0FPJgcWAhe3d/ 0ItOkNWBqgq8Mf3p7WFBhaQ0a27BC/mKtH8fI3kPcS305imPRja69Msq3EwUZBc9ToVp6FRQ NYKjfOBybDUzVkmRZl3H8xutQP2w8Zxb8m5f7Q1BfLLrIFScfYvIDgOERxTCd4lab8+/09XH AgMBAAGjggFEMIIBQDAMBgNVHRMBAf8EAjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91 ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0Fj ZXJ0Lm9yZzAOBgNVHQ8BAf8EBAMCA6gwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMC BgorBgEEAYI3CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIG CCsGAQUFBzABhhZodHRwOi8vb2NzcC5jYWNlcnQub3JnMDEGA1UdHwQqMCgwJqAkoCKGIGh0 dHA6Ly9jcmwuY2FjZXJ0Lm9yZy9yZXZva2UuY3JsMB8GA1UdEQQYMBaBFG1pY2hhZWxAc3Ry b2VkZXIuY29tMA0GCSqGSIb3DQEBBQUAA4ICAQC9ouXq3p/bDWMM4tBKgD3tl4HY5H0eECl8 q9/nqk0UL6YeWkrCiQdrDtNPW7DcGqNYtzdgtzmyTr1GhiAX+igrOjdk/ge5NRcQOpONK/4b zrmpQEcIUyxSSDKLWh211/kcFfxxLEiJ5teF4GL8Fc1qbrLP4+DCvJXWfYaaR5NLjZMqm2VP yKTv3qpXWnGohiRkGTwS/11QM2XCfIGdRsQT9a8mO4m2fn2tGPp2TEIoCLrDDrbGVeDWaOWB OIeTrp4wa3Q4OI6yCptJhEqKvjhV96IBRYgM76nTBqsqnDzwxExAyhhWiUS5DunRHOr/+NyF pUpD4883RBLO0g9kUEGOhtZNF1u+8zEL0YgMGvifAom9JEklLOXZuqj0MThypKs/3d/OyOQb 4gURnu6oZwcKZ7LskytWnlRKUxF6o0A8grtmyKkqe14TS7cQbg0NTaIYXPkHR+dfFmb3uEqn BBjvpJXFcEtWI2lQXC/ET+au991pK797ExBOmpQwjIn3SjiW80vw/UoL6DMvqY/6JhVhyNTP MJ2W5AX5kc27DIbVtVGZs8J4AYhuNALJUq9N9Ka7rPRj3RcYDrfehDLOkM5iMnarpmtuOpLK d1SvZhqj/0N/JWGIDpPSTkTFOPP6ZN9I9Rqyf+9NGqb2sjo4DkIiZcHxt735/GJLwus5KLBl 2DGCA6EwggOdAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93 d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8G CSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMMTn0wCQYFKw4DAhoFAKCCAfUwGAYJ KoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNzA3MTIzMzAwWjAj BgkqhkiG9w0BCQQxFgQUcA4tlsdiopKrS2o6P/u/9l6BtaowbAYJKoZIhvcNAQkPMV8wXTAL BglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAN BggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBkQYJKwYBBAGCNxAEMYGD MIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9y ZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYS c3VwcG9ydEBjYWNlcnQub3JnAgMMTn0wgZMGCyqGSIb3DQEJEAILMYGDoIGAMHkxEDAOBgNV BAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZ Q0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNl cnQub3JnAgMMTn0wDQYJKoZIhvcNAQEBBQAEggEAVQZMpxErjJaK7BfN3lo+Q0Jf4cJRZ3Y/ hutq+P9aUTxJB1pOwjxle8MZ0H0/TbJ5XJu5Mtc/fzc3DcKMH+EDgyM8Jt/z5bqY1SRmVBNA U8ZZMxyhaBDpt4wIl1JftEkrn87iLXD5H5uxsE70ohKSOKIt0m+500tuvWxGtlrQPV4Ufilf a/jQU3G9Td04y4T4eq6ql39AkZPYR88SyJC1jjKhPPzRb/iWvvUzsJNpe/LSgd+ujdpIceY7 rM0PS8bPMZUCtS5TS9f+QT//tb7YI5r/a5jlP3nTeTRiQjMBLMb2EU2+q0fA6PcsQ0Hhr3TU OeNbOIlyfS6NrRu5pjupkgAAAAAAAA== --------------ms060507090607040908080102--

1 0

(ITS#7638) Handle connection loss in SQL backend
by pierre＠reactos.org 07 Jul '13

07 Jul '13

Full_Name: Pierre Schweitzer Version: HEAD OS: Ubuntu URL: http://fc.isima.fr/~schweitz/schweitz/0001-In-the-SQL-backend-add-code-to-h… Submission from: (NULL) (90.27.237.49) Hi, here is a patch to handle a possible connection loss to DBMS for the SQL backend. Right now, in case of connection loss, slapd just denied any entry lookup with an error 80 (backend error). With this patch, before preparing any req on the given connection handle, the backend will first try to check whether the connection is active by issue a dummy query. In case it's not, it will close the previous connection and open a new one. And then, will prepare the req on the connection link. I made this choice of developement because, preparing statement, executing it and then, only looking whether it fails to re-submit would have been more complex, since it would have required to start over the whole process for the query (statement preparation and such) while preparation & execution aren't not in the same function. This patch has been tested and validated in production on the ReactOS Foundation infrastructure. The attached patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Pierre Schweitzer (pierre(a)reactos.org). I have not assigned rights and/or interest in this work to any party. I, Pierre Schweitzer, hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice. Regards, Pierre

1 0

Re: (ITS#7637) Need documentation: LDAP on virtual IP address
by hyc＠symas.com 04 Jul '13

04 Jul '13

Ulrich.Windl(a)rz.uni-regensburg.de wrote: > Full_Name: Ulrich Windl > Version: 2.4.26 > OS: Linux (SLES11 SP2) > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (132.199.152.129) > > > I was able to set up a master LDAP server and a replication consumer using the > physical host names and TLS. However when I tried to bind slapd on a virtual IP > address ("interface alias"), I never got slapd working (even though I fixed the > certificates for TLS, of course). Dynamic configuration ("cn=config") seems to > make things very difficult, because slapd ends in a state where _nobody_ can > make configuration changes. Use the openldap-technical mailing list to ask for configuration help. You talk about IP addresses and yet in your quoted text below you are using hostnames. Be consistent when you post your question to the mailing list otherwise no one will understand what you're asking for. Closing this ITS. > It seems slapd tried to use the wrong URI (using the physical host where nobody > is listening): > slapd[10036]: slap_client_connect: URI=ldap://phost.domain.org/ Error, > ldap_start_tls failed (-1) > slapd[10036]: do_syncrepl: rid=002 rc -1 retrying > > slapd is listening on ldap://vhost.domain.org/ however. > > I read lots of procedures using Google, but could not find the solution for this > problem. Thus I suggest to add documentation how to configure such a scenario: > > 1) Set up an LDAP Master server that provides service on a specific IP address > using TLS > 2) Set up a replication consumer that provides service on a specific IP address > using TLS also > 3) The replication consumer should use the address where the master server > listens for replication > > It sounds like an every-day setup, but I failed multiple times, thus the request > for documentation. > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#7637) Need documentation: LDAP on virtual IP address
by Ulrich.Windl＠rz.uni-regensburg.de 04 Jul '13

04 Jul '13

Full_Name: Ulrich Windl Version: 2.4.26 OS: Linux (SLES11 SP2) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (132.199.152.129) I was able to set up a master LDAP server and a replication consumer using the physical host names and TLS. However when I tried to bind slapd on a virtual IP address ("interface alias"), I never got slapd working (even though I fixed the certificates for TLS, of course). Dynamic configuration ("cn=config") seems to make things very difficult, because slapd ends in a state where _nobody_ can make configuration changes. It seems slapd tried to use the wrong URI (using the physical host where nobody is listening): slapd[10036]: slap_client_connect: URI=ldap://phost.domain.org/ Error, ldap_start_tls failed (-1) slapd[10036]: do_syncrepl: rid=002 rc -1 retrying slapd is listening on ldap://vhost.domain.org/ however. I read lots of procedures using Google, but could not find the solution for this problem. Thus I suggest to add documentation how to configure such a scenario: 1) Set up an LDAP Master server that provides service on a specific IP address using TLS 2) Set up a replication consumer that provides service on a specific IP address using TLS also 3) The replication consumer should use the address where the master server listens for replication It sounds like an every-day setup, but I failed multiple times, thus the request for documentation.

1 0

Re: (ITS#7636) slapd crash when multi-master replication (syncrepl) enabled
by hyc＠symas.com 03 Jul '13

03 Jul '13

kb9vqf(a)pearsoncomputing.net wrote: >> kb9vqf(a)pearsoncomputing.net wrote: >>> Full_Name: Timothy Pearson >>> Version: 2.4.31 >>> OS: Debian Wheezy >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (131.156.2.26) >>> >>> >>> The setup: >>> Multi-master syncrepl on two servers >>> Identical hardware and software between servers >>> Self-signed TLS using common (private) CA certificate >>> >>> The problem: >>> slapd on one server crashes repeatably within a minute of slapd > starting on the >>> other server. slapd works reliably if and only if the other server is not >>> running a slapd process. >> >> 1) 2.4.31 is ancient. Current is 2.4.35. Please provide a backtrace > against a >> current OpenLDAP release. >> >> 2) Your backtrace shows a crash in a slapi plugin. If the bug is in your > plugin there's nothing we can do about it. >> >> 3) Don't touch the individual files inside the slapd configuration > database. >> Use "slapcat -n0". > > Thank you for your prompt response. In the backtrace I posted, which > portion suggests that the crash occurred in a plugin? I would have > expected to see at least one frame in something other than > ../../../../servers/slapd. Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffe356c700 (LWP 10433)] 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff5a356f0 in *__GI_abort () at abort.c:92 #2 0x00007ffff5a6d52b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #3 0x00007ffff5a76d76 in malloc_printerr (action=3, str=0x7ffff5b4f170 "munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:6283 #4 0x00007ffff63d214a in slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>, prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:313 #5 slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>, prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:296 #6 0x00007ffff63d304f in slapi_op_func (rs=0x7fffe3569f60, op=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:631 #7 slapi_op_func (op=0x7fffe3569fd0, rs=0x7fffe3569f60) at ../../../../../servers/slapd/slapi/slapi_overlay.c:556 The slapi_* functions would not be present in the stack trace unless you had configured a slapi plugin on this database. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7636) slapd crash when multi-master replication (syncrepl) enabled
by kb9vqf＠pearsoncomputing.net 03 Jul '13

03 Jul '13

> kb9vqf(a)pearsoncomputing.net wrote: >> Full_Name: Timothy Pearson >> Version: 2.4.31 >> OS: Debian Wheezy >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (131.156.2.26) >> >> >> The setup: >> Multi-master syncrepl on two servers >> Identical hardware and software between servers >> Self-signed TLS using common (private) CA certificate >> >> The problem: >> slapd on one server crashes repeatably within a minute of slapd starting on the >> other server. slapd works reliably if and only if the other server is not >> running a slapd process. > > 1) 2.4.31 is ancient. Current is 2.4.35. Please provide a backtrace against a > current OpenLDAP release. > > 2) Your backtrace shows a crash in a slapi plugin. If the bug is in your plugin there's nothing we can do about it. > > 3) Don't touch the individual files inside the slapd configuration database. > Use "slapcat -n0". Thank you for your prompt response. In the backtrace I posted, which portion suggests that the crash occurred in a plugin? I would have expected to see at least one frame in something other than ../../../../servers/slapd. I am not directly modifying the config database text files, but did not know the correct method to dump the existing files. Thanks for the command!

1 0

Re: (ITS#7633) Slapd hangs on hdb write lock
by hyc＠symas.com 03 Jul '13

03 Jul '13

dusan.fric(a)t-systems.sk wrote: > --_000_B3C9B2D7E2866A479BAEDF530AA0293D2C5FE65416TSSKKEEXCCR1s_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Hi guys, > > good news, the issue is solved. We changed db setting (DB_CONFIG) as follow= > s: > > set_lk_detect DB_LOCK_RANDOM > > (instead of bad set_lk_detect DB_LOCK_EXPIRE) > > and no hangs until now. That's great, but why was it set to DB_LOCK_EXPIRE in the first place? DB_LOCK_RANDOM is the default, you should not be changing this setting without a good reason and good knowledge of what you're doing. > > We can also find the same issue described here > > http://www.openldap.org/lists/openldap-technical/201102/msg00074.html > > > FYI - customer's test confirmed it. > > Thanks for your suggestions and help. > > Regards, > Dusan -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7633) Slapd hangs on hdb write lock
by dusan.fric＠t-systems.sk 03 Jul '13

03 Jul '13

--_000_B3C9B2D7E2866A479BAEDF530AA0293D2C5FE65416TSSKKEEXCCR1s_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi guys, good news, the issue is solved. We changed db setting (DB_CONFIG) as follow= s: set_lk_detect DB_LOCK_RANDOM (instead of bad set_lk_detect DB_LOCK_EXPIRE) and no hangs until now. We can also find the same issue described here http://www.openldap.org/lists/openldap-technical/201102/msg00074.html FYI - customer's test confirmed it. Thanks for your suggestions and help. Regards, Dusan --_000_B3C9B2D7E2866A479BAEDF530AA0293D2C5FE65416TSSKKEEXCCR1s_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content= =3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros= oft Word 14 (filtered medium)"><style></style></head><body lang=3DEN-US link=3Dblue vli= nk=3Dpurple><div class=3DWordSection1>Hi guys,<o:p></o= :p><o:p> </o:p>good = news, the issue is solved. We changed db setting (DB_CONFIG) as follows:<o:= p></o:p><o:p> </o:p>= set_lk_detect DB_LOCK_RANDOM<o:p></o:p><o:p> = </o:p>(instead of bad <s>set_lk_detect DB_LOCK_EXP= IRE</s>)<o:p></o:p><o:p> </o:p>and no hangs until now. <o:p></o:p><o= :p> </o:p>We can also find the same issue des= cribed here<o:p></o:p><o:p> </o:p><a href=3D"http://www.openldap.org/lists/openldap-technical/2= 01102/msg00074.html">http://www.openldap.org/lists/openldap-technical/20110= 2/msg00074.html</a><o:p></o:p><o:p> </o:p></p= ><o:p> </o:p>FYI –= customer’s test confirmed it.<o:p></o:p><o:= p> </o:p>Thanks for your suggestions and help= .<o:p></o:p><o:p> </o:p>Regards,<o:p></o:p>Dusan<o:p></o:p></div><= /body></html>= --_000_B3C9B2D7E2866A479BAEDF530AA0293D2C5FE65416TSSKKEEXCCR1s_--

1 0

Re: (ITS#7636) slapd crash when multi-master replication (syncrepl) enabled
by hyc＠symas.com 02 Jul '13

02 Jul '13

kb9vqf(a)pearsoncomputing.net wrote: > Full_Name: Timothy Pearson > Version: 2.4.31 > OS: Debian Wheezy > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (131.156.2.26) > > > The setup: > Multi-master syncrepl on two servers > Identical hardware and software between servers > Self-signed TLS using common (private) CA certificate > > The problem: > slapd on one server crashes repeatably within a minute of slapd starting on the > other server. slapd works reliably if and only if the other server is not > running a slapd process. 1) 2.4.31 is ancient. Current is 2.4.35. Please provide a backtrace against a current OpenLDAP release. 2) Your backtrace shows a crash in a slapi plugin. If the bug is in your plugin there's nothing we can do about it. 3) Don't touch the individual files inside the slapd configuration database. Use "slapcat -n0". > > Backtrace (does not change appreciably from crash to crash): > > Program received signal SIGABRT, Aborted. > [Switching to Thread 0x7fffe356c700 (LWP 10433)] > 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. > (gdb) bt > #0 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x00007ffff5a356f0 in *__GI_abort () at abort.c:92 > #2 0x00007ffff5a6d52b in __libc_message (do_abort=<optimized out>, > fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 > #3 0x00007ffff5a76d76 in malloc_printerr (action=3, str=0x7ffff5b4f170 > "munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:6283 > #4 0x00007ffff63d214a in slapi_op_search_callback (op=0x7fffe3569fd0, > rs=<optimized out>, prc=<optimized out>) at > ../../../../../servers/slapd/slapi/slapi_overlay.c:313 > #5 slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>, > prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:296 > #6 0x00007ffff63d304f in slapi_op_func (rs=0x7fffe3569f60, op=<optimized out>) > at ../../../../../servers/slapd/slapi/slapi_overlay.c:631 > #7 slapi_op_func (op=0x7fffe3569fd0, rs=0x7fffe3569f60) at > ../../../../../servers/slapd/slapi/slapi_overlay.c:556 > #8 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x7fffe3569fd0, > rs=0x7fffe3569f60, which=op_search, oi=0x5555559e57f0, on=0x5555559e4510) at > ../../../../servers/slapd/backover.c:661 > #9 0x00005555555ff31b in over_op_func (op=0x7fffe3569fd0, rs=<optimized out>, > which=<optimized out>) at ../../../../servers/slapd/backover.c:723 > #10 0x00007ffff1c4870e in syncprov_findbase (op=op@entry=0x555555dd8560, > fc=fc@entry=0x7fffe356a280) at > ../../../../../servers/slapd/overlays/syncprov.c:453 > #11 0x00007ffff1c4b1ef in syncprov_op_search (op=0x555555dd8560, > rs=0x7fffe356ba50) at ../../../../../servers/slapd/overlays/syncprov.c:2465 > #12 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x555555dd8560, > rs=rs@entry=0x7fffe356ba50, which=which@entry=op_search, oi=0x5555559e57f0, > on=0x5555559e15e0) at ../../../../servers/slapd/backover.c:661 > #13 0x00007ffff63d3086 in slapi_op_func (rs=0x7fffe356ba50, op=<optimized out>) > at ../../../../../servers/slapd/slapi/slapi_overlay.c:647 > #14 slapi_op_func (op=0x555555dd8560, rs=0x7fffe356ba50) at > ../../../../../servers/slapd/slapi/slapi_overlay.c:556 > #15 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x555555dd8560, > rs=0x7fffe356ba50, which=op_search, oi=0x5555559e57f0, on=0x5555559e4510) at > ../../../../servers/slapd/backover.c:661 > #16 0x00005555555ff31b in over_op_func (op=0x555555dd8560, rs=<optimized out>, > which=<optimized out>) at ../../../../servers/slapd/backover.c:723 > #17 0x0000555555594641 in fe_op_search (op=0x555555dd8560, rs=0x7fffe356ba50) at > ../../../../servers/slapd/search.c:402 > #18 0x0000555555593f06 in do_search (op=0x555555dd8560, rs=0x7fffe356ba50) at > ../../../../servers/slapd/search.c:247 > #19 0x0000555555591961 in connection_operation (ctx=ctx@entry=0x7fffe356bba0, > arg_v=arg_v@entry=0x555555dd8560) at > ../../../../servers/slapd/connection.c:1150 > #20 0x0000555555591c84 in connection_read_thread (ctx=0x7fffe356bba0, > argv=<optimized out>) at ../../../../servers/slapd/connection.c:1286 > #21 0x00007ffff7b9dff3 in ?? () from > /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 > #22 0x00007ffff5d90b50 in start_thread (arg=<optimized out>) at > pthread_create.c:304 > #23 0x00007ffff5adaa7d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 > #24 0x0000000000000000 in ?? () > > > Relevant configuration files: > > > olcDatabase={0}config.ldif: > > dn: olcDatabase={0}config > objectClass: olcDatabaseConfig > olcDatabase: {0}config > olcAccess: {0}to * by > group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" > write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" write > by dn.base="cn=admin,dc=<redacted>" write by sockurl.regex="^ldapi:///$" write > by dynacl/aci write by * none > olcAddContentAcl: TRUE > olcLastMod: TRUE > olcMaxDerefDepth: 15 > olcReadOnly: FALSE > olcRootDN: cn=config > olcRootPW:: REDACTED > olcSyncUseSubentry: FALSE > olcMonitoring: FALSE > structuralObjectClass: olcDatabaseConfig > creatorsName: cn=config > createTimestamp: 20130702170316Z > olcSyncrepl: {0}rid=001 provider=ldaps://ldap002.<redacted>/ > binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" > searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5 600 +" timeout=1 > tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem"lcSyncrepl: > {1}rid=002 provider=ldaps://ldap003.<redacted>/ binddn="cn=admin,dc=<redacted>" > bindmethod=simple credentials="ldapadmin001" searchbase="cn=config" > type=refreshAndPersist retry="5 5 300 5 600 +" timeout=1 tls_reqcert=never > tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" > olcMirrorMode: TRUE > entryCSN: 20130702180604.682031Z#000000#002#000000 > modifiersName: > modifyTimestamp: 20130702180604Z > > > olcDatabase={1}hdb.ldif: > > dn: olcDatabase={1}hdb > objectClass: olcDatabaseConfig > objectClass: olcHdbConfig > olcDatabase: {1}hdb > olcDbDirectory: /var/lib/ldap > olcSuffix: dc=<redacted> > olcAccess: {0}to attrs=userPassword,shadowLastChange,krb5Key,krb5PrincipalName,krb5KeyVersionNumber,krb5MaxLife,krb5MaxRenew,krb5KDCFlags,privateRootCertificateKey > by group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" > write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" by > sockurl.regex="^ldapi:///$" write by anonymous auth by self write by * none > olcAccess: {1}to dn.base="" by * read > olcAccess: {2}to * by > group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" > write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" write > by sockurl.regex="^ldapi:///$" write by dynacl/aci write > olcAddContentAcl: FALSE > olcLastMod: TRUE > olcMaxDerefDepth: 15 > olcReadOnly: FALSE > olcRootDN: cn=admin,dc=<redacted> > olcRootPW:: REDACTED > olcMonitoring: TRUE > olcDbCacheSize: 1000 > olcDbCheckpoint: 512 30 > olcDbConfig: {0}set_cachesize 0 67108864 1 > olcDbConfig: {1}set_lg_regionmax 262144 > olcDbConfig: {2}set_lg_bsize 2097152 > olcDbNoSync: FALSE > olcDbDirtyRead: FALSE > olcDbIDLcacheSize: 0 > olcDbIndex: objectClass eq > olcDbIndex: krb5PrincipalName eq,pres > olcDbIndex: cn eq,pres,subinitial > olcDbIndex: mail eq,pres > olcDbIndex: uid pres,eq > olcDbIndex: uidNumber eq > olcDbIndex: gidNumber eq > olcDbLinearIndex: FALSE > olcDbMode: 0600 > olcDbSearchStack: 16 > olcDbShmKey: 0 > olcDbCacheFree: 1 > olcDbDNcacheSize: 0 > olcPlugin: postoperation /opt/trinity/lib/slapi-acl-manager.so plugin_init > admingroup-dn:=cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted> > realm:=CEET.NIU.EDU aclfile:=/etc/heimdal-kdc/kadmind.acl builtinadmin:=admin > structuralObjectClass: olcHdbConfig > creatorsName: cn=config > createTimestamp: 20130702170316Z > olcSyncrepl: {0}rid=001 provider=ldaps://ldap002.<redacted>/ > binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" > searchbase="dc=<redacted>" type=refreshAndPersist retry="5 5 300 5" timeout=1 > tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" > olcSyncrepl: {1}rid=002 provider=ldaps://ldap003.<redacted>/ > binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" > searchbase="dc=<redacted>" type=refreshAndPersist retry="5 5 300 5" timeout=1 > tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" > olcMirrorMode: TRUE > entryCSN: 20130702170511.039863Z#000000#002#000000 > modifiersName: > modifyTimestamp: 20130702170511Z > > > olcDatabase={0}config/olcOverlay={0}syncprov.ldif: > > dn: olcOverlay={0}syncprov > objectClass: olcOverlayConfig > objectClass: olcSyncProvConfig > olcOverlay: {0}syncprov > structuralObjectClass: olcSyncProvConfig > entryUUID: 14f25934-7785-1032-93bd-0fe5d581c3b6 > creatorsName: > createTimestamp: 20130702170337Z > entryCSN: 20130702170337.631532Z#000000#002#000000 > modifiersName: > modifyTimestamp: 20130702170337Z > > > olcDatabase={1}hdb/olcOverlay={0}syncprov.ldif: > > dn: olcOverlay={0}syncprov > objectClass: olcOverlayConfig > objectClass: olcSyncProvConfig > olcOverlay: {0}syncprov > structuralObjectClass: olcSyncProvConfig > entryUUID: bfa2e530-778d-1032-9b41-e7480f731418 > creatorsName: > createTimestamp: 20130702180539Z > entryCSN: 20130702180539.975057Z#000000#002#000000 > modifiersName: > modifyTimestamp: 20130702180539Z > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7636) slapd crash when multi-master replication (syncrepl) enabled
by kb9vqf＠pearsoncomputing.net 02 Jul '13

02 Jul '13

Since my report above seems to have been somewhat mangled by the submission process, here is a link to a plain-text version of the same report: http://www.ceet.niu.edu/pastebin/openldap_bug_report_7636.txt

1 0

(ITS#7636) slapd crash when multi-master replication (syncrepl) enabled
by kb9vqf＠pearsoncomputing.net 02 Jul '13

02 Jul '13

Full_Name: Timothy Pearson Version: 2.4.31 OS: Debian Wheezy URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (131.156.2.26) The setup: Multi-master syncrepl on two servers Identical hardware and software between servers Self-signed TLS using common (private) CA certificate The problem: slapd on one server crashes repeatably within a minute of slapd starting on the other server. slapd works reliably if and only if the other server is not running a slapd process. Backtrace (does not change appreciably from crash to crash): Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffe356c700 (LWP 10433)] 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff5a356f0 in *__GI_abort () at abort.c:92 #2 0x00007ffff5a6d52b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #3 0x00007ffff5a76d76 in malloc_printerr (action=3, str=0x7ffff5b4f170 "munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:6283 #4 0x00007ffff63d214a in slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>, prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:313 #5 slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>, prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:296 #6 0x00007ffff63d304f in slapi_op_func (rs=0x7fffe3569f60, op=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:631 #7 slapi_op_func (op=0x7fffe3569fd0, rs=0x7fffe3569f60) at ../../../../../servers/slapd/slapi/slapi_overlay.c:556 #8 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x7fffe3569fd0, rs=0x7fffe3569f60, which=op_search, oi=0x5555559e57f0, on=0x5555559e4510) at ../../../../servers/slapd/backover.c:661 #9 0x00005555555ff31b in over_op_func (op=0x7fffe3569fd0, rs=<optimized out>, which=<optimized out>) at ../../../../servers/slapd/backover.c:723 #10 0x00007ffff1c4870e in syncprov_findbase (op=op@entry=0x555555dd8560, fc=fc@entry=0x7fffe356a280) at ../../../../../servers/slapd/overlays/syncprov.c:453 #11 0x00007ffff1c4b1ef in syncprov_op_search (op=0x555555dd8560, rs=0x7fffe356ba50) at ../../../../../servers/slapd/overlays/syncprov.c:2465 #12 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x555555dd8560, rs=rs@entry=0x7fffe356ba50, which=which@entry=op_search, oi=0x5555559e57f0, on=0x5555559e15e0) at ../../../../servers/slapd/backover.c:661 #13 0x00007ffff63d3086 in slapi_op_func (rs=0x7fffe356ba50, op=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:647 #14 slapi_op_func (op=0x555555dd8560, rs=0x7fffe356ba50) at ../../../../../servers/slapd/slapi/slapi_overlay.c:556 #15 0x00005555555ff18a in overlay_op_walk (op=op@entry=0x555555dd8560, rs=0x7fffe356ba50, which=op_search, oi=0x5555559e57f0, on=0x5555559e4510) at ../../../../servers/slapd/backover.c:661 #16 0x00005555555ff31b in over_op_func (op=0x555555dd8560, rs=<optimized out>, which=<optimized out>) at ../../../../servers/slapd/backover.c:723 #17 0x0000555555594641 in fe_op_search (op=0x555555dd8560, rs=0x7fffe356ba50) at ../../../../servers/slapd/search.c:402 #18 0x0000555555593f06 in do_search (op=0x555555dd8560, rs=0x7fffe356ba50) at ../../../../servers/slapd/search.c:247 #19 0x0000555555591961 in connection_operation (ctx=ctx@entry=0x7fffe356bba0, arg_v=arg_v@entry=0x555555dd8560) at ../../../../servers/slapd/connection.c:1150 #20 0x0000555555591c84 in connection_read_thread (ctx=0x7fffe356bba0, argv=<optimized out>) at ../../../../servers/slapd/connection.c:1286 #21 0x00007ffff7b9dff3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #22 0x00007ffff5d90b50 in start_thread (arg=<optimized out>) at pthread_create.c:304 #23 0x00007ffff5adaa7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #24 0x0000000000000000 in ?? () Relevant configuration files: olcDatabase={0}config.ldif: dn: olcDatabase={0}config objectClass: olcDatabaseConfig olcDatabase: {0}config olcAccess: {0}to * by group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" write by dn.base="cn=admin,dc=<redacted>" write by sockurl.regex="^ldapi:///$" write by dynacl/aci write by * none olcAddContentAcl: TRUE olcLastMod: TRUE olcMaxDerefDepth: 15 olcReadOnly: FALSE olcRootDN: cn=config olcRootPW:: REDACTED olcSyncUseSubentry: FALSE olcMonitoring: FALSE structuralObjectClass: olcDatabaseConfig creatorsName: cn=config createTimestamp: 20130702170316Z olcSyncrepl: {0}rid=001 provider=ldaps://ldap002.<redacted>/ binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5 600 +" timeout=1 tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem"lcSyncrepl: {1}rid=002 provider=ldaps://ldap003.<redacted>/ binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5 600 +" timeout=1 tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" olcMirrorMode: TRUE entryCSN: 20130702180604.682031Z#000000#002#000000 modifiersName: modifyTimestamp: 20130702180604Z olcDatabase={1}hdb.ldif: dn: olcDatabase={1}hdb objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: {1}hdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=<redacted> olcAccess: {0}to attrs=userPassword,shadowLastChange,krb5Key,krb5PrincipalName,krb5KeyVersionNumber,krb5MaxLife,krb5MaxRenew,krb5KDCFlags,privateRootCertificateKey by group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" by sockurl.regex="^ldapi:///$" write by anonymous auth by self write by * none olcAccess: {1}to dn.base="" by * read olcAccess: {2}to * by group/groupOfNames/member.exact="cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted>" write by dn.base="uid=ldapadmin,ou=users,ou=core,ou=realm,dc=<redacted>" write by sockurl.regex="^ldapi:///$" write by dynacl/aci write olcAddContentAcl: FALSE olcLastMod: TRUE olcMaxDerefDepth: 15 olcReadOnly: FALSE olcRootDN: cn=admin,dc=<redacted> olcRootPW:: REDACTED olcMonitoring: TRUE olcDbCacheSize: 1000 olcDbCheckpoint: 512 30 olcDbConfig: {0}set_cachesize 0 67108864 1 olcDbConfig: {1}set_lg_regionmax 262144 olcDbConfig: {2}set_lg_bsize 2097152 olcDbNoSync: FALSE olcDbDirtyRead: FALSE olcDbIDLcacheSize: 0 olcDbIndex: objectClass eq olcDbIndex: krb5PrincipalName eq,pres olcDbIndex: cn eq,pres,subinitial olcDbIndex: mail eq,pres olcDbIndex: uid pres,eq olcDbIndex: uidNumber eq olcDbIndex: gidNumber eq olcDbLinearIndex: FALSE olcDbMode: 0600 olcDbSearchStack: 16 olcDbShmKey: 0 olcDbCacheFree: 1 olcDbDNcacheSize: 0 olcPlugin: postoperation /opt/trinity/lib/slapi-acl-manager.so plugin_init admingroup-dn:=cn=realmadmins,ou=groups,ou=core,ou=realm,dc=<redacted> realm:=CEET.NIU.EDU aclfile:=/etc/heimdal-kdc/kadmind.acl builtinadmin:=admin structuralObjectClass: olcHdbConfig creatorsName: cn=config createTimestamp: 20130702170316Z olcSyncrepl: {0}rid=001 provider=ldaps://ldap002.<redacted>/ binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" searchbase="dc=<redacted>" type=refreshAndPersist retry="5 5 300 5" timeout=1 tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" olcSyncrepl: {1}rid=002 provider=ldaps://ldap003.<redacted>/ binddn="cn=admin,dc=<redacted>" bindmethod=simple credentials="ldapadmin001" searchbase="dc=<redacted>" type=refreshAndPersist retry="5 5 300 5" timeout=1 tls_reqcert=never tls_cacert="/etc/trinity/ldap/tde-ca/anchors/tdeca.pem" olcMirrorMode: TRUE entryCSN: 20130702170511.039863Z#000000#002#000000 modifiersName: modifyTimestamp: 20130702170511Z olcDatabase={0}config/olcOverlay={0}syncprov.ldif: dn: olcOverlay={0}syncprov objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov structuralObjectClass: olcSyncProvConfig entryUUID: 14f25934-7785-1032-93bd-0fe5d581c3b6 creatorsName: createTimestamp: 20130702170337Z entryCSN: 20130702170337.631532Z#000000#002#000000 modifiersName: modifyTimestamp: 20130702170337Z olcDatabase={1}hdb/olcOverlay={0}syncprov.ldif: dn: olcOverlay={0}syncprov objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov structuralObjectClass: olcSyncProvConfig entryUUID: bfa2e530-778d-1032-9b41-e7480f731418 creatorsName: createTimestamp: 20130702180539Z entryCSN: 20130702180539.975057Z#000000#002#000000 modifiersName: modifyTimestamp: 20130702180539Z

1 0

(ITS#7635) lmdb race condition in read vs write txns
by hyc＠OpenLDAP.org 01 Jul '13

01 Jul '13

Full_Name: Howard Chu Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.127.144.82) Submitted by: hyc It's possible for a write txn to update a meta page while a reader is creating its snapshot of the meta page. In most cases this situation is harmless, but if the update raises the mm_last_pg field it may later cause an assert if the reader still has the old value of mm_last_pg, but accesses a DB whose pages are beyond the old value. A fix has been tested and will be committed shortly.

1 0

RE: (ITS#7634) openldap 2.4.24 hangs while attempting to shutdown
by madhan.kumar＠alcatel-lucent.com 01 Jul '13

01 Jul '13

Thanks Micheal. -----Original Message----- From: Michael Ströder [mailto:michael@stroeder.com] Sent: Monday, July 01, 2013 1:49 PM To: KUMAR, Madhan (Madhan); openldap-its(a)openldap.org Subject: Re: (ITS#7634) openldap 2.4.24 hangs while attempting to shutdown madhan.kumar(a)alcatel-lucent.com wrote: > We have an issue of openldap 2.4.24 hanging. This is similar to the issue > mentioned in the link: > http://www.openldap.org/lists/openldap-technical/201208/msg00119.html If you read the follow-up in the ML archive Howard says this was fixed in 2.4.25. So could you please try out recent release 2.4.35? Ciao, Michael.

1 0

Re: (ITS#7634) openldap 2.4.24 hangs while attempting to shutdown
by michael＠stroeder.com 01 Jul '13

01 Jul '13

madhan.kumar(a)alcatel-lucent.com wrote: > We have an issue of openldap 2.4.24 hanging. This is similar to the issue > mentioned in the link: > http://www.openldap.org/lists/openldap-technical/201208/msg00119.html If you read the follow-up in the ML archive Howard says this was fixed in 2.4.25. So could you please try out recent release 2.4.35? Ciao, Michael.

1 0

(ITS#7634) openldap 2.4.24 hangs while attempting to shutdown
by madhan.kumar＠alcatel-lucent.com 01 Jul '13

01 Jul '13

Full_Name: Madhan Kumar Version: 2.4.24 OS: linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (135.245.192.4) We have an issue of openldap 2.4.24 hanging. This is similar to the issue mentioned in the link: http://www.openldap.org/lists/openldap-technical/201208/msg00119.html When I checked the openldap logs I could see that the listeners are shown as busy continuously and an automatic internal shutdown is initiated to recover the ldap process. Unfortunately in our case the automatic internal shutdown is stuck and hence the issue. daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: epoll: listen=7 active_threads=0 tvp=zero daemon: epoll: listen=8 busy daemon: shutdown requested and initiated. daemon: closing 7 daemon: closing 8 We need to get an confirmation that this issue is being fixed in openldap 2.4.25 so that we can upgrade our openldap version. Please confirm.

1 0

RE: (ITS#7633) Slapd hangs on hdb write lock
by ck＠cksoft.de 28 Jun '13

28 Jun '13

Hi Dusan, On Fri, 28 Jun 2013, dusan.fric(a)t-systems.sk wrote: > Hi Chu, > > thanks for your quick response. We will try to contact Oracle to advice here. > > However, what is your suggestion here ' try different settings for the deadlock detector' exactly? > > BTW - certainly, we are patched DB 4.7.25 (all 4 patches)... In case you can update to 2.4.35 you might want to test the mdb backend with your workload. Especially if you can easily reproduce the problem. Greetings Christian > > Regards, > Dusan > > -----Original Message----- > From: Howard Chu [mailto:hyc@symas.com] > Sent: 26. j??na 2013 13:32 > To: Fric, Dusan; openldap-its(a)openldap.org > Subject: Re: (ITS#7633) Slapd hangs on hdb write lock > > dusan.fric(a)t-systems.sk wrote: >> Full_Name: Dusan Fric >> Version: 2.4.32 >> OS: RHEL 5.7 x64 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (88.212.40.139) >> >> >> We are experiencing frequent hangs in slapd. Once hung we usualy >> cannot continue to connect until we kill -9 the slapd process and >> restart it. The directory is used for 2 applications as user eDir and >> we are using it in production over 1 month - we have noted the busier >> the directory becomes the more often it hangs (now twice per week). >> >> We have installed identical configurations on 3 environments, each has >> only one single server (no replication). There are 30k entries in the >> directory (production). >> >> We are running: >> >> RHEL 5.7 x64 (VMWare with NFS mountpoints) OpenLDAP 2.4.32 Berkeley DB >> 4.8.30 (4.7.25) >> >> We were starting with DB 4.8.30, after downgrade to version 4.7.25 >> (according to >> ITS#7378 - >> https://www.openldap.org/its/index.cgi/Incoming?id=7378;selectid=7378) >> we are facing the same issue. >> >> The problem occurs when two requests simultaneously try to update >> attributes of a record and in most cases of the same DN value. >> We can easily reproduce it with a java test program running 2 threads >> each connecting to the ldap server and updating the record for a >> particular DN value. >> It need not be the same DN value but DN values which reside on the >> same BDB page. > > Thanks for the traces, but the information you've provided shows that this is a BDB problem, not an OpenLDAP bug. You'll have to contact Oracle for help. > The BDB deadlock detector is supposed to handle these situations. > > For example in your 4.8.30 lock status there are only 2 conflicting transactions 80000028 and 80000029 and they are only contending on a single page. This is one of the most elementary deadlock situations. > > You might try different settings for the deadlock detector, but ultimately this appears to be a BDB bug and the choice of detector shouldn't matter. > >> Configuration >> >> olc cn=config (part): >> dn: cn=config >> objectClass: olcGlobal >> cn: config >> olcConcurrency: 0 >> olcConnMaxPending: 100 >> olcConnMaxPendingAuth: 1000 >> olcSockbufMaxIncoming: 262143 >> olcSockbufMaxIncomingAuth: 16777215 >> olcThreads: 32 >> >> olc DB hdb config (part): >> dn: olcDatabase={1}hdb,cn=config >> objectClass: olcHdbConfig >> objectClass: olcDatabaseConfig >> olcDatabase: {1}hdb >> olcDbCacheSize: 80000 >> olcDbCheckpoint: 128 5 >> olcDbConfig: {0}set_cachesize 0 268435456 1 >> olcDbConfig: {1}set_lg_max 10485760 >> olcDbConfig: {2}set_lg_bsize 2097152 >> olcDbConfig: {3}set_lg_dir /pkg/openldap/dblog >> olcDbConfig: {4}set_lg_regionmax 262144 >> olcDbConfig: {5}set_lk_detect DB_LOCK_EXPIRE >> olcDbConfig: {6}set_flags DB_TXN_NOSYNC >> olcDbDirtyRead: FALSE >> olcDbDNcacheSize: 0 >> olcDbIDLcacheSize: 240000 >> olcDbIndex: default eq,sub >> olcDbIndex: objectClass eq >> olcDbIndex: cn eq,sub >> olcDbIndex: uid eq,sub >> olcDbIndex: mail pres,eq >> olcDbIndex: sn eq,sub >> olcDbIndex: member eq >> olcDbLinearIndex: FALSE >> olcDbMode: 0600 >> olcDbNoSync: TRUE >> olcDbSearchStack: 20 >> olcDbShmKey: 0 >> olcLastMod: TRUE >> olcMaxDerefDepth: 15 >> olcMonitoring: TRUE >> olcReadOnly: FALSE >> >> We have managed to collect db_stat lock information, which indicates >> the same issue with DB write locks on both DB versions. >> >> db_stat -C ol (4.8.30) >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Lock REGINFO information: >> Lock Region type >> 5 Region ID >> /apps/DECCLASA-1/data/openldap/__db.005 Region name >> 0x2ab41cdc3000 Region address >> 0x2ab41cdc3138 Region primary address >> 0 Region maximum allocation >> 0 Region allocated >> Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest >> REGION_JOIN_OK Region flags >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Locks grouped by lockers: >> Locker Mode Count Status ----------------- Object --------------- >> 1 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 >> 1 READ 1 HELD id2entry.bdb handle 0 >> 2 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 >> 3 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 >> 3 READ 1 HELD dn2id.bdb handle 0 >> 4 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 5 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 >> 6 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 >> 7 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 8 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 >> 9 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 >> 9 READ 1 HELD objectClass.bdb handle 0 >> a dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> b dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> c dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 >> c READ 1 HELD uid.bdb handle 0 >> d dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> f dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> 10 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 >> 10 READ 1 HELD member.bdb handle 0 >> 11 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 12 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 13 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 >> 13 READ 1 HELD mail.bdb handle 0 >> 14 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 15 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 16 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 17 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 18 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 >> 18 READ 1 HELD sn.bdb handle 0 >> 19 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 1a dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 1b dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 >> 1b READ 1 HELD cn.bdb handle 0 >> 1c dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 1d dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 1e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> 1f dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 >> 80000003 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 >> 80000004 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 >> 80000005 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 >> 80000006 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 >> 80000007 dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 >> 80000026 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 >> 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 >> 80000027 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 >> 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 >> 80000028 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 >> 80000028 WRITE 1 WAIT mail.bdb page 3 >> 80000028 READ 1 HELD mail.bdb page 3 >> 80000029 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 >> 80000029 WRITE 1 WAIT mail.bdb page 3 >> 80000029 READ 1 HELD mail.bdb page 3 >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Locks grouped by object: >> Locker Mode Count Status ----------------- Object --------------- >> 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 >> >> 1b READ 1 HELD cn.bdb handle 0 >> >> 10 READ 1 HELD member.bdb handle 0 >> >> 9 READ 1 HELD objectClass.bdb handle 0 >> >> c READ 1 HELD uid.bdb handle 0 >> >> 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 >> >> 1 READ 1 HELD id2entry.bdb handle 0 >> >> 18 READ 1 HELD sn.bdb handle 0 >> >> 3 READ 1 HELD dn2id.bdb handle 0 >> >> 80000029 READ 1 HELD mail.bdb page 3 >> 80000028 READ 1 HELD mail.bdb page 3 >> 80000029 WRITE 1 WAIT mail.bdb page 3 >> 80000028 WRITE 1 WAIT mail.bdb page 3 >> >> 13 READ 1 HELD mail.bdb handle 0 >> >> db_stat -C ol (4.7.25) >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Lock REGINFO information: >> Lock Region type >> 5 Region ID >> /apps/DECCLASA-1/data/openldap/__db.005 Region name >> 0x2b4a8a577000 Original region address >> 0x2b4a8a577000 Region address >> 0x2b4a8a577138 Region primary address >> 0 Region maximum allocation >> 0 Region allocated >> Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest >> REGION_JOIN_OK Region flags >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Locks grouped by lockers: >> Locker Mode Count Status ----------------- Object --------------- >> 1 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 >> 1 READ 1 HELD id2entry.bdb handle 0 >> 2 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 >> 3 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 >> 3 READ 1 HELD dn2id.bdb handle 0 >> 4 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 >> 5 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 >> 6 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 7 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 >> 7 READ 1 HELD objectClass.bdb handle 0 >> 8 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 9 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> a dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> b dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> c dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 >> c READ 1 HELD cn.bdb handle 0 >> d dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> e dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> f dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 >> f READ 1 HELD uid.bdb handle 0 >> 10 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 11 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 12 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 >> 12 READ 1 HELD member.bdb handle 0 >> 13 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 14 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 15 dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 >> 15 READ 1 HELD mail.bdb handle 0 >> 16 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 17 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 18 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 19 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 1a dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 >> 1a READ 1 HELD sn.bdb handle 0 >> 1b dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 1c dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 1d dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 1e dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 1f dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 80000003 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 >> 80000004 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 >> 80000008 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 >> 80000038 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 >> 800000a9 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 >> 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 >> 800000aa dd= 0 locks held 2 write locks 0 pid/thread 32447/1097341248 >> 800000aa WRITE 1 WAIT mail.bdb page 3 >> 800000aa READ 1 HELD mail.bdb page 1 >> 800000aa READ 1 HELD mail.bdb page 3 >> 800000ab dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 >> 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 >> 800000ac dd= 0 locks held 2 write locks 0 pid/thread 32447/1105733952 >> 800000ac WRITE 1 WAIT mail.bdb page 3 >> 800000ac READ 1 HELD mail.bdb page 1 >> 800000ac READ 1 HELD mail.bdb page 3 >> 800000b1 dd= 0 locks held 0 write locks 0 pid/thread 32447/1122519360 >> 800000b2 dd= 0 locks held 0 write locks 0 pid/thread 32447/1130912064 >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> Locks grouped by object: >> Locker Mode Count Status ----------------- Object --------------- >> 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 >> >> 1 READ 1 HELD id2entry.bdb handle 0 >> >> 3 READ 1 HELD dn2id.bdb handle 0 >> >> 7 READ 1 HELD objectClass.bdb handle 0 >> >> f READ 1 HELD uid.bdb handle 0 >> >> 1a READ 1 HELD sn.bdb handle 0 >> >> 800000aa READ 1 HELD mail.bdb page 3 >> 800000ac READ 1 HELD mail.bdb page 3 >> 800000aa WRITE 1 WAIT mail.bdb page 3 >> 800000ac WRITE 1 WAIT mail.bdb page 3 >> >> c READ 1 HELD cn.bdb handle 0 >> >> 15 READ 1 HELD mail.bdb handle 0 >> >> 800000aa READ 1 HELD mail.bdb page 1 >> 800000ac READ 1 HELD mail.bdb page 1 >> >> 12 READ 1 HELD member.bdb handle 0 >> >> 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 >> >> >> We have also collected the backtrace of threads for both DB versions >> which I have uploaded to: >> https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.8.30_ >> 20130625.txt >> >> https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.7.25_ >> 20130625.txt >> >> > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > > > -- Christian Kratzer CK Software GmbH Email: ck(a)cksoft.de Wildberger Weg 24/2 Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer

1 0

RE: (ITS#7633) Slapd hangs on hdb write lock
by dusan.fric＠t-systems.sk 28 Jun '13

28 Jun '13

Hi Chu, thanks for your quick response. We will try to contact Oracle to advice here. However, what is your suggestion here ' try different settings for the deadlock detector' exactly? BTW - certainly, we are patched DB 4.7.25 (all 4 patches)... Regards, Dusan -----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: 26. júna 2013 13:32 To: Fric, Dusan; openldap-its(a)openldap.org Subject: Re: (ITS#7633) Slapd hangs on hdb write lock dusan.fric(a)t-systems.sk wrote: > Full_Name: Dusan Fric > Version: 2.4.32 > OS: RHEL 5.7 x64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.212.40.139) > > > We are experiencing frequent hangs in slapd. Once hung we usualy > cannot continue to connect until we kill -9 the slapd process and > restart it. The directory is used for 2 applications as user eDir and > we are using it in production over 1 month - we have noted the busier > the directory becomes the more often it hangs (now twice per week). > > We have installed identical configurations on 3 environments, each has > only one single server (no replication). There are 30k entries in the > directory (production). > > We are running: > > RHEL 5.7 x64 (VMWare with NFS mountpoints) OpenLDAP 2.4.32 Berkeley DB > 4.8.30 (4.7.25) > > We were starting with DB 4.8.30, after downgrade to version 4.7.25 > (according to > ITS#7378 - > https://www.openldap.org/its/index.cgi/Incoming?id=7378;selectid=7378) > we are facing the same issue. > > The problem occurs when two requests simultaneously try to update > attributes of a record and in most cases of the same DN value. > We can easily reproduce it with a java test program running 2 threads > each connecting to the ldap server and updating the record for a > particular DN value. > It need not be the same DN value but DN values which reside on the > same BDB page. Thanks for the traces, but the information you've provided shows that this is a BDB problem, not an OpenLDAP bug. You'll have to contact Oracle for help. The BDB deadlock detector is supposed to handle these situations. For example in your 4.8.30 lock status there are only 2 conflicting transactions 80000028 and 80000029 and they are only contending on a single page. This is one of the most elementary deadlock situations. You might try different settings for the deadlock detector, but ultimately this appears to be a BDB bug and the choice of detector shouldn't matter. > Configuration > > olc cn=config (part): > dn: cn=config > objectClass: olcGlobal > cn: config > olcConcurrency: 0 > olcConnMaxPending: 100 > olcConnMaxPendingAuth: 1000 > olcSockbufMaxIncoming: 262143 > olcSockbufMaxIncomingAuth: 16777215 > olcThreads: 32 > > olc DB hdb config (part): > dn: olcDatabase={1}hdb,cn=config > objectClass: olcHdbConfig > objectClass: olcDatabaseConfig > olcDatabase: {1}hdb > olcDbCacheSize: 80000 > olcDbCheckpoint: 128 5 > olcDbConfig: {0}set_cachesize 0 268435456 1 > olcDbConfig: {1}set_lg_max 10485760 > olcDbConfig: {2}set_lg_bsize 2097152 > olcDbConfig: {3}set_lg_dir /pkg/openldap/dblog > olcDbConfig: {4}set_lg_regionmax 262144 > olcDbConfig: {5}set_lk_detect DB_LOCK_EXPIRE > olcDbConfig: {6}set_flags DB_TXN_NOSYNC > olcDbDirtyRead: FALSE > olcDbDNcacheSize: 0 > olcDbIDLcacheSize: 240000 > olcDbIndex: default eq,sub > olcDbIndex: objectClass eq > olcDbIndex: cn eq,sub > olcDbIndex: uid eq,sub > olcDbIndex: mail pres,eq > olcDbIndex: sn eq,sub > olcDbIndex: member eq > olcDbLinearIndex: FALSE > olcDbMode: 0600 > olcDbNoSync: TRUE > olcDbSearchStack: 20 > olcDbShmKey: 0 > olcLastMod: TRUE > olcMaxDerefDepth: 15 > olcMonitoring: TRUE > olcReadOnly: FALSE > > We have managed to collect db_stat lock information, which indicates > the same issue with DB write locks on both DB versions. > > db_stat -C ol (4.8.30) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Lock REGINFO information: > Lock Region type > 5 Region ID > /apps/DECCLASA-1/data/openldap/__db.005 Region name > 0x2ab41cdc3000 Region address > 0x2ab41cdc3138 Region primary address > 0 Region maximum allocation > 0 Region allocated > Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest > REGION_JOIN_OK Region flags > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by lockers: > Locker Mode Count Status ----------------- Object --------------- > 1 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 > 1 READ 1 HELD id2entry.bdb handle 0 > 2 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 3 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 > 3 READ 1 HELD dn2id.bdb handle 0 > 4 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 5 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 6 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 > 7 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 8 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 9 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 9 READ 1 HELD objectClass.bdb handle 0 > a dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > b dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > c dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > c READ 1 HELD uid.bdb handle 0 > d dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > f dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 10 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 10 READ 1 HELD member.bdb handle 0 > 11 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 12 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 13 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 13 READ 1 HELD mail.bdb handle 0 > 14 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 15 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 16 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 17 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 18 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 18 READ 1 HELD sn.bdb handle 0 > 19 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1a dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1b dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 1b READ 1 HELD cn.bdb handle 0 > 1c dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1d dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 1f dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 80000003 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 80000004 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 > 80000005 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 80000006 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 80000007 dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 80000026 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 > 80000027 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 > 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 > 80000028 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 > 80000028 WRITE 1 WAIT mail.bdb page 3 > 80000028 READ 1 HELD mail.bdb page 3 > 80000029 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 80000029 WRITE 1 WAIT mail.bdb page 3 > 80000029 READ 1 HELD mail.bdb page 3 > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by object: > Locker Mode Count Status ----------------- Object --------------- > 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 > > 1b READ 1 HELD cn.bdb handle 0 > > 10 READ 1 HELD member.bdb handle 0 > > 9 READ 1 HELD objectClass.bdb handle 0 > > c READ 1 HELD uid.bdb handle 0 > > 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 > > 1 READ 1 HELD id2entry.bdb handle 0 > > 18 READ 1 HELD sn.bdb handle 0 > > 3 READ 1 HELD dn2id.bdb handle 0 > > 80000029 READ 1 HELD mail.bdb page 3 > 80000028 READ 1 HELD mail.bdb page 3 > 80000029 WRITE 1 WAIT mail.bdb page 3 > 80000028 WRITE 1 WAIT mail.bdb page 3 > > 13 READ 1 HELD mail.bdb handle 0 > > db_stat -C ol (4.7.25) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Lock REGINFO information: > Lock Region type > 5 Region ID > /apps/DECCLASA-1/data/openldap/__db.005 Region name > 0x2b4a8a577000 Original region address > 0x2b4a8a577000 Region address > 0x2b4a8a577138 Region primary address > 0 Region maximum allocation > 0 Region allocated > Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest > REGION_JOIN_OK Region flags > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by lockers: > Locker Mode Count Status ----------------- Object --------------- > 1 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 > 1 READ 1 HELD id2entry.bdb handle 0 > 2 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 3 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 > 3 READ 1 HELD dn2id.bdb handle 0 > 4 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 > 5 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 6 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 7 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 7 READ 1 HELD objectClass.bdb handle 0 > 8 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 9 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > a dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > b dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > c dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > c READ 1 HELD cn.bdb handle 0 > d dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > e dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > f dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > f READ 1 HELD uid.bdb handle 0 > 10 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 11 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 12 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 12 READ 1 HELD member.bdb handle 0 > 13 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 14 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 15 dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 15 READ 1 HELD mail.bdb handle 0 > 16 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 17 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 18 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 19 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1a dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 1a READ 1 HELD sn.bdb handle 0 > 1b dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1c dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1d dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1e dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1f dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 80000003 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 80000004 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 80000008 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 80000038 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 > 800000a9 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 > 800000aa dd= 0 locks held 2 write locks 0 pid/thread 32447/1097341248 > 800000aa WRITE 1 WAIT mail.bdb page 3 > 800000aa READ 1 HELD mail.bdb page 1 > 800000aa READ 1 HELD mail.bdb page 3 > 800000ab dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 > 800000ac dd= 0 locks held 2 write locks 0 pid/thread 32447/1105733952 > 800000ac WRITE 1 WAIT mail.bdb page 3 > 800000ac READ 1 HELD mail.bdb page 1 > 800000ac READ 1 HELD mail.bdb page 3 > 800000b1 dd= 0 locks held 0 write locks 0 pid/thread 32447/1122519360 > 800000b2 dd= 0 locks held 0 write locks 0 pid/thread 32447/1130912064 > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by object: > Locker Mode Count Status ----------------- Object --------------- > 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 > > 1 READ 1 HELD id2entry.bdb handle 0 > > 3 READ 1 HELD dn2id.bdb handle 0 > > 7 READ 1 HELD objectClass.bdb handle 0 > > f READ 1 HELD uid.bdb handle 0 > > 1a READ 1 HELD sn.bdb handle 0 > > 800000aa READ 1 HELD mail.bdb page 3 > 800000ac READ 1 HELD mail.bdb page 3 > 800000aa WRITE 1 WAIT mail.bdb page 3 > 800000ac WRITE 1 WAIT mail.bdb page 3 > > c READ 1 HELD cn.bdb handle 0 > > 15 READ 1 HELD mail.bdb handle 0 > > 800000aa READ 1 HELD mail.bdb page 1 > 800000ac READ 1 HELD mail.bdb page 1 > > 12 READ 1 HELD member.bdb handle 0 > > 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 > > > We have also collected the backtrace of threads for both DB versions > which I have uploaded to: > https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.8.30_ > 20130625.txt > > https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.7.25_ > 20130625.txt > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7377) Poor libmdb error handling
by h.b.furuseth＠usit.uio.no 27 Jun '13

27 Jun '13

I wrote: > at > least MDB_KEYEXIST can happen after touching pages, which affects > the txn size even if the change "does nothing". Only when updating subDBs, I think. -- Hallvard

1 0

Re: (ITS#7377) Poor libmdb error handling
by h.b.furuseth＠usit.uio.no 27 Jun '13

27 Jun '13

Howard Chu writes: > h.b.furuseth(a)usit.uio.no wrote: >> Changes from a failed liblmdb operation can be visible. Sometimes >> the resulting DB will also be inconsistent. The operation should >> invalidate the affected transaction/cursors or revert the change. > > The transaction should be invalidated. Nothing more can be done > once any error occurs in a transaction. That would break back-mdb for MDB_NOTFOUND/MDB_KEYEXIST. And at least MDB_KEYEXIST can happen after touching pages, which affects the txn size even if the change "does nothing". I expected to generally invalidate except in necessary cases, and from then on make more cases "gentle" at our convenience without spending much time on it. >> put(MDB_MULTIPLE) can write some of the provided items and then >> fail, but be able to keep the txn usable. (...) > > No, "partial success" is not allowed. A transaction is atomic, all > or nothing. It would be atomic like a partial OS write(). It'd be up to the user what to do next. Not that I care myself if it is supported. >> A failed txn could still grow the txn size, unless MDB "un-touches" >> pages which memcmp says have not changed, rewinds me_pglast and >> me_pghead, etc. Which seems a lot of work, likely not worth the >> trouble. > > pghead/pglast should not persist into the environment until a successful > commit. Until then any error should just discard them. Sorry, I meant a failed _operation_ could grow them and thus affect the committed freelist size. >> I think cursors need a C_INVALID flag, so future ops cannot give a >> surprising success result instead of failing: get(MDB_NEXT/MDB_PREV) >> take ~C_INITIALIZED to mean (re)start from the beginning/end. > > Good idea. ...or C_VALID so a single OR/AND can set/clear them both. >> Don't know how often reverting is a relevant option. (...) > > Reverting is irrelevant. Once a txn is aborted no changes are visible. True, but I meant while the txn is still live and usable. Hopefully it's only relevant for "nice to have" cases. -- Hallvard

1 0

Re: (ITS#7377) Poor libmdb error handling
by hyc＠symas.com 27 Jun '13

27 Jun '13

h.b.furuseth(a)usit.uio.no wrote: > Changes from a failed liblmdb operation can be visible. Sometimes > the resulting DB will also be inconsistent. The operation should > invalidate the affected transaction/cursors or revert the change. The transaction should be invalidated. Nothing more can be done once any error occurs in a transaction. > At least I hope it's feasible to invalidate so the user cannot see > surprising results, instead of just documenting "don't do that". > > Related issues: > > put(MDB_MULTIPLE) can write some of the provided items and then > fail, but be able to keep the txn usable. It should invalidate the > txn anyway, or document that the caller must check for e.g. return > value MDB_PARTIAL_SUCCESS. Maybe invalidate unless the the caller > requests support for partial success. put() would update the input > params to indicate which items remain unwritten. No, "partial success" is not allowed. A transaction is atomic, all or nothing. > A failed txn could still grow the txn size, unless MDB "un-touches" > pages which memcmp says have not changed, rewinds me_pglast and > me_pghead, etc. Which seems a lot of work, likely not worth the > trouble. pghead/pglast should not persist into the environment until a successful commit. Until then any error should just discard them. > > I think cursors need a C_INVALID flag, so future ops cannot give a > surprising success result instead of failing: get(MDB_NEXT/MDB_PREV) > take ~C_INITIALIZED to mean (re)start from the beginning/end. Good idea. > Don't know how often reverting is a relevant option. Rearranging > code can help, but maybe not much. E.g. the mdb_del() in mdb_drop() > can do some harmless touches and then fail cleanly - but mdb_drop() > must invalidate the txn anyway since mdb_drop0() has deleted pages. > Unless it does extra work - remember mt_free_pgs[0] before and after > mdb_drop0(), then delete from mt_free_pgs[] the pages added by > drop0. Or drop0 could be done last since it can fail cleanly just > by resetting mt_free_pgs[0]. But I don't know if del(MDB_MULTIPLE) > can also do that if the DB used a subpage. drop0 can't examine the > subpage after it got deleted. > Reverting is irrelevant. Once a txn is aborted no changes are visible. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7377) Poor libmdb error handling
by h.b.furuseth＠usit.uio.no 26 Jun '13

26 Jun '13

Changes from a failed liblmdb operation can be visible. Sometimes the resulting DB will also be inconsistent. The operation should invalidate the affected transaction/cursors or revert the change. At least I hope it's feasible to invalidate so the user cannot see surprising results, instead of just documenting "don't do that". Related issues: put(MDB_MULTIPLE) can write some of the provided items and then fail, but be able to keep the txn usable. It should invalidate the txn anyway, or document that the caller must check for e.g. return value MDB_PARTIAL_SUCCESS. Maybe invalidate unless the the caller requests support for partial success. put() would update the input params to indicate which items remain unwritten. A failed txn could still grow the txn size, unless MDB "un-touches" pages which memcmp says have not changed, rewinds me_pglast and me_pghead, etc. Which seems a lot of work, likely not worth the trouble. I think cursors need a C_INVALID flag, so future ops cannot give a surprising success result instead of failing: get(MDB_NEXT/MDB_PREV) take ~C_INITIALIZED to mean (re)start from the beginning/end. Don't know how often reverting is a relevant option. Rearranging code can help, but maybe not much. E.g. the mdb_del() in mdb_drop() can do some harmless touches and then fail cleanly - but mdb_drop() must invalidate the txn anyway since mdb_drop0() has deleted pages. Unless it does extra work - remember mt_free_pgs[0] before and after mdb_drop0(), then delete from mt_free_pgs[] the pages added by drop0. Or drop0 could be done last since it can fail cleanly just by resetting mt_free_pgs[0]. But I don't know if del(MDB_MULTIPLE) can also do that if the DB used a subpage. drop0 can't examine the subpage after it got deleted. -- Hallvard

1 0

Re: (ITS#7633) Slapd hangs on hdb write lock
by hyc＠symas.com 26 Jun '13

26 Jun '13

dusan.fric(a)t-systems.sk wrote: > Full_Name: Dusan Fric > Version: 2.4.32 > OS: RHEL 5.7 x64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.212.40.139) > > > We are experiencing frequent hangs in slapd. Once hung we usualy cannot continue > to > connect until we kill -9 the slapd process and restart it. The directory is used > for 2 applications as user eDir and we are using it in production over 1 month - > we have noted the busier the directory becomes the more often it hangs (now > twice per week). > > We have installed identical configurations on 3 environments, each has only one > single server (no replication). There are 30k entries in the directory > (production). > > We are running: > > RHEL 5.7 x64 (VMWare with NFS mountpoints) > OpenLDAP 2.4.32 > Berkeley DB 4.8.30 (4.7.25) > > We were starting with DB 4.8.30, after downgrade to version 4.7.25 (according to > ITS#7378 - https://www.openldap.org/its/index.cgi/Incoming?id=7378;selectid=7378) > we are facing the same issue. Note that BDB 4.7.25 is known to self-deadlock if you haven't applied all of the patches. http://www.oracle.com/technetwork/products/berkeleydb/patch-088170.html -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7633) Slapd hangs on hdb write lock
by hyc＠symas.com 26 Jun '13

26 Jun '13

dusan.fric(a)t-systems.sk wrote: > Full_Name: Dusan Fric > Version: 2.4.32 > OS: RHEL 5.7 x64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.212.40.139) > > > We are experiencing frequent hangs in slapd. Once hung we usualy cannot continue > to > connect until we kill -9 the slapd process and restart it. The directory is used > for 2 applications as user eDir and we are using it in production over 1 month - > we have noted the busier the directory becomes the more often it hangs (now > twice per week). > > We have installed identical configurations on 3 environments, each has only one > single server (no replication). There are 30k entries in the directory > (production). > > We are running: > > RHEL 5.7 x64 (VMWare with NFS mountpoints) > OpenLDAP 2.4.32 > Berkeley DB 4.8.30 (4.7.25) > > We were starting with DB 4.8.30, after downgrade to version 4.7.25 (according to > ITS#7378 - https://www.openldap.org/its/index.cgi/Incoming?id=7378;selectid=7378) > we are facing the same issue. > > The problem occurs when two requests simultaneously try to update attributes of > a record and in most cases of the same DN value. > We can easily reproduce it with a java test program running 2 threads each > connecting to the ldap server and updating the record for a particular DN > value. > It need not be the same DN value but DN values which reside on the same BDB > page. Thanks for the traces, but the information you've provided shows that this is a BDB problem, not an OpenLDAP bug. You'll have to contact Oracle for help. The BDB deadlock detector is supposed to handle these situations. For example in your 4.8.30 lock status there are only 2 conflicting transactions 80000028 and 80000029 and they are only contending on a single page. This is one of the most elementary deadlock situations. You might try different settings for the deadlock detector, but ultimately this appears to be a BDB bug and the choice of detector shouldn't matter. > Configuration > > olc cn=config (part): > dn: cn=config > objectClass: olcGlobal > cn: config > olcConcurrency: 0 > olcConnMaxPending: 100 > olcConnMaxPendingAuth: 1000 > olcSockbufMaxIncoming: 262143 > olcSockbufMaxIncomingAuth: 16777215 > olcThreads: 32 > > olc DB hdb config (part): > dn: olcDatabase={1}hdb,cn=config > objectClass: olcHdbConfig > objectClass: olcDatabaseConfig > olcDatabase: {1}hdb > olcDbCacheSize: 80000 > olcDbCheckpoint: 128 5 > olcDbConfig: {0}set_cachesize 0 268435456 1 > olcDbConfig: {1}set_lg_max 10485760 > olcDbConfig: {2}set_lg_bsize 2097152 > olcDbConfig: {3}set_lg_dir /pkg/openldap/dblog > olcDbConfig: {4}set_lg_regionmax 262144 > olcDbConfig: {5}set_lk_detect DB_LOCK_EXPIRE > olcDbConfig: {6}set_flags DB_TXN_NOSYNC > olcDbDirtyRead: FALSE > olcDbDNcacheSize: 0 > olcDbIDLcacheSize: 240000 > olcDbIndex: default eq,sub > olcDbIndex: objectClass eq > olcDbIndex: cn eq,sub > olcDbIndex: uid eq,sub > olcDbIndex: mail pres,eq > olcDbIndex: sn eq,sub > olcDbIndex: member eq > olcDbLinearIndex: FALSE > olcDbMode: 0600 > olcDbNoSync: TRUE > olcDbSearchStack: 20 > olcDbShmKey: 0 > olcLastMod: TRUE > olcMaxDerefDepth: 15 > olcMonitoring: TRUE > olcReadOnly: FALSE > > We have managed to collect db_stat lock information, which indicates the same > issue with DB write locks on both DB versions. > > db_stat -C ol (4.8.30) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Lock REGINFO information: > Lock Region type > 5 Region ID > /apps/DECCLASA-1/data/openldap/__db.005 Region name > 0x2ab41cdc3000 Region address > 0x2ab41cdc3138 Region primary address > 0 Region maximum allocation > 0 Region allocated > Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest > REGION_JOIN_OK Region flags > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by lockers: > Locker Mode Count Status ----------------- Object --------------- > 1 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 > 1 READ 1 HELD id2entry.bdb handle 0 > 2 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 3 dd= 0 locks held 1 write locks 0 pid/thread 30034/47555767609232 > 3 READ 1 HELD dn2id.bdb handle 0 > 4 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 5 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 6 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 > 7 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 8 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 9 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 9 READ 1 HELD objectClass.bdb handle 0 > a dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > b dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > c dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > c READ 1 HELD uid.bdb handle 0 > d dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > f dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 10 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 10 READ 1 HELD member.bdb handle 0 > 11 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 12 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 13 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 13 READ 1 HELD mail.bdb handle 0 > 14 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 15 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 16 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 17 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 18 dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 18 READ 1 HELD sn.bdb handle 0 > 19 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1a dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1b dd= 0 locks held 1 write locks 0 pid/thread 30034/1147971904 > 1b READ 1 HELD cn.bdb handle 0 > 1c dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1d dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 1e dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 1f dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 80000003 dd= 0 locks held 0 write locks 0 pid/thread 30034/47555767609232 > 80000004 dd= 0 locks held 0 write locks 0 pid/thread 30034/1139579200 > 80000005 dd= 0 locks held 0 write locks 0 pid/thread 30034/1147971904 > 80000006 dd= 0 locks held 0 write locks 0 pid/thread 30034/1131186496 > 80000007 dd= 0 locks held 0 write locks 0 pid/thread 30034/1122793792 > 80000026 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 > 80000027 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 > 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 > 80000028 dd= 0 locks held 1 write locks 0 pid/thread 30034/1131186496 > 80000028 WRITE 1 WAIT mail.bdb page 3 > 80000028 READ 1 HELD mail.bdb page 3 > 80000029 dd= 0 locks held 1 write locks 0 pid/thread 30034/1122793792 > 80000029 WRITE 1 WAIT mail.bdb page 3 > 80000029 READ 1 HELD mail.bdb page 3 > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by object: > Locker Mode Count Status ----------------- Object --------------- > 80000027 READ 1 HELD 0x36490 len: 9 data: 0x370000000000000000 > > 1b READ 1 HELD cn.bdb handle 0 > > 10 READ 1 HELD member.bdb handle 0 > > 9 READ 1 HELD objectClass.bdb handle 0 > > c READ 1 HELD uid.bdb handle 0 > > 80000026 READ 1 HELD 0x5e948 len: 9 data: 0x560x0500000000000000 > > 1 READ 1 HELD id2entry.bdb handle 0 > > 18 READ 1 HELD sn.bdb handle 0 > > 3 READ 1 HELD dn2id.bdb handle 0 > > 80000029 READ 1 HELD mail.bdb page 3 > 80000028 READ 1 HELD mail.bdb page 3 > 80000029 WRITE 1 WAIT mail.bdb page 3 > 80000028 WRITE 1 WAIT mail.bdb page 3 > > 13 READ 1 HELD mail.bdb handle 0 > > db_stat -C ol (4.7.25) > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Lock REGINFO information: > Lock Region type > 5 Region ID > /apps/DECCLASA-1/data/openldap/__db.005 Region name > 0x2b4a8a577000 Original region address > 0x2b4a8a577000 Region address > 0x2b4a8a577138 Region primary address > 0 Region maximum allocation > 0 Region allocated > Region allocations: 3006 allocations, 0 failures, 0 frees, 1 longest > REGION_JOIN_OK Region flags > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by lockers: > Locker Mode Count Status ----------------- Object --------------- > 1 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 > 1 READ 1 HELD id2entry.bdb handle 0 > 2 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 3 dd= 0 locks held 1 write locks 0 pid/thread 32447/47463753631632 > 3 READ 1 HELD dn2id.bdb handle 0 > 4 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 > 5 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 6 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 7 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 7 READ 1 HELD objectClass.bdb handle 0 > 8 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 9 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > a dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > b dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > c dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > c READ 1 HELD cn.bdb handle 0 > d dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > e dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > f dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > f READ 1 HELD uid.bdb handle 0 > 10 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 11 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 12 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 12 READ 1 HELD member.bdb handle 0 > 13 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 14 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 15 dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 15 READ 1 HELD mail.bdb handle 0 > 16 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 17 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 18 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 19 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1a dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 1a READ 1 HELD sn.bdb handle 0 > 1b dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1c dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1d dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1e dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 1f dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 80000003 dd= 0 locks held 0 write locks 0 pid/thread 32447/47463753631632 > 80000004 dd= 0 locks held 0 write locks 0 pid/thread 32447/1097341248 > 80000008 dd= 0 locks held 0 write locks 0 pid/thread 32447/1105733952 > 80000038 dd= 0 locks held 0 write locks 0 pid/thread 32447/1114126656 > 800000a9 dd= 0 locks held 1 write locks 0 pid/thread 32447/1097341248 > 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 > 800000aa dd= 0 locks held 2 write locks 0 pid/thread 32447/1097341248 > 800000aa WRITE 1 WAIT mail.bdb page 3 > 800000aa READ 1 HELD mail.bdb page 1 > 800000aa READ 1 HELD mail.bdb page 3 > 800000ab dd= 0 locks held 1 write locks 0 pid/thread 32447/1105733952 > 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 > 800000ac dd= 0 locks held 2 write locks 0 pid/thread 32447/1105733952 > 800000ac WRITE 1 WAIT mail.bdb page 3 > 800000ac READ 1 HELD mail.bdb page 1 > 800000ac READ 1 HELD mail.bdb page 3 > 800000b1 dd= 0 locks held 0 write locks 0 pid/thread 32447/1122519360 > 800000b2 dd= 0 locks held 0 write locks 0 pid/thread 32447/1130912064 > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Locks grouped by object: > Locker Mode Count Status ----------------- Object --------------- > 800000a9 READ 1 HELD 0x2d228 len: 9 data: 0x370000000000000000 > > 1 READ 1 HELD id2entry.bdb handle 0 > > 3 READ 1 HELD dn2id.bdb handle 0 > > 7 READ 1 HELD objectClass.bdb handle 0 > > f READ 1 HELD uid.bdb handle 0 > > 1a READ 1 HELD sn.bdb handle 0 > > 800000aa READ 1 HELD mail.bdb page 3 > 800000ac READ 1 HELD mail.bdb page 3 > 800000aa WRITE 1 WAIT mail.bdb page 3 > 800000ac WRITE 1 WAIT mail.bdb page 3 > > c READ 1 HELD cn.bdb handle 0 > > 15 READ 1 HELD mail.bdb handle 0 > > 800000aa READ 1 HELD mail.bdb page 1 > 800000ac READ 1 HELD mail.bdb page 1 > > 12 READ 1 HELD member.bdb handle 0 > > 800000ab READ 1 HELD 0x43d58 len: 9 data: 0x540x0500000000000000 > > > We have also collected the backtrace of threads for both DB versions which I > have uploaded to: > https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.8.30_20130… > > https://dl.dropboxusercontent.com/u/92115703/dusan_gdb_threads_4.7.25_20130… > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs