On 04/07/2016 10:45 AM, ghiureai wrote:
Hello Gurus,
I was searching the web for some scripts to monitor DS performance ,
and found the Open Ldap: ldap-ping.pl script,
I wonder if there is a version for 389-DS or if are other similar
performance measure scripts available for 389-ds?
Looks
On 03/08/2016 03:36 PM, liblfds admin wrote:
On 08/03/16 22:35, Howard Chu wrote:
Even though it's a VM, numactl -H may still show something relevant.
I'll try it next time I have one running.
BerkeleyDB did adaptive locking, using a spinlock before falling back to
a heavier weight system
On 04/25/2016 01:24 PM, ghiureai wrote:
Hello List,
I am running some search performance tests , basic ldapsearch
augument "cn" , on local ldap host with rsearch, and
seeing readwaiters: values chainng , here is a sample from dbmon
This is not from dbmon. This is from cn=monitor:
On 05/17/2016 08:01 AM, Alberto Viana wrote:
Noriko,
Just to let you know, after I replicated/created the exactly same OU
structure on both side, the replication seems to works fine. I'm still
not sure that is the expected behavior:
Yes, it is. Winsync does _not_ sync the OU structure -
On 05/17/2016 02:04 PM, Robert Viduya wrote:
We run a cluster of directory servers (4 masters, 2 hubs, 14 slaves)
behind a set of F5 Bigip load balancers. Our Bigip admins recently
decided to switch the boxes to "one-armed" mode and that services
would have to use X-Forwarded-For headers or
AM, Rich Megginson <rmegg...@redhat.com
<mailto:rmegg...@redhat.com>> wrote:
On 05/17/2016 02:04 PM, Robert Viduya wrote:
We run a cluster of directory servers (4 masters, 2 hubs, 14 slaves)
behind a set of F5 Bigip load balancers. Our Bigip admins recently
decided to switch the b
On 02/23/2017 01:11 AM, William Brown wrote:
On Wed, 2017-02-22 at 22:20 -0800, Gordon Messmer wrote:
On 02/22/2017 09:25 PM, William Brown wrote:
Default indexes only apply to new databases (It's a template iirc). You
need to edit the index on the cn=userRoot,cn=ldbm
On 11/15/2016 12:58 PM, Marc Sauton wrote:
What is the test filter like?
Can we see a sanitized sample of the access log with the SRCH and RESULT?
If using SSL, review the output of
cat /proc/sys/kernel/random/entropy_avail
Do we have replication? (and large attribute values?)
You may want to
On 11/15/2016 05:51 PM, Gordon Messmer wrote:
On 11/15/2016 12:08 PM, Rich Megginson wrote:
It is also useful to get a few stacktraces which will give us
detailed information about what the server is doing. For example, if
you can "catch" the server while it is misbehavin
On 03/31/2017 07:58 AM, Mark Reynolds wrote:
On 03/30/2017 09:05 PM, William Brown wrote:
On Thu, 2017-03-16 at 15:16 -0400, Mark Reynolds wrote:
Just curious if anyone is building 389 on HPUX? There is very old code
in our server that is specific to HPUX that we'd like to remove. Most
of
I keep getting this error:
Traceback (most recent call last):
File "/home/rmeggins/scripts/repltest.py", line 53, in
m1 = tools.DirSrvTools.createInstance(createargs)
File "/home/rmeggins/ds/ds.git/src/lib389/lib389/tools.py", line 627,
in createInstance
cfgdn = lib389.CFGSUFFIX
On 08/15/2018 10:13 AM, David Boreham wrote:
in strace.log:
[pid 8088] 12:55:39.739539 poll([{fd=435, events=POLLOUT}], 1, 180
[pid 8058] 12:55:39.739573 <... write resumed> ) = 1 <0.87>
[pid 8088] 12:55:39.739723 <... poll resumed> ) = 1 ([{fd=435,
revents=POLLOUT}]) <0.000168>
On 08/15/2018 10:56 AM, David Boreham wrote:
On 8/15/2018 10:36 AM, Rich Megginson wrote:
Updating the csn generator and the uuid generator will cause a lot of
churn in dse.ldif. There are other housekeeping tasks which will
write dse.ldif
But if those things were being done so
801 - 813 of 813 matches
Mail list logo
