openldap-bugs April 2012

openldap-bugs@openldap.org

36 participants
172 discussions

Re: (ITS#7229) still not fixed
by michael＠stroeder.com 14 Apr '12

14 Apr '12

hyc(a)symas.com wrote: > Your problem is completely unrelated to ITS#7229, which was about an ENOSPC > error. You're getting ENOMEM, which simply means you've exceeded the > configured size of the DB. Yes, forgot setting maxsize. Sorry. Ciao, Michael.

1 0

Re: (ITS#7229) still not fixed
by hyc＠symas.com 14 Apr '12

14 Apr '12

michael(a)stroeder.com wrote: > This is a cryptographically signed message in MIME format. > > --------------ms000002080400040504030402 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > HI! > > I'm testing with RE24 (39fb7afe5f5acb48686a41a11ef57aa72a772626) on openS= > USE > 11.4 x86_64 but I'm still getting this error when loading an accesslog DB= > =2E It > is not fixed yet. > > slapadd: could not add entry dn=3D"reqStart=3D20110131134340.000002Z,cn=3D= > accesslog" > (line=3D270877): txn_aborted! Internal error (80) > 4f897bb9 mdb_id2entry_put: mdb_put failed: Cannot allocate memory(12) > "reqStart=3D20110201074944.000001Z,cn=3Daccesslog" Your problem is completely unrelated to ITS#7229, which was about an ENOSPC error. You're getting ENOMEM, which simply means you've exceeded the configured size of the DB. > The problem is that adding most entries does work but the error happens > occasionally no matter whether -q is used or not. > > Ciao, Michael. -- -- 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#7229) still not fixed
by michael＠stroeder.com 14 Apr '12

14 Apr '12

This is a cryptographically signed message in MIME format. --------------ms000002080400040504030402 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable HI! I'm testing with RE24 (39fb7afe5f5acb48686a41a11ef57aa72a772626) on openS= USE 11.4 x86_64 but I'm still getting this error when loading an accesslog DB= =2E It is not fixed yet. slapadd: could not add entry dn=3D"reqStart=3D20110131134340.000002Z,cn=3D= accesslog" (line=3D270877): txn_aborted! Internal error (80) 4f897bb9 mdb_id2entry_put: mdb_put failed: Cannot allocate memory(12) "reqStart=3D20110201074944.000001Z,cn=3Daccesslog" The problem is that adding most entries does work but the error happens occasionally no matter whether -q is used or not. Ciao, Michael. --------------ms000002080400040504030402 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFOzCC BTcwggMfoAMCAQICAwl4kDANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMDEx MTcxNTQzMzFaFw0xMjExMTYxNTQzMzFaMD8xGDAWBgNVBAMUD01pY2hhZWwgU3Ry9mRlcjEj MCEGCSqGSIb3DQEJARYUbWljaGFlbEBzdHJvZWRlci5jb20wggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDo2SKth5GhtaDrCyfGtyUG+/hAAa/J52L0NFN4SSRvTtdGf9HfWwwd NCtgae0TVGWk2lKDbXA9d5vmyIiRhuwxd90H6FLErhRBeB9G67qtw87E8WUoXt2DwPQEUTWV hqHpPadlmgFw3+i3TGQQTe3O3W9MMMd4GJNhObem2VGRuCD37OXnzBksTcq0FPJgcWAhe3d/ 0ItOkNWBqgq8Mf3p7WFBhaQ0a27BC/mKtH8fI3kPcS305imPRja69Msq3EwUZBc9ToVp6FRQ NYKjfOBybDUzVkmRZl3H8xutQP2w8Zxb8m5f7Q1BfLLrIFScfYvIDgOERxTCd4lab8+/09XH AgMBAAGjggEAMIH9MAwGA1UdEwEB/wQCMAAwVgYJYIZIAYb4QgENBEkWR1RvIGdldCB5b3Vy IG93biBjZXJ0aWZpY2F0ZSBmb3IgRlJFRSBoZWFkIG92ZXIgdG8gaHR0cDovL3d3dy5DQWNl cnQub3JnMEAGA1UdJQQ5MDcGCCsGAQUFBwMEBggrBgEFBQcDAgYKKwYBBAGCNwoDBAYKKwYB BAGCNwoDAwYJYIZIAYb4QgQBMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcwAYYWaHR0cDov L29jc3AuY2FjZXJ0Lm9yZzAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkq hkiG9w0BAQUFAAOCAgEANPf/aLF41eQlvN5dEg3CFnlN//qQK7+EPIXLnHprNWLb4nBwgdPj /E+qa1umT7px4Py3VS0UTKqLmMdWftwid8MOMHWalZwrfx0Z8U3He+EdJhOSnn9vdd/ug7Xd dI/hRjLaBSq9ZhCczEUgL6vTxCYPlIoHF56y/oxSJw59vRBjvRFKXvpBZWseeRkcGACQduNH SNdWC1IqHAbQlgOS9VWQUYlm//BdaLkezRxqnQp5+KJMAcZzHpdNJ3G4SqCJ02Z3n4kk8IKZ AjgiWxisDFNsfXKDb9Ng5ntnnH2ouxrgPoNnW445tgkz50VKHstylx9s5O3G7uUTtg0J+z63 TA8xbN6kzRx7RgAUkEXhl6WEdW+3EVj5tYY38Uy8vleP+gYZfphKEmQJgIQqy9D2+gesbolT QdWYgbUYY2AHJOshskMW7pahYnFX2pZmn/ayaPc+JFJlCEqO0+DcYQjYuv6sntQgZGkok7yZ R4xMbyCp61pTrfGWOufZs/FiScJZg1IWY5qb4URH4VZZjLNMR2pFMRuE4LvgkkMRasbUv7Yv n3Lzv34lTfJKUqYW6nx//L2NS4rN63o0taPwRygnuBK4kp7EYEcwtLeanJhQoIu4b6If9rwy D7CFAp51wIewV9VtZ1Is0irNBcMVyhJogIcuIn+VWY1ff1RxySD/djMxggOUMIIDkAIBATCB gDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcx IjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1 cHBvcnRAY2FjZXJ0Lm9yZwIDCXiQMAkGBSsOAwIaBQCgggHoMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDQxNDEzMzgyOVowIwYJKoZIhvcNAQkEMRYE FKKKmWqR32lsW+TjX16Hc69krw+dMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoG CCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggq hkiG9w0DAgIBKDCBkQYJKwYBBAGCNxAEMYGDMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAc BgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5n IEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMJeJAwgZMG CyqGSIb3DQEJEAILMYGDoIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6 Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEh MB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMJeJAwDQYJKoZIhvcNAQEBBQAE ggEAbbQYCiOcoNfziXvc8fZxpKVoCT37MQv9Se72yCki6aW7JscIVueaH82mYczG5sba6V94 ayQiMhLeGq+LTlqpN9ZacEm1/SgN8Nfh9NU70F564Zw34YZ78PPVpodxy8e/IB4EX6sV3vaq XGNObPCBUKhMrXIvJ4nmjgzDbDcH9gTxY3WxHfU3JQlzI89s3bwVNVLmb5ET1XEi+3kAbrik CdjO0ysc9abDarLzp9jKkElzVb1Tb3xRygFEyLtPmqfQMktHIhIqUlWkbo3+w9WpoH0obHLd UV9k3F3A7EYSeYVvA9N5mcNcTyDt4SKybNIT9rbMxQzv44DCfJ12MUHXyQAAAAAAAA== --------------ms000002080400040504030402--

1 0

Re: (ITS#7243) sudo: uid 14281 does not exist in the passwd file!
by masarati＠aero.polimi.it 13 Apr '12

13 Apr '12

> Full_Name: Natarrajan > Version: 2.2.13-7.4E > OS: RHEL4.5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (216.113.168.128) > > > I am getting the following error frequently in my ldap client machine. > > LDAPCLIENT ~> whoami > whoami: cannot find name for user ID 14281 > LDAPCLIENT ~> sudo -u qserv ls > sudo: uid 14281 does not exist in the passwd file! > > Let me know the fix for the issue. Upgrade (2.2.13 is about 10 years old now; 2.4.30 is the current release). Then, fix the configuration of your nss? p.

1 0

(ITS#7244) sudo: uid 14281 does not exist in the passwd file!
by napalaniappan＠yahoo.com 13 Apr '12

13 Apr '12

Full_Name: Natarrajan Version: 2.2.13-7.4E OS: RHEL4.5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (216.113.168.128) I am getting the following error frequently in my ldap client machine. LDAPCLIENT ~> whoami whoami: cannot find name for user ID 14281 LDAPCLIENT ~> sudo -u qserv ls sudo: uid 14281 does not exist in the passwd file! Let me know the fix for the issue. Thanks,

1 0

(ITS#7243) sudo: uid 14281 does not exist in the passwd file!
by napalaniappan＠paypal.com 13 Apr '12

13 Apr '12

1 0

Re: (ITS#7242) new -y (Read password from file) does not work
by chris.paul＠rexconsulting.net 13 Apr '12

13 Apr '12

Oh duh. I see now. Thanks! CP On Apr 13, 2012, at 13:59, masarati(a)aero.polimi.it wrote: >> Full_Name: Chris Paul >> Version: ldapsearch 2.4.23 (Dec 7 2011 21:37:03) >> OS: tried both Centos 2.6.32-220.el6.i686 and Cygwin >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (162.119.68.25) >> >> >> I really like the new -y option to read the password from a file but it >> doesn't >> work. Also it broke the old behavior which read it from standard input if >> you >> used -W. >> >> I have a one line password file. I used to use this successfully with a >> command >> like: >> >> $ ldapsearch -x -H $TIM -s sub -b "dc=myorg, dc=org" "(uid=someuid)" uid >> cn < >> ~/.ldappw >> >> Now this command just prompts me for the password. >> >> And when I try -y, it seems that an 0x0a character is added to the >> password >> string (I found this by using tcpdump to capture the packets), so that >> fails >> with "Invalid credentials (49)". > > This is a common user error. The "0x0a" is a newline ('\n') which is > probably present in your file. You need to create a file that contains > exactly the password. For example, to create a file that contains the > password "secret" you need to do > > echo -n "secret" > filename. > > This ITS will be closed. > > p. >

1 0

Re: (ITS#7242) new -y (Read password from file) does not work
by masarati＠aero.polimi.it 13 Apr '12

13 Apr '12

> Full_Name: Chris Paul > Version: ldapsearch 2.4.23 (Dec 7 2011 21:37:03) > OS: tried both Centos 2.6.32-220.el6.i686 and Cygwin > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (162.119.68.25) > > > I really like the new -y option to read the password from a file but it > doesn't > work. Also it broke the old behavior which read it from standard input if > you > used -W. > > I have a one line password file. I used to use this successfully with a > command > like: > > $ ldapsearch -x -H $TIM -s sub -b "dc=myorg, dc=org" "(uid=someuid)" uid > cn < > ~/.ldappw > > Now this command just prompts me for the password. > > And when I try -y, it seems that an 0x0a character is added to the > password > string (I found this by using tcpdump to capture the packets), so that > fails > with "Invalid credentials (49)". This is a common user error. The "0x0a" is a newline ('\n') which is probably present in your file. You need to create a file that contains exactly the password. For example, to create a file that contains the password "secret" you need to do echo -n "secret" > filename. This ITS will be closed. p.

1 0

(ITS#7242) new -y (Read password from file) does not work
by chris.paul＠rexconsulting.net 13 Apr '12

13 Apr '12

Full_Name: Chris Paul Version: ldapsearch 2.4.23 (Dec 7 2011 21:37:03) OS: tried both Centos 2.6.32-220.el6.i686 and Cygwin URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (162.119.68.25) I really like the new -y option to read the password from a file but it doesn't work. Also it broke the old behavior which read it from standard input if you used -W. I have a one line password file. I used to use this successfully with a command like: $ ldapsearch -x -H $TIM -s sub -b "dc=myorg, dc=org" "(uid=someuid)" uid cn < ~/.ldappw Now this command just prompts me for the password. And when I try -y, it seems that an 0x0a character is added to the password string (I found this by using tcpdump to capture the packets), so that fails with "Invalid credentials (49)".

1 0

Re: (ITS#7212) slapmodify support for back-config
by ondrej.kuznik＠acision.com 13 Apr '12

13 Apr '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/20/2012 11:11 AM, ondrej.kuznik(a)acision.com wrote: > For slapmodify to be usable on a database, that database needs to > implement the bi_tool_dn2id_get and bi_tool_entry_modify > functions, which is not the case of the back-config. I've put > together a minimal (and maybe too naive) implementation of these > for back-config and back-ldif at the above link. Ok, nevermind for now, the implementation was too naive and would break some other things (the slapadd in test005). - -- Ondrej Kuznik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IMUkACgkQ9GWxeeH+cXtodQCeJdq8IQvH+hWEYTTMt3hn+6UC K20An0uaLb/lmDo6zBJtHm3RL9FMXezq =xnVE -----END PGP SIGNATURE----- This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs April 2012