"Dennis Misc" <[EMAIL PROTECTED]> writes:
>> > It seems that the binddn is listed on the database. Here is the relevant
>> > output from the slapcat command:
>>
>> I do hope that binddn is not rootdn, otherwise it would be a rather
>> bad idea.
>> [...]
>
> Pardon my ignorance, what is the problem
Quanah Gibson-Mount wrote:
--On Thursday, July 20, 2006 3:21 PM -0700 Ski Kacoroski
<[EMAIL PROTECTED]> wrote:
Hi,
I am using version 2.3.24 and syncrepl. On the master I have:
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
index entryCSN,entryUUID
--On Thursday, July 20, 2006 3:21 PM -0700 Ski Kacoroski
<[EMAIL PROTECTED]> wrote:
Hi,
I am using version 2.3.24 and syncrepl. On the master I have:
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
index entryCSN,entryUUID eq
Hi Ski,
Hi,
I am using version 2.3.24 and syncrepl. On the master I have:
overlay syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100
index entryCSN,entryUUID eq
On the first replica I have:
syncrepl rid=12
provider=ldaps://srvld01.nsd.org:636
interval=00:00
Dennis Misc wrote:
> It seems that the binddn is listed on the database. Here is the
relevant
> output from the slapcat command:
I do hope that binddn is not rootdn, otherwise it would be a rather
bad idea.
[...]
Pardon my ignorance, what is the problem using the rootdn as binddn?
rootdn h
Hello,
"Daniel Maher" <[EMAIL PROTECTED]> writes:
> Hello all (again),
>
>
>
> Regarding the segfault (see previous email, or quote below); a small
> addition to slapd.conf eliminates the condition that was causing the
> fault:
>
> slapd.conf:
>
> proxyAttrset 0 proxyAddress
>
> proxyTemplate
Quanah Gibson-Mount wrote:
--On Thursday, July 20, 2006 9:58 PM +0200 Tomasz Chmielewski
<[EMAIL PROTECTED]> wrote:
Matthew Hardin wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-openldap-
[EMAIL PROTECTED] On Behalf Of Daniel Maher
Sent: Thursday, July 20, 2006 7:5
On Thu, Jul 20, 2006 at 09:55:46PM +0200, Tomasz Chmielewski wrote:
> Matthew Hardin wrote:
> >>Tomasz Chmielewski wrote:
> >>
> >>(...)
> >>
> >[...]
> >>I digged a bit in the mailing list, and found that OpenLDAP with bdb
> >>backend needs a special startup script to recover from such situations.
> It seems that the binddn is listed on the database. Here is the relevant
> output from the slapcat command:
I do hope that binddn is not rootdn, otherwise it would be a rather
bad idea.
[...]
Pardon my ignorance, what is the problem using the rootdn as binddn?
Dmisc
Tomasz Chmielewski <[EMAIL PROTECTED]> writes:
> Matthew Hardin wrote:
>>> Tomasz Chmielewski wrote:
>>>
>>> (...)
>>>
>> [...]
>
> Although it sounds great, lots of posts on this group prove quite the
> contrary - there are problems with recovery with bdb backends, and for
> lots of people it ta
> I recently set up OpenLDAP as a proxy to an Active Directory server.
> Happily, this works just fine, and was quite easy to set up. When I
> attempted to enable pcache however, slapd started segfaulting on startup.
Your configuration is incomplete; of course, an incorrect configuration
shouldn'
Owen DeLong wrote:
This may not be the politically correct thing to say here, but, it is my
experience and YMMV.
BDB is very stable and reliable, once you get the right combination of
configuration figured out. There's lots of different things that need
to be set up to get BDB stable and many o
> So, will it recover, or will it not?
It will.
> I'm confused, I use 2.3.6, and it doesn't recover. After reading lots of
> posts in this thread, I would say db_recover is needed after an unclean
> shutdown.
>
> Did you mean a recent 2.3 version (2.3.24 or so)?
I believe at least 18 releases oc
--On Thursday, July 20, 2006 9:58 PM +0200 Tomasz Chmielewski
<[EMAIL PROTECTED]> wrote:
Matthew Hardin wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-openldap-
[EMAIL PROTECTED] On Behalf Of Daniel Maher
Sent: Thursday, July 20, 2006 7:55 AM
To: openldap
Subject: R
--On Thursday, July 20, 2006 9:49 PM +0200 Tomasz Chmielewski
<[EMAIL PROTECTED]> wrote:
FRLinux wrote:
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
It's hard to do so when you have multiple servers, and don't know which
one had a power outage...
If you don't mind me saying,
Hello all,
I recently set up OpenLDAP as a proxy to an Active Directory server. Happily,
this works just fine, and was quite easy to set up. When I attempted to enable
pcache however, slapd started segfaulting on startup.
Software versions:
RedHat EL3 (somewhat modified from stock)
Hello all (again),
Regarding the segfault (see previous email, or quote below); a small addition
to slapd.conf eliminates the condition that was causing the fault:
slapd.conf:
proxyAttrset0 proxyAddress
proxyTemplate (sn=) 0 3600
However, while it no longer crashes on load,
Matthew Hardin wrote:
Tomasz Chmielewski wrote:
(...)
[...]
I digged a bit in the mailing list, and found that OpenLDAP with bdb
backend needs a special startup script to recover from such situations.
Too bad it isn't mentioned, even short and briefly, in OpenLDAP Admin
Guide.
It's not men
Matthew Hardin wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-openldap-
[EMAIL PROTECTED] On Behalf Of Daniel Maher
Sent: Thursday, July 20, 2006 7:55 AM
To: openldap
Subject: RE: bdb backend - reliable or not?
Do you have any idea where might we locate this special star
FRLinux wrote:
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
It's hard to do so when you have multiple servers, and don't know which
one had a power outage...
If you don't mind me saying, i thought it was what notification
utilities were for (nagios springs to mind ...)
You're mi
Marc Tardif <[EMAIL PROTECTED]> writes:
> * Dieter Kluenter <[EMAIL PROTECTED]> [2006-07-20 17:46 +0200]:
>> Marc Tardif <[EMAIL PROTECTED]> writes:
>>
[...]
>> > It seems that the binddn is listed on the database. Here is the relevant
>> > output from the slapcat command:
>>
>> I do hope that b
Marc Tardif <[EMAIL PROTECTED]> writes:
> * Marc Tardif <[EMAIL PROTECTED]> [2006-07-20 10:53 -0400]:
>> I have installed OpenLDAP 2.2.26 from package on Ubuntu 6.06 LTS. The
>> postinst script prompts for a password to create an admin user. However,
>> when I try to run the ldapsearch command as
This may not be the politically correct thing to say here, but, it is my
experience and YMMV.
BDB is very stable and reliable, once you get the right combination of
configuration figured out. There's lots of different things that need
to be set up to get BDB stable and many of them are less than
* Marc Tardif <[EMAIL PROTECTED]> [2006-07-20 10:53 -0400]:
> I have installed OpenLDAP 2.2.26 from package on Ubuntu 6.06 LTS. The
> postinst script prompts for a password to create an admin user. However,
> when I try to run the ldapsearch command as the admin with that password, I
> get the foll
The question might seem like it's on the level of "Why do people make
spelling errors?", but it seems like many others who are running older
openldap servers migrating to newer servers also have had this
problem. Did the standards change?
I don't think the standards changed; OpenLDAP 2.0.21 was
Atom Powers wrote:
>
> Tomasz Chmielewski wrote:
> > Atom Powers wrote:
> >
> > (...)
> >
> >> Then put the db_recover command in your start-up script, and/or tune
> >> BDB so that it can survive a crash more easily.
> >
> > Is it OK if I put "db_recover" before each slapd startup? I guess it
> >
Atom Powers wrote:
>
> Tomasz Chmielewski wrote:
> > Unfortunately, the choice was a disaster - a couple of tests showed that
> > after powering off the server, OpenLDAP is not able to start anymore -
> > all I see in logs is a single message (loglevel 256):
> >
> > bdb_db_open: unclean shutdown d
> Tomasz Chmielewski wrote:
>
> (...)
>
[...]
>
> I digged a bit in the mailing list, and found that OpenLDAP with bdb
> backend needs a special startup script to recover from such situations.
>
> Too bad it isn't mentioned, even short and briefly, in OpenLDAP Admin
> Guide.
It's not mentioned
Aaron, thanks for your input.
Replication has been setup between these servers, but running
"ldapsearch -x -b 'o=HotCoco,c=US' '(objectclass=*)' " on both of the
servers return different results.
I thought slurpd would keep the data consistent, but apparently on the
Master server, the line: "o:
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
It's hard to do so when you have multiple servers, and don't know which
one had a power outage...
If you don't mind me saying, i thought it was what notification
utilities were for (nagios springs to mind ...)
Steph
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Did you ever press the reset button to simulate a power outage? :)
As a matter of fact, i did better than simulate, due to *human error*
it did happen twice and bdb does recover from it pretty well.
Steph
* Dieter Kluenter <[EMAIL PROTECTED]> [2006-07-20 17:46 +0200]:
> Marc Tardif <[EMAIL PROTECTED]> writes:
>
> > I have installed OpenLDAP 2.2.26 from package on Ubuntu 6.06 LTS. The
> > postinst script prompts for a password to create an admin user. However,
> > when I try to run the ldapsearch co
Tomasz Chmielewski wrote:
Atom Powers wrote:
(...)
Then put the db_recover command in your start-up script, and/or tune
BDB so that it can survive a crash more easily.
Is it OK if I put "db_recover" before each slapd startup? I guess it
should be avoided.
In that case, how can I detect tha
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-openldap-
> [EMAIL PROTECTED] On Behalf Of Tomasz Chmielewski
> Sent: Thursday, July 20, 2006 1:24 AM
> To: openldap-software@OpenLDAP.org
> Subject: bdb backend - reliable or not?
>
> Previously I was using OpenLDAP 2.1.x and 2.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-openldap-
> [EMAIL PROTECTED] On Behalf Of Daniel Maher
> Sent: Thursday, July 20, 2006 7:55 AM
> To: openldap
> Subject: RE: bdb backend - reliable or not?
>
> Do you have any idea where might we locate this special startup scri
FRLinux wrote:
On 7/20/06, Daniel Maher <[EMAIL PROTECTED]> wrote:
Do you have any idea where might we locate this special startup
script? :)
I think he actually meant : where to find the special utility to
recover from corrupted databases, so namely that would be db_recover.
And as mentionned
FRLinux wrote:
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Will an upgrade to 2.3.24 solve my problems with bdb, or shall I revert
back to ldbm?
We've been using 2.3.21 for a bit and recently upgraded to 2.3.24 and
all servers are really happy. Worth mentionning that from 2.1.x t
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Will an upgrade to 2.3.24 solve my problems with bdb, or shall I revert
back to ldbm?
We've been using 2.3.21 for a bit and recently upgraded to 2.3.24 and
all servers are really happy. Worth mentionning that from 2.1.x to
2.3.x, we've a
On 7/20/06, Daniel Maher <[EMAIL PROTECTED]> wrote:
Do you have any idea where might we locate this special startup script? :)
I think he actually meant : where to find the special utility to
recover from corrupted databases, so namely that would be db_recover.
And as mentionned in a previous p
Atom Powers wrote:
(...)
Then put the db_recover command in your start-up script, and/or tune BDB
so that it can survive a crash more easily.
Is it OK if I put "db_recover" before each slapd startup? I guess it
should be avoided.
In that case, how can I detect that the server crashed unexpe
Marc Tardif <[EMAIL PROTECTED]> writes:
> I have installed OpenLDAP 2.2.26 from package on Ubuntu 6.06 LTS. The
> postinst script prompts for a password to create an admin user. However,
> when I try to run the ldapsearch command as the admin with that password, I
> get the following error message
Tomasz Chmielewski wrote:
Unfortunately, the choice was a disaster - a couple of tests showed that
after powering off the server, OpenLDAP is not able to start anymore -
all I see in logs is a single message (loglevel 256):
bdb_db_open: unclean shutdown detected; attempting recovery.
And that
Chris Lundell wrote:
Dieter Kluenter wrote:
Tomasz Chmielewski <[EMAIL PROTECTED]> writes:
Previously I was using OpenLDAP 2.1.x and 2.2.x with ldbm backend.
I never had problems with it.
As I've read on the list that ldbm support will be dropped in the next
major version of OpenLDAP, and
matthew sporleder wrote:
That special startup script is only for 2.2. As your logs show,
openldap attempted to automatically recover. You can try running
db_recover manually, and see if that works.
It's hard to do so when you have multiple servers, and don't know which
one had a power outage
Daniel Maher wrote:
Do you have any idea where might we locate this special startup script? :)
Hmm, if you're talking about the documentation (OpenLDAP Admin Guide),
I'd mention the fact that one needs to run db_recover after an unclean
shutdown (power outage).
And an example init.d script
--On Thursday, July 20, 2006 10:23 AM +0200 Tomasz Chmielewski
<[EMAIL PROTECTED]> wrote:
Previously I was using OpenLDAP 2.1.x and 2.2.x with ldbm backend.
I never had problems with it.
As I've read on the list that ldbm support will be dropped in the next
major version of OpenLDAP, and b
Do you have any idea where might we locate this special startup script? :)
_
°v° Daniel Maher
/(_)\ Administrateur Système Unix
^ ^ Unix System Administrator
Sentio aliquos togatos contra me conspirare.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behal
Yes, I've just setup replication (Redhat7 -> FedoraCore5), and it
seems to work.
I've tested adding a new record into the Redhat7server and changes
were reflected on the FedoraCore5 server. Modifying a record was
replicated over also.
So replication from openldap-2.0.21 -> openldap-2.3.24 works,
Dieter Kluenter wrote:
Tomasz Chmielewski <[EMAIL PROTECTED]> writes:
Previously I was using OpenLDAP 2.1.x and 2.2.x with ldbm backend.
I never had problems with it.
As I've read on the list that ldbm support will be dropped in the next
major version of OpenLDAP, and bdb is the recommended
That special startup script is only for 2.2. As your logs show,
openldap attempted to automatically recover. You can try running
db_recover manually, and see if that works.
On 7/20/06, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Tomasz Chmielewski wrote:
(...)
> Performance is not an issue
I have installed OpenLDAP 2.2.26 from package on Ubuntu 6.06 LTS. The
postinst script prompts for a password to create an admin user. However,
when I try to run the ldapsearch command as the admin with that password, I
get the following error message:
$ ldapsearch -x -w password -D "cn=admin,dc=
Tomasz Chmielewski <[EMAIL PROTECTED]> writes:
> Previously I was using OpenLDAP 2.1.x and 2.2.x with ldbm backend.
>
> I never had problems with it.
>
> As I've read on the list that ldbm support will be dropped in the next
> major version of OpenLDAP, and bdb is the recommended backend, I
> deci
On Qua, 2006-07-19 at 14:30 -0400, Aaron Richton wrote:
> > My question is, shouldn't the proxy server figure out that the
> > connection is dead and retry opening a new connection? If so, is there
> > any configuration directive that i need to specify, either on the proxy
> > side or the backend s
Quoting Aaron Richton <[EMAIL PROTECTED]>:
When I start slapd with slapd -d acl, the server starts normally.
Evn if there are warning messages. The ending message is "slapd
starting".
Fantastic. Now keep that running as is (go to another window or
something) and run your ldapsearch (or whate
Tomasz Chmielewski wrote:
(...)
Performance is not an issue here, databases are relatively small.
What is important is the ability to survive unexpected system
crash/poweroff.
I digged a bit in the mailing list, and found that OpenLDAP with bdb
backend needs a special startup script to reco
Previously I was using OpenLDAP 2.1.x and 2.2.x with ldbm backend.
I never had problems with it.
As I've read on the list that ldbm support will be dropped in the next
major version of OpenLDAP, and bdb is the recommended backend, I decided
to deploy a couple of new OpenLDAP servers with bdb b
Hi,
I'm testing 2.3.24 back-ldap with proxycache on Linux-2.6.11-x86_64
installed in VMware-Server-1.0, with 512MB Ram, 1GB swap and 10GB disk
space. The host is a x86_64, 2GB RAM, same kernel version.
I just wonder how much memory pcache is allocating, as the kernel runs
out of memory and kills sl
57 matches
Mail list logo
