[mythtv] [mythtv-commits] Ticket #4174: Pinging backend port causes occasional crash

Michael T. Dean mtdean at thirdcontact.com
Wed Nov 14 23:42:33 UTC 2007


On 11/14/2007 11:01 AM, MythTV wrote:
> #4174: Pinging backend port causes occasional crash
>
>  Checking backend status on port 6544 causes the backend to crash 1-2 times
>  a day.   This has been reported with monit, mythgrowl, and user written
>  scripts that grab xml data.

Steve,

If you're "associated" with MythGrowl, you may be interested in the
contrib/misc_status_info/myth_recent_recordings.pl (and/or
myth_upcoming_recordings.pl in the same dir).  (If you need info about
recordings in progress only, let me know and I'll update
myth_recent_recordings.pl to include an argument for that.)

Also, for checking status with monit, you may be able to use something
like the attached "myth_ping.pl".  Currently, just creating a new MythTV
object connects to the master backend, so it tells you if the master
backend is available.  I haven't thought through whether you can get
slave backend status using the Perl bindings--myth_ping.pl was just
something I threw together and decided wasn't useful to me, so it was
just sitting on my filesystem (i.e. I didn't do it for this).

Even if the status page is made more stable when doing frequent polling,
these approaches may be more appropriate for what you're trying to do.

Also, if one of you from the thread could get a backtrace on a debug
build of Myth, that would make things a lot easier for the dev who tries
to figure out the issue.  (And, direct links to the actual replies that
contain the backtraces would have made it easier to find them ;)

non-debug backtraces are at:

http://www.gossamer-threads.com/lists/mythtv/users/296988#296988
http://www.gossamer-threads.com/lists/mythtv/users/298138#298138

Mike


More information about the mythtv-dev mailing list