[mythtv-users] No connection to the backend (~every two weeks) -- Need help

[Michael T. Dean]

On 08/18/2009 11:43 AM, Allen Edwards wrote:
> I need help please.  My wife is being very understanding but I am not
> sure how long that will last.
>
> I have googled and searched the archives for the past 4 months.  I
> looked on the Ubuntu forum.
>
> I have rewritten my last post providing new information and removing
> spurious stuff.
>
> I went through my logs looking for no connection to the backend
> looking for a pattern.  The only pattern I see is that this started in
> March.  It looks like I did an upgrade mid February so perhaps the
> upgrade caused this.
> There is also upgrade log information from June.  I attached dpkg.log
> files to this email.
>   
...
> dad at myth_desktop:~$ grep " No connection to the backend"
> /var/log/mythtv/mythfrontend.log.2
> 2009-03-02 09:25:23.302 Event socket closed. No connection to the backend.
> 2009-03-14 19:00:03.139 Event socket closed. No connection to the backend.
> 2009-05-08 03:10:02.580 Event socket closed. No connection to the backend.
> dad at myth_desktop:~$ grep " No connection to the backend"
> /var/log/mythtv/mythfrontend.log.1
> 2009-06-13 07:35:18.058 Event socket closed. No connection to the backend.
> 2009-06-13 11:16:37.476 Event socket closed. No connection to the backend.
> 2009-06-13 11:50:52.904 Event socket closed. No connection to the backend.
> 2009-06-13 15:56:17.528 Event socket closed. No connection to the backend.
> dad at myth_desktop:~$ grep " No connection to the backend"
> /var/log/mythtv/mythfrontend.log
> 2009-07-16 10:20:02.695 Event socket closed. No connection to the backend.
> 2009-08-09 21:28:59.723 Event socket closed. No connection to the backend.
> 2009-08-17 05:30:18.856 Event socket closed. No connection to the backend.
>   
...
> I am running mythbuntu 8.04.  Here is the version information for mythbackend
>
> MythTV Version   : 19878
> MythTV Branch    : branches/release-0-21-fixes

There's a known issue with the MythTV socket code when used on new 
distros (or at least, likely, some new library version) that causes 
symptoms such as you're seeing.  Daniel K is currently experiencing the 
issue on his recently-upgraded system, so he's working on it.

If that issue is what's causing the problems you're seeing, there's 
probably not a lot you can do until he gets it figured out and working 
(other than, maybe, going back to old distro versions--which may make 
upgrading to current 0.21-fixes Myth without pulling in the new libs 
causing issues a challenge).  Or, really, I should say that there's no 
known resolution for the problem at this time.  If you can figure 
something out you'll make a /lot/ of users very happy.

Note, also, that the assumption the problem exists only on newer 
distros/with newer lib versions is based solely on anecdotal evidence.  
So, even if you did go back to an old/not-upgraded distro and, maybe, 
compiled 0.21-fixes (and any dependencies you need to add whose packages 
would pull in other updated libs) from source, you may still encounter 
the issues.  (And, if you did, please let us know--as it would be 
another interesting data point.  And, especially if someone can figure 
out exactly which library/version is causing issues, knowing would be 
very helpful in fixing the issues.)

Mike