LinHES Forums http://forum.linhes.org/ |
|
Front end playing and then nothing- How come? http://forum.linhes.org/viewtopic.php?f=6&t=8467 |
Page 1 of 1 |
Author: | Big boy stan [ Sun Feb 12, 2006 5:40 pm ] |
Post subject: | Front end playing and then nothing- How come? |
I have a rock solid FE/BE system. I recently tried my first take at a remote FE using an old Gateway Solo5300 notebook I had laying around. Things seemed to work pretty good and I actually went ahead and put it in. The problem that I have with the system is when watching recorded programs, the front end will just stop playing and return to the list of available recordings. This seems to happen at random times in a playback (even the same one recording) but varies from 1 to 60 minutes after the start. No problem watching the same recording on the FE/BE system. I checked almost every log I can find on the FE as well as the BE. The xsessions.errors log will show on the FE shows Code: 2006-02-12 14:22:07.711 Opening audio device '/dev/dsp'.
2006-02-12 14:22:07.711 Opening OSS audio device '/dev/dsp'. 2006-02-12 14:22:07.766 Using XV port 56 2006-02-12 14:22:08.448 Realtime priority would require SUID as root. 2006-02-12 14:22:08.450 Changing from None to WatchingPreRecorded 2006-02-12 14:22:09.134 Video timing method: USleep with busy wait [mpeg2video @ 0xb770c010]00 motion_type at 15 27 [mpeg2video @ 0xb770c010]Warning MVs not available [mpeg2video @ 0xb770c010]00 motion_type at 25 28 [mpeg2video @ 0xb770c010]Warning MVs not available [mpeg2video @ 0xb770c010]00 motion_type at 26 10 [mpeg2video @ 0xb770c010]Warning MVs not available [mpeg2video @ 0xb770c010]00 motion_type at 5 26 2006-02-12 14:24:16.880 prebuffering pause [mpeg2video @ 0xb770c010]00 motion_type at 3 14 [mpeg2video @ 0xb770c010]00 motion_type at 28 25 [mpeg2video @ 0xb770c010]invalid cbp at 12 12 [mpeg2video @ 0xb770c010]00 motion_type at 12 10 2006-02-12 14:32:59.009 prebuffering pause [mpeg2video @ 0xb770c010]ac-tex damaged at 3 26 2006-02-12 14:33:06.200 Changing from WatchingPreRecorded to None 2006-02-12 14:33:06.215 Changing from None to None Nothing of any interest on the other logs. I am running this over a wired network so I don't this it is a networking issue but am open to any suggestions. The wife is close to throwing the whole thing back into the basement. Can anyone suggest somewhere to look to find out why the FE would just stop playing? |
Author: | Big boy stan [ Tue Feb 14, 2006 11:13 am ] |
Post subject: | |
Here is an update. After spending a tremendous amount of time on the front end notebook, I decided to test out the backend with a different computer run as a frontend. I ran the kid's P3 1000MHz system from the CD frontend and it had the same problems! Playback starts and looks great but after several minutes it just stops and returns to the watch recordings screen. Since I have no problems with the backend computer playing the files itself, I am guessing that this is either a network problem or a NIC problem. I tried a different router but same result. Being a total noob, can someone point me in the direction of error logs or network utilities that might ferret out something going on with the backend. Also, shouldn't the backend log if it ran into such a problem? |
Author: | EvilTwin [ Tue Feb 14, 2006 5:21 pm ] |
Post subject: | |
http://www.knoppmythwiki.org/index.php? ... ngLogFiles |
Author: | Big boy stan [ Tue Feb 14, 2006 8:03 pm ] |
Post subject: | |
I have read through all of these logs but nothing jumps out at the time that the front end stops playing. Is there a setting for the level of logging by the backend that I need to increase? |
Author: | mschlott [ Tue Feb 14, 2006 10:11 pm ] |
Post subject: | |
Since you have seen this problem on 2 front ends, have you looked at the log files on your backend? How are these computers connected? Are they all on 100Mb wired interface? I see you have a couple of prebuffering pause messages in your log file. I get this when my bitrate and resolution are too high for my front end. What are your recording profiles like? I don't know how fammiliar you are with linux, so don't be offended if this is too basic. Do an ls -l on each of the log files mentioned in the previous link after you expereince the problem. Compare the time stamps to the output of the date comand. Use this to find log files that are being updated around the time you are having the problem. Run tail -f on the file and watch the output, while you try to reproduce the problem. good luck |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |