Hi,
On 09/13/2016 07:37 PM, Rakesh Rajasekharan wrote:
Hi All,
Have finally made some progress with this.. after changing the
checkpoint interval to 180, my hangs have gone down now..
However, I faced a similar hang yesterday... users were not able to
login.. , though this time the ns-slapd
Hi Thierry,
I was getting the hang issue while running ipa-client-install
simultaneously on few clients..
However, today, I am not able to replicate that.
I could not get a gdb . But i will try getting that the next time I face
this issue.
The CPU does not stay high.. it just momentarily
Hi Rakesh,
Were you able to get a pstack or full stack with gdb
(http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes) when
the server hangs ?
If it happens with 500 threads as well as with 30, using 30 threads is a
better choice to debug this issue.
I will try to reproduce
starce on the slapd process actually had this in the output..
FUTEX_WAIT_PRIVATE
and checking for the number of threads slapd had.. there were 5015 threads
ps -efL|grep slapd|wc -l
5015
strace on most of the threads gave this output
strace -p 67411
Process 67411 attached
futex(0x7f3f0226b41c,
I have again got the issue of IPA hanging.. The issue came up when i tried
to run ipa-client-isntall on 142 clients simultaneously
None of the IPA commands are responding, and I see this error
ipa user-find p-testipa
ipa: ERROR: Insufficient access: SASL(-1): generic failure: GSSAPI Error:
On 08/29/2016 10:53 AM, Rakesh Rajasekharan wrote:
Hi Thierry,
My machine has 30GB RAM ..and 389-ds version is 1.3.4
ldapsearch shows the values for nsslapd-cachememsize updated to 200MB.
ldapsearch -LLL -o ldif-wrap=no -D "cn=directory manager" -w
'mypassword' -b 'cn=userRoot,cn=ldbm
Hi Thierry,
My machine has 30GB RAM ..and 389-ds version is 1.3.4
ldapsearch shows the values for nsslapd-cachememsize updated to 200MB.
ldapsearch -LLL -o ldif-wrap=no -D "cn=directory manager" -w 'mypassword'
-b 'cn=userRoot,cn=ldbm database,cn=plugins,cn=config'|grep
nsslapd-cachememsize
Hi Rakesh,
Those tuning may depend on the memory available on your machine.
nsslapd-cachememsize allows the entry cache to consume up to 200Mb but
its memory footprint is known to go above.
200Mb both looks pretty good to me. How large is your machine ? What is
your version of 389-ds ?
Those
Hi Thierry,
Coz of the issues we had to revert back to earlier running openldap in
production.
I have now done a few TCP related changes in sysctl.conf and have also
increased the nsslapd-dbcachesize and nsslapd-cachememsize to 200MB
I will again start migrating hosts back to IPA and see if I
All of the troubleshooting seems fine.
However, Running libconv.pl gives me this output
- Recommendations -
1. You have unindexed components, this can be caused from a search on an
unindexed attribute, or your returned results exceeded the
allidsthreshold. Unindexed components are
On 23.8.2016 18:44, Rakesh Rajasekharan wrote:
> I think thers something seriously wrong with my system
>
> not able to run any IPA commands
>
> klist
> Ticket cache: KEYRING:persistent:0:0
> Default principal: ad...@xyz.com
>
> Valid starting Expires Service principal
>
I think thers something seriously wrong with my system
not able to run any IPA commands
klist
Ticket cache: KEYRING:persistent:0:0
Default principal: ad...@xyz.com
Valid starting Expires Service principal
2016-08-23T16:26:36 2016-08-24T16:26:22 krbtgt/xyz@xyz.com
i changed the loggin level to 4 . Modifying nsslapd-accesslog-level
But, the hang is still there. though I dont see the sigfault now
On Tue, Aug 23, 2016 at 9:02 PM, Rakesh Rajasekharan <
rakesh.rajasekha...@gmail.com> wrote:
> My disk was getting filled too fast
>
> logs under
My disk was getting filled too fast
logs under /var/log/dirsrv was coming around 5 gb quickly filling up
Is there a way to make the logging less verbose
On Tue, Aug 23, 2016 at 6:41 PM, Petr Spacek wrote:
> On 23.8.2016 15:07, Rakesh Rajasekharan wrote:
> > I was able to
On 23.8.2016 15:07, Rakesh Rajasekharan wrote:
> I was able to fix that may be temporarily... when i checked the network..
> there was another process that was running and consuming a lot of network (
> i have no idea who did that. I need to seriously start restricting people
> access to this
On 19.8.2016 19:32, Rakesh Rajasekharan wrote:
> I am running my set up on AWS cloud, and entropy is low at around 180 .
>
> I plan to increase it bu installing haveged . But, would low entropy by any
> chance cause this issue of intermittent hang .
> Also, the hang is mostly observed when
I am running my set up on AWS cloud, and entropy is low at around 180 .
I plan to increase it bu installing haveged . But, would low entropy by any
chance cause this issue of intermittent hang .
Also, the hang is mostly observed when registering around 20 clients
together
On Fri, Aug 19, 2016 at
yes there seems to be something thats worrying.. I have faced this today as
well.
There are few hosts around 280 odd left and when i try adding them to IPA ,
the slowness begins..
all the ipa commands like ipa user-find.. etc becomes very slow in
responding.
the SYNC_RECV are not many though
On 18.8.2016 17:23, Rakesh Rajasekharan wrote:
> Hi
>
> I am migrating to freeipa from openldap and have around 4000 clients
>
> I had openned a another thread on that, but chose to start a new one here
> as its a separate issue
>
> I was able to change the nssslapd-maxdescriptors adding an
19 matches
Mail list logo