Um 02:29 Uhr am 16.04.05 schrieb Steve Langasek:
>> #txn_checkpoint 128 15 1
>> set_cachesize 0 2524288000
>> set_lk_max_objects 10
>> set_lk_max_locks10
>> #
>> set_lk_max_lockers 10
>> #
>> set_lg_regionmax1048576
>>
Hi Sven,
On Mon, Apr 11, 2005 at 11:56:23PM +0200, Sven Hartge wrote:
> After the last episode of "killall slapd; db4.2_recover; /etc/init.d/slapd
> start"
> my DB_CONFIG looks like this:
> #txn_checkpoint 128 15 1
> set_cachesize 0 2524288000
> set_lk_m
Um 23:56 Uhr am 11.04.05 schrieb Sven Hartge:
[Sorry for spamming this bug report, but I _really_ need to get this going
*fast*.]
> My last change is
>
> set_lk_max_lockers 10
>
> which was still default and seems to be to _real_ culprit, as per
> ITS#2030:
>
> http://www.openldap
Hi.
After the last episode of "killall slapd; db4.2_recover; /etc/init.d/slapd
start"
my DB_CONFIG looks like this:
#txn_checkpoint 128 15 1
set_cachesize 0 2524288000
set_lk_max_objects 10
set_lk_max_locks10
#
set_lk_max_lockers
Hi.
Could we please raise this bug to at least "important", because every day
at least one of my 8 replicas goes bottom up with the sched_yield() loop.
Right now I even consider this bug RC-worthy.
Grüße,
Sven.
--
Sven Hartge -- professioneller Unix-Geek und alltime Nerd
Meine Gedanken im Net
Um 09:24 Uhr am 11.04.05 schrieb Torsten Landschoff:
> On Wed, Apr 06, 2005 at 09:27:19PM +0200, Sven Hartge wrote:
>> Right now I am running with LD_ASSUME_KERNEL=2.4.1 as suggested in
>> $the_other_bug, so far no problems, but as this sched_yield()-problem
>> needs some time to show, I don't
Hi Sven,
On Wed, Apr 06, 2005 at 09:27:19PM +0200, Sven Hartge wrote:
> Right now I am running with LD_ASSUME_KERNEL=2.4.1 as suggested in
> $the_other_bug, so far no problems, but as this sched_yield()-problem
> needs some time to show, I don't know, if this really is the solution or
> if I
Um 21:01 Uhr am 06.04.05 schrieb Torsten Landschoff:
> Hmm, very interesting. I wonder why it works at Stanford and apparently
> nowhere else. I was notified today that putting a DB_CONFIG file into
> the directory has no effect after the initial database was created so
> I'd like to ask if you d
Um 21:01 Uhr am 06.04.05 schrieb Torsten Landschoff:
> On Wed, Apr 06, 2005 at 03:32:11PM +0200, Sven Hartge wrote:
>>> I thought so as well. Did you use a DB_CONFIG file suited for your
>>> setup?
>> Yes, of course.
>> #txn_checkpoint 128 15 1
>> set_cachesize 0
Hi Sven,
On Wed, Apr 06, 2005 at 03:32:11PM +0200, Sven Hartge wrote:
> >I thought so as well. Did you use a DB_CONFIG file suited for your
> >setup?
>
> Yes, of course.
> #txn_checkpoint 128 15 1
> set_cachesize 0 2524288000
> set_lk_max_objects
Torsten Landschoff wrote:
I am deeply sorry, but I have to report 2.2.23 hitting the same problem
for me.
How can this be? I thought all those bugs were elimated in 2.2 using db4.2?
I thought so as well. Did you use a DB_CONFIG file suited for your
setup?
Yes, of course.
I am thinking along 8MB
Hi Sven,
On Tue, Apr 05, 2005 at 01:53:26PM +0200, Sven Hartge wrote:
> >Known problem. Please try upgrading to 2.2.23. 2.1.30 will not ship
> >with sarge because of these and other problems. Running db4.2_recover
> >in the database directory may temporarily fix those problems but they
> >are go
On Mon, Apr 04, 2005 at 05:25:35PM +0200, Wolfgang Kohnen wrote:
Sometimes all openldap programs (slapd, slapcat, slapindex) which
want to access my bdb_backend the program eats up all cpu cycles
and doesn't react anymore except of SIGNAL 2 and 4 (not 15; didn't
check any other).
Known problem.
Hi Wolfgang,
On Mon, Apr 04, 2005 at 05:25:35PM +0200, Wolfgang Kohnen wrote:
> Sometimes all openldap programs (slapd, slapcat, slapindex) which
> want to access my bdb_backend the program eats up all cpu cycles
> and doesn't react anymore except of SIGNAL 2 and 4 (not 15; didn't
> check any
Package: slapd
Version: 2.1.30-3
Severity: important
Sometimes all openldap programs (slapd, slapcat, slapindex) which
want to access my bdb_backend the program eats up all cpu cycles
and doesn't react anymore except of SIGNAL 2 and 4 (not 15; didn't
check any other).
Increasing the loglevel d
15 matches
Mail list logo
