Hi,<div><br></div><div>Thanks for the quick response<br><br><div class="gmail_quote">On Thu, Jan 27, 2011 at 10:19, Rich Megginson <span dir="ltr"><<a href="mailto:rmeggins@redhat.com">rmeggins@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 01/27/2011 07:47 AM, Dan Scott wrote:
<blockquote type="cite">Hi,
<div><br>
</div>
<div>I have a FreeIPA server running on Fedora 14</div>
<div><br>
</div>
<div>
<div>[root@ohm ~]# rpm -qa|grep ipa-server</div>
<div>ipa-server-selinux-1.2.2-5.fc14.x86_64</div>
<div>ipa-server-1.2.2-5.fc14.x86_64</div>
</div>
<div><br>
</div>
<div>For the past few weeks, the dirsrv service has been
'crashing'. Randomly, as far as I can tell. - the service
appears to remain running, but fails to serve any LDAP requests.</div>
<div><br>
</div>
<div>/etc/init.d/dirsrv status</div>
<div><br>
</div>
<div>claims that the service is still running, but I get these
errors in the 'access' log file:</div>
<div><br>
</div>
<div>
<div>[27/Jan/2011:03:30:01 -0500] conn=9 op=11582 RESULT err=0
tag=101 nentries=0 etime=0</div>
<div>[27/Jan/2011:03:35:11 -0500] conn=897 fd=86 slot=86
connection from 192.168.1.202 to 192.168.100.30</div>
<div>[27/Jan/2011:03:35:11 -0500] conn=897 op=-1 fd=86 closed -
T2</div>
</div>
</blockquote></div>
This looks like <a href="https://bugzilla.redhat.com/show_bug.cgi?id=668548" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=668548</a>
or <a href="https://bugzilla.redhat.com/show_bug.cgi?id=668619" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=668619</a></div></blockquote><div><br></div><div>Yes, it could well be this. Thanks.</div><div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>There is nothing relevant in the 'errors' log file:</div>
<div><br>
</div>
<div>
<div>[27/Jan/2011:00:00:00 -0500] NSMMReplicationPlugin -
agmt="cn=meTocurie.example.com636" (curie:636): Incremental
protocol: event update_window_opened should not occur in state
wait_for_changes</div>
<div>[27/Jan/2011:09:38:32 -0500] - slapd shutting down -
signaling operation threads</div>
</div>
<div><br>
</div>
<div>The entry at 09:38 is me restarting the service. 'curie' is a
replica server which also occasionally crashes, but not at the
same time as ohm.</div>
<div><br>
</div>
<div>I have to do:</div>
<div><br>
</div>
<div>/etc/init.d/dirsrv status</div>
<div><br>
</div>
<div>to get things working again.</div>
</blockquote></div>
status? All status does is a kill -0 which just tests to see if the
process is running. Are you absolutely positive that status makes
things work again?</div></blockquote><div><br></div><div>Very sorry about this. A copy-and-paste error, I meant:</div><div><br></div><div>/etc/init.d/dirsrv restart</div><div> </div><div>Sorry.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>Does anyone know how I can figure out what the problem is? I
also have 2 Fedora 13 IPA FreeIPA servers which *don't* exhibit
this problem.</div>
</blockquote></div>
The problem is specific to F14? What version of 389-ds-base are you
using on F13?<br></div></blockquote><div><br></div><div>The Fedora 13 servers are using:</div><div><br></div><div><div>[djscott@fileserver2 ~]$ rpm -qa|grep 389</div><div>389-ds-base-1.2.7.5-1.fc13.i686</div></div><div>
<br></div><div>The Fedora 14 servers are using:</div><div><br></div><div><div>[djscott@ohm ~]# rpm -qa|grep 389</div><div>389-ds-base-1.2.7.5-1.fc14.x86_64</div></div><div><br></div><div>Thanks,</div><div><br></div><div>
Dan</div>
</div><br></div>