On Nov 14, 2007 2:35 AM, David Whyte <<a href="mailto:david.whyte@gmail.com">david.whyte@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Nov 11, 2007 4:06 PM, Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br>><br>> Constantly pinging the backend status page is "known" to cause<br>> mythbackend to crash. I'd bet that your proactive approach to handling
<br>> the crashes--monitoring with monit so you can restart after a crash--is<br>> what's causing the crashes.<br>><br><br><br>Heh, I wrote a Google Gadget that grabs the xml data from the backend<br>and parses it to show the current state of my tuners and stuff. I
<br>found that it would cause the backend to crash intermittently too. I<br>assumed it was a problem with the backend, but I had no idea it was a<br>known-issue per se.<br><br>Well done Steve on updating the wiki. Your note is what prompted me
<br>to search for this post and confirm it all.<br><br>Cheers,<br>Whytey<br>_______________________________________________</blockquote><div><br>Just to confirm on my end as well, I commented out the line in monit that checks the backend status and mythbackend has stopped crashing. After reading Whytey's note, I searched for any potential tickets and couldn't find one. So I created my first ticket. Yeah.
<br><br>It is somewhat comical to read one of my posts several several months ago on this. I couldn't figure out why the backend wouldn't crash when I started it in debug mode. I now realize that is because I turned monit off in debug mode in order to prevent it from starting two instances of the same program.
<br></div></div><br>