On Wed, 2016-11-16 at 16:00 -0800, Gordon Messmer wrote:
> On 11/16/2016 01:23 PM, William Brown wrote:
> > What's your ioblocktimeout set to?
>
> nsslapd-ioblocktimeout: 180
Hmm, that's default, but it's quite high, you could lower this if you
wanted. See:
On 11/16/2016 01:23 PM, William Brown wrote:
What's your ioblocktimeout set to?
nsslapd-ioblocktimeout: 180
How many connections are idle on the server?
How would I check?
Are you seeing OOM behaviour or memory not being released to the OS?
No, the systems use very little memory:
On Wed, 2016-11-16 at 10:24 -0800, Gordon Messmer wrote:
> On 11/16/2016 09:21 AM, Rich Megginson wrote:
> > I suggest you file a ticket at https://fedorahosted.org/389/newticket
> > and attach this and the other information for tracking. This doesn't
> > seem like an issue that will be easily
Am 11/16/2016 um 7:24 PM schrieb Gordon Messmer:
On 11/16/2016 09:21 AM, Rich Megginson wrote:
I suggest you file a ticket at https://fedorahosted.org/389/newticket
and attach this and the other information for tracking. This doesn't
seem like an issue that will be easily resolved . . .
On 11/16/2016 09:21 AM, Rich Megginson wrote:
I suggest you file a ticket at https://fedorahosted.org/389/newticket
and attach this and the other information for tracking. This doesn't
seem like an issue that will be easily resolved . . .
OK. Is there any other data I can gather right
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 misbehaving, and get
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 misbehaving, and get stacktraces every
second for 10 seconds.
On 11/15/2016 05:16 PM, Noriko Hosoi wrote:
rpm -q 389-ds-base?
# rpm -q 389-ds-base
389-ds-base-1.3.4.0-33.el7_2.x86_64
I wonder you are running the latest version?
https://git.centos.org/summary/rpms!!389-ds-base
2016-11-03 *imports/c7/389-ds-base-1.3.5.10-11.el7
rpm -q 389-ds-base?
I wonder you are running the latest version?
https://git.centos.org/summary/rpms!!389-ds-base
2016-11-03 *imports/c7/389-ds-base-1.3.5.10-11.el7
On 11/15/2016 11:58 AM, Marc Sauton wrote:
What is the test filter like?
my $LDAP_BASE = 'dc=dept,dc=uni,dc=edu';
my $LDAP_ATTRS = [qw/cn/];
my $LDAP_FILTER= '(cn=sysadm)';
...
my $ldap =
Net::LDAP->new( $LDAP_SERVER, timeout => $TIMEOUT, onerror =>
'die' )
or
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
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 run the "dbmon.sh" script to monitor cache
12 matches
Mail list logo
