[mythtv-commits] Ticket #7078: socket errors cause back-end to become unresponsive (trunk 21894)

[MythTV]

#7078: socket errors cause back-end to become unresponsive (trunk 21894)
------------------------------+---------------------------------------------
 Reporter:  databubble        |        Owner:  danielk   
     Type:  defect            |       Status:  infoneeded
 Priority:  major             |    Milestone:  0.22      
Component:  MythTV - General  |      Version:  head      
 Severity:  medium            |   Resolution:            
  Mlocked:  0                 |  
------------------------------+---------------------------------------------

Comment(by davideshay at gmail.com):

 danielk, perhaps posted under wrong ticket.  Symptom I am getting timeouts
 on the frontend like this:

 2009-09-21 07:03:40.446 MythSocket(25aae80:55): readStringList: Error,
 timed out after 30000 ms.
 2009-09-21 07:03:40.447 Preview Error: Remote Preview failed due to
 communications error.

 Not always remote preview.  Right now I always get the error when entering
 watch recordings, and nearly always get a pause when exiting a show.

 At some point, the front end gets confused and thinks shows are missing in
 Watch Recordings and I have to at least exit that screen and go back in.

 Thought based on the email in mythtv-users to post on this ticket, maybe
 not.  I see that since my backend wasn't completely unresponsive that a
 backtrace did no good. Do you want -v socket logs on front and back
 simultaneously or what else would help to track this down?

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7078#comment:11>
MythTV <http://www.mythtv.org/>
MythTV