<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
In regards to the hangs in the Directory Server that were observed,
it seems related thread 15 that is polling waiting for something to
come through the pipe which never happens. The default poll timeout
is 1800000(or 30 minutes!). Reducing this timeout should resolve
the "hang". <br>
<br>
Example:<br>
<br>
# ldapmodify -p PORT -h HOST -D "cn=directory manager" -w PASSWORD<br>
dn: cn=config<br>
changetype: modify<br>
replace: nsslapd-ioblocktimeout<br>
nsslapd-ioblocktimeout: 10000<br>
<br>
<press enter twice, then control-D><br>
<br>
This should be done for all the Directory Servers in your deployment.<br>
<br>
Regards,<br>
Mark<br>
<br>
<div class="moz-cite-prefix">On 03/26/2015 06:18 PM, David Kreuter
wrote:<br>
</div>
<blockquote
cite="mid:e660486f-3ab2-4f4a-99c7-05885b2fe4ed@zimbra.bytesource.net"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: arial,helvetica,sans-serif; font-size:
10pt; color: #000000">We have been using FreeIPA since two years
and were more than happy. But since two weeks we are facing
unexpected crashed and can not really debug the strange
behaviours. The crashes are definitely not caused by connecting
a new<span style="font-size: 10pt;"> system or changing the LDAP
schema heavily. Following IPA is used:</span>
<div>
<div><br>
</div>
<div>
<p class="p1"><span class="s1">Name : </span><span
class="s2">ipa-server</span></p>
<p class="p1"><span class="s1">Arch : x86_64</span></p>
<p class="p1"><span class="s1">Version : 3.3.3</span></p>
<p class="p1"><span class="s1">Release :
28.0.1.el7.centos.3</span></p>
<p class="p1"><span class="s1">Size : 4.1 M</span></p>
<p class="p1"><span class="s1"><br>
</span></p>
<p class="p1"><span class="s1">I have followed the
troubleshooting
guide <a class="moz-txt-link-freetext" href="http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#Troubleshooting">http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#Troubleshooting</a>
and activated logging and activated the core dumping.
Unfortunately, I cannot provide you any core dump,
because it is not created after the ipa servers crashes.
I'm sure the dirsrv is causing the problem, because when
i restart the 389, then ipa works fine for a while.
Currently I have activated the replication log level
8192. The error log shows no suspicious error or any
fatal error. Following 389* versions are used:</span></p>
<p class="p1"><span class="s1"><br>
</span></p>
<p class="p1"><span class="s1">Installed Packages</span></p>
<p class="p1"><span class="s1">389-ds-base.x86_64
1.3.3.1-15.el7_1
@/389-ds-base-1.3.3.1-15.el7_1.x86_64 </span></p>
<p class="p1"><span class="s1">389-ds-base-debuginfo.x86_64
1.3.1.6-26.el7_0
@base-debuginfo
</span></p>
<p class="p1"><span class="s1">
</span></p>
<p class="p1"><span class="s1">389-ds-base-libs.x86_64
1.3.3.1-15.el7_1</span></p>
<p class="p1"><span class="s1"><br>
</span></p>
<p class="p1"><span class="s1">Can you please provide some
hint how I can debug this problem in more detail. Btw,
the ipa infrastructure consist of one master and one
replica. The server was also crashing, when the replica
server was turned off. Do you thing an upgrade would
solve the problem as the last resort?</span></p>
<p class="p1"><span class="s1"><br>
</span></p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>