| LinHES Forums http://forum.linhes.org/ |
|
| Frontend keeps lossing connection to the backend http://forum.linhes.org/viewtopic.php?f=17&t=13995 |
Page 1 of 1 |
| Author: | Type82 [ Thu Feb 01, 2007 8:04 pm ] |
| Post subject: | Frontend keeps lossing connection to the backend |
On my remote frontend as well as the frontend running on my MBE, I am constantly getting a message saying the frontend has lost its connection to the backend. I would say this happens probably less around 10 times a day. The exact message I get is: The connection to the master backend server has gone away for some reason.. Is it running? Playback works fine, it's never disconnected during playback of a recorded show at all. If you stay at the recording screen, it will eventually happen. I've noticed that it happens at the same time on both systems. The mythbackend process never actually dies. I've setup a script to monitor the existing of the mythbackend process and to log to a file in /tmp if it has to restart it, and thats yet to happen. I'm not able to find anything the logs other than: from dmesg Code: ivtv0: Cause: the application is not reading fast enough. ivtv0: All encoder MPEG stream buffers are full. Dropping data. ivtv0: Cause: the application is not reading fast enough. ivtv1: All encoder MPEG stream buffers are full. Dropping data. ivtv1: Cause: the application is not reading fast enough. in /var/log/mythtv/mythbackend.log Code: 2007-02-01 20:30:18.493 scheduler: Started recording: The War at Home "Zero Tolerance": channel 1004 on cardid 2, sourceid 1 2007-02-01 20:30:18.509 MPEGRec(/dev/video1) Error: Error getting codec params using old IVTV ioctl eno: Bad address (14) 2007-02-01 20:30:19.511 Reschedule requested for id 0. 2007-02-01 20:30:25.104 TFW, Error: Write() -- IOBOUND begin cnt(2048) free(1571) 2007-02-01 20:30:25.434 TFW, Error: Write() -- IOBOUND end Code: 2007-02-01 21:00:48.290 MythSocket(a8c7ffe0:-1): writeStringList: Error, socket went unconnected.
2007-02-01 21:00:48.329 MythSocket(a8912d40:-1): writeStringList: Error, socket went unconnected. 2007-02-01 20:00:17.671 TVRec(1): Changing from None to RecordingOnly 2007-02-01 20:00:17.793 TVRec(1): HW Tuner: 1->1 2007-02-01 20:00:18.177 MPEGRec(/dev/video0) Error: Error getting codec params using old IVTV ioctl eno: Bad address (14) Does anybody have any suggestions? This is driving me mad. I can't find anything worth while to lead in the right direction. |
|
| Author: | miker [ Fri Feb 02, 2007 7:59 am ] |
| Post subject: | |
Are you running R5E50? I had the same problem with my setup. I've seen a few possible fixes but not a clear and simple fix so I installed R5D1 and have no troubles at all. R5E50 looks like it was released a bit too early. A quick look look around and you will see quite a few people are having troubles with it as well. mike ________ HEALTHY RELATIONSHIP ADVICE FORUMS |
|
| Author: | jmacmythtv [ Sun Feb 25, 2007 9:43 am ] |
| Post subject: | |
I was having this problem in both R5D1 and R5E50. Found this regarding the IVTV dropping data / not reading fast enough error (Scroll to the end) http://www.gossamer-threads.com/lists/i ... ata;#33874 I created a file called "options" in /etc/modprobe.d/ that has the following line in it: options ivtv mpg_buffers=16 I restarted and haven't seen the error since. HTH |
|
| Author: | joltosa [ Mon Mar 03, 2008 12:42 pm ] |
| Post subject: | |
Hi. I'm using R5F27, and I was having a similar problem: very infrequently the backend server would go away. I tried the above but that froze my system upon boot. I found this link http://www.gossamer-threads.com/lists/ivtv/users/37562 which suggests using this instead options ivtv enc_mpg_buffers=16 Now at least my box boots up normally. |
|
| Author: | falinskip [ Wed Apr 16, 2008 7:13 pm ] |
| Post subject: | Check the network connectivity |
Hi There, One of my friends had a similar problem with his Frontend / Backend connection. We ended up doing a continuous ping to the backend from the frontend (you can actually do it either way). We found that he was dropping about 15 - 20 % of his packets. It ended up being a network card was not going "Full Duplex" on Network Switch but the NIC thought it was "Full Duplex". Just a thought |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|