--On Thursday, April 13, 2006 12:38 AM +0200 Pierangelo Masarati
<[EMAIL PROTECTED]> wrote:
On Wed, 2006-04-12 at 14:01 -0700, Quanah Gibson-Mount wrote:
--On Wednesday, April 12, 2006 10:54 PM +0200 Pierangelo Masarati
<[EMAIL PROTECTED]> wrote:
> I don't remember the details, but I'm p
On Wed, 2006-04-12 at 14:01 -0700, Quanah Gibson-Mount wrote:
>
> --On Wednesday, April 12, 2006 10:54 PM +0200 Pierangelo Masarati
> <[EMAIL PROTECTED]> wrote:
>
>
> > I don't remember the details, but I'm pretty sure there's no binary
> > compatibility between database files created by OpenLD
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> > ldbm_back_db_open: alock package is unstable; database may be
> > inconsistent!
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
> > slapd starting
> >
> >
> > Can I get
matthew sporleder wrote:
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
slapd starting
Can I get a status on alock for LDBM?
Accord
--On Wednesday, April 12, 2006 4:39 PM -0400 matthew sporleder
<[EMAIL PROTECTED]> wrote:
I would really rethink using LDBM, especially since you are upgrading to
a modern version of OpenLDAP.
Now that you've started slapd, and alock is created, does LDBM continue
to complain, or are things
--On Wednesday, April 12, 2006 10:54 PM +0200 Pierangelo Masarati
<[EMAIL PROTECTED]> wrote:
I don't remember the details, but I'm pretty sure there's no binary
compatibility between database files created by OpenLDAP 2.1 and
OpenLDAP 2.3; in general, you shouldn't expect anything like that
--On Wednesday, April 12, 2006 4:56 PM -0300 "Marcelo H. Terres"
<[EMAIL PROTECTED]> wrote:
Hi.
Sorry, forget my older e-mail.
I compiled my openldap 2.3.21 with CPPFLAGS="-DOPENLDAP_FD_SETSIZE=8192"
I ran ulimit -n 8192.
But I'm still can't open more than 1024 ldap connections simultane
Quanah Gibson-Mount wrote:
By the way, your best strategy at this point is to stop slapd, wipe
out the database you created, and then start over now that you have a
better understanding of how things work.
good idea, I'll pick up the Oreilly LDAP book too :)
--On Wednesday, April 12, 2006 4:18 PM -0400 matthew sporleder
<[EMAIL PROTECTED]> wrote:
> Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> ldbm_back_db_open: alock package is unstable; database may be
> inconsistent!
> Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 10011
Hi.
Sorry, forget my older e-mail.
I compiled my openldap 2.3.21 with CPPFLAGS="-DOPENLDAP_FD_SETSIZE=8192"
I ran ulimit -n 8192.
But I'm still can't open more than 1024 ldap connections simultaneously.
Any ideas ?
Thanks.
--
Marcelo H. Terres
[EMAIL PROTECTED]
On Wed, 2006-04-12 at 16:18 -0400, matthew sporleder wrote:
> I wasn't aware that LDBM was susceptible to the same inconsistencies
> as BDB. I thought the lack of transactions/checkpointing prevented
> this. And if this situation did occur, I thought 2.3 was smart enough
> to try fixing itself.
> >> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> >> > ldbm_back_db_open: alock package is unstable; database may be
> >> > inconsistent!
> >> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
> >> > slapd starting
> >> >
> >> >
> >> > Can I get a status
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> > ldbm_back_db_open: alock package is unstable; database may be
> > inconsistent!
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
> > slapd starting
> >
> >
> > Can I get a status on alock for LDBM?
> >
--On Wednesday, April 12, 2006 4:10 PM -0400 matthew sporleder
<[EMAIL PROTECTED]> wrote:
> Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> ldbm_back_db_open: alock package is unstable; database may be
> inconsistent!
> Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 10011
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> > ldbm_back_db_open: alock package is unstable; database may be
> > inconsistent!
> > Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
> > slapd starting
> >
> >
> > Can I get a status on alock for LDBM?
> >
matthew sporleder wrote:
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
slapd starting
Can I get a status on alock for LDBM?
Accord
--On Wednesday, April 12, 2006 12:11 PM -0500 Adam Williams
<[EMAIL PROTECTED]> wrote:
same error still.
By the way, your best strategy at this point is to stop slapd, wipe out the
database you created, and then start over now that you have a better
understanding of how things work.
--On Wednesday, April 12, 2006 3:33 PM -0400 matthew sporleder
<[EMAIL PROTECTED]> wrote:
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6
Hi.
I compiled my openldap 2.3.21 with CPPFLAGS="-DFD_SETSIZE=8192".
I ran ulimit -n 8192.
But I'm still can't open more than 1024 ldap connections simultaneously.
Any ideas ?
Thanks.
--
Marcelo H. Terres
[EMAIL PROTECTED]
(You'd think I would know by now)
I'm running openldap 2.3.21, bdb 4.4.20, and solaris 10.
On 4/12/06, matthew sporleder <[EMAIL PROTECTED]> wrote:
> Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
> ldbm_back_db_open: alock package is unstable; database may be
> inconsistent!
>
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
slapd starting
Can I get a status on alock for LDBM?
According to:
http://www.openldap
--On Wednesday, April 12, 2006 12:11 PM -0500 Adam Williams
<[EMAIL PROTECTED]> wrote:
Quanah Gibson-Mount wrote:
Okay, now lets add your search base to this search. Add the flag:
-b "dc=mdah,dc=state,dc=ms,dc=us"
same error still.
Sounds like that tree doesn't exist then.
--Q
Quanah Gibson-Mount wrote:
Okay, now lets add your search base to this search. Add the flag:
-b "dc=mdah,dc=state,dc=ms,dc=us"
same error still.
ldapsearch -x -D "cn=adam,dc=mdah,dc=state,dc=ms,dc=us" -W -b
"dc=mdah,dc=state,dc=ms,dc=us"
Enter LDAP Password:
# extended LDIF
#
# LDAP
At 07:45 AM 4/12/2006, Michael Ströder wrote:
>Kurt D. Zeilenga wrote:
>> I note that, in 2.4, we hope to introduce a control which will allow
>> administrators (and other authorized users) to request this (and
>> other) restrictions be temporarily relaxed.
>
>We have to wait for 2.4 to see support
--On Wednesday, April 12, 2006 3:42 PM +0200 Guillaume Rousse
<[EMAIL PROTECTED]> wrote:
Hello.
I'm having troubles with replication using sync-repl.
I first configured my provider and consumer servers as explained on
http://www.openldap.org/doc/admin22/syncrepl.html.
I would advise not
Kurt D. Zeilenga wrote:
>
> I note that, in 2.4, we hope to introduce a control which will allow
> administrators (and other authorized users) to request this (and
> other) restrictions be temporarily relaxed.
We have to wait for 2.4 to see support for the ManageDIT control?
I hoped to have it so
--On Wednesday, April 12, 2006 5:38 AM -0500 Adam Williams
<[EMAIL PROTECTED]> wrote:
Quanah Gibson-Mount wrote:
Look at your ldapadd command:
ldapadd -x -D "cn=adam,dc=mdah,dc=state,dc=ms,dc=us" -W -h
Now, all you need to do is change "add" to "search" and remove the -h
at the end.
--On Wednesday, April 12, 2006 10:33 AM +0200 Lorenz Krause
<[EMAIL PROTECTED]> wrote:
Hello
I want to add a person into my LDAP database, but i get the following
error back:
ldap_sasl_interactive_bind_s: Internal (implementation specific) error
(80) additional info: SASL (-13): user not fo
--On Wednesday, April 12, 2006 8:30 AM -0700 Taolizhong
<[EMAIL PROTECTED]> wrote:
Thanks Quanah. I had to use kill -9 because slapd hadn't responsed to
any other signals. In addition, as I mentioned in my first message, I
even tried to recompile the package and ran "make test" (without
It would be useful, I think, for you to illustrate the authentication
success and failure using an OpenLDAP command line tool, such as
ldapwhoami(1) (providing both command input and output) and the
associated slapd(8) logging for each. For instance, this would
clarify whether you are doing LDAP/S
>> Our openldap 2.2.24 running on Solaris 9 x86 suddently stopped
>> functioning this morning:( .
>>
>> It can still be started up but doesn't give any response to queries:
>>
>> # ps -ef |grep slapd
>> root 648 1 0 11:18:33 ? 0:00
>> /usr/local/libexec/slapd -h ldap:/// ldaps:///
>>
>> # ld
> Our openldap 2.2.24 running on Solaris 9 x86 suddently stopped functioning
this morning:( .
>
> It can still be started up but doesn't give any response to queries:
>
> # ps -ef |grep slapd
> root 648 1 0 11:18:33 ? 0:00 /usr/local/libexec/slapd -h ldap:/// ldaps:///
>
> # ldapsearch -x "uid
Hello
I want to add a person into my LDAP database, but i get the following error
back:
ldap_sasl_interactive_bind_s: Internal (implementation specific) error (80)
additional info: SASL (-13): user not found: no secret in database
Does anyone can help me with this problem?
>
>
> Quanah Gibson-Mount wrote:
>>
>> Look at your ldapadd command:
>>
>> ldapadd -x -D "cn=adam,dc=mdah,dc=state,dc=ms,dc=us" -W -h
>>
>> Now, all you need to do is change "add" to "search" and remove the -h
>> at the end.
>>
>>
>
> cool, thanks. I am still getting the same result, though.
>
> l
Hello.
I'm having troubles with replication using sync-repl.
I first configured my provider and consumer servers as explained on
http://www.openldap.org/doc/admin22/syncrepl.html.
Additional directives for the provider:
# replication management
sessionlog 001 500
Additional directives for
Quanah Gibson-Mount wrote:
Look at your ldapadd command:
ldapadd -x -D "cn=adam,dc=mdah,dc=state,dc=ms,dc=us" -W -h
Now, all you need to do is change "add" to "search" and remove the -h
at the end.
cool, thanks. I am still getting the same result, though.
ldapsearch -x -D "cn=adam,dc
I have a couple of users whom the following sasl-regexp stanza is not
catching. Strange since all user accounts are identical.
sasl-regexp
uid=(.*),cn=internal.epo.org,cn=gssapi,cn=auth
uid=$1,ou=people,ou=internal,dc=epo,dc=org
I am fairly sure that OpenLDAP is not passing them
Make sure that a password has been set. Look for
olcRootPW
in the file
olcDatabase={0}config.ldif
If you are generating cn=config configuration from slapd.conf file with
slaptest make sure that slapd.conf holds lines like
database config
rootpw secret
Niels Frimodt Sørensen
-Oprindelig
38 matches
Mail list logo
