<br><div class="gmail_quote">On Nov 10, 2007 5:07 PM, Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 11/09/2007 11:18 AM, Steve Skarda wrote:<br>> Mythbackend dies roughly 1-2 times a day. It did this on stable<br>> version and continues to do it on SVN trunk. I am posting the last<br>> items in the log on the last several crashes (on latest trunk from
<br>> mythbuntu weekly builds). It always ends with reschedule requested.<br><br></div>Are you sure it's the reschedule that crashes it? Reschedules happen<br>quite often, so it's quite possible that was the last thing written to
<br>the log, then later, mythbackend crashed.<br><br>Have you seen it crash immediately after logging the reschedule<br>requested message?<br><br>Mike<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">
</a><br></blockquote></div>Thank you for replying!<br><br>Monit runs every 60 seconds. If I compare the timestamp when Monit first saw that mythbackend was gone, to the timestamp in the mythbackend log, the last thing in the log before restart is the reschedule request and it is typically 20-30 seconds before monit sees that mythbackend is gone.
<br><br>You have caused me to wonder about something else though. Monit doesn't say that process doesn't exist which is what happens if I kill mythbackend. Rather it says that mythbackend failed HTTP test. <br>
<br>This is what I see in monit log:<br><br>[EST Nov 10 09:02:14] error : HTTP: error receiving data -- Resource temporarily unavailable<br>[EST Nov 10 09:02:14] error : 'mythbackend' failed protocol test [HTTP] at INET[localhost:6544] via TCP
<br>[EST Nov 10 09:02:15] info : 'mythbackend' trying to restart<br>[EST Nov 10 09:02:15] info : 'mythbackend' stop: /bin/sh<br>[EST Nov 10 09:02:16] info : 'mythbackend' start: /bin/sh
<br>[EST Nov 10 09:02:47] info : 'mythbackend' connection passed to INET[localhost:6544] via TCP<br><br>Maybe I should try to modify my monit monitoring configuration?<br><br>