| LinHES Forums http://forums.linhes.org/ |
|
| system was fine-- now system is Screwed! http://forums.linhes.org/viewtopic.php?f=17&t=7799 |
Page 1 of 1 |
| Author: | Domino [ Mon Jan 09, 2006 9:23 pm ] |
| Post subject: | system was fine-- now system is Screwed! |
My mythbox was great. Fabulous. Worked great, aside from the fact that one tuner (out of 4) was giving me nothing but snow. I intended to swap it out, but as an intermediate step, I thought I'd just remove its entry from mythtv-setup . And that, ladies and gentlemen, was the day the music died. I deleted the card's entry, and now I (and, more importantly, mythfrontend) can't communicate with mythbackend. At all. The IP and port settings are the same (the default, 127.0.0.1:6543); mythbackend is listening on that port, and mythfrontend says it's trying to talk to the server on that port. But it can't get any conversation going. From checking the large files magically appearing in /myth/tv, I know that mythbackend is not just running but actively recording scheduled programs. But when I run mythfrontend, as soon as I select any menu entry that would require communication with mythbackend (such as scheduling new programs or watching recordings/videos), it hangs for 60 seconds or so and then reports the infamous "cannot connect to mythbackend server" message. I get similar results from the command line when running something like "mythbackend --printsched." I have tried rebooting about six dozen times; I'm running version 5A26 of KnoppMyth; and it's a single-machine setup, so both server and client are running in the same machine. I don't know what else to try, but I'm very frustrated and would love to know how to get these two crazy kids (mythfrontend and mythfrontend) together again. Oh! and the four tuners are two Hauppauge 500MCE's if that makes a difference. I've tried re-enabling the fourth tuner without success. I've tried deleting the settings for all four tuners and setting them up from scratch again in mythtv-setup--still nothing. Help? |
|
| Author: | Xsecrets [ Mon Jan 09, 2006 10:49 pm ] |
| Post subject: | |
have you tried checking the database for corruption and repairing if necessary? there is a sticky post in either howto or tips and tricks. |
|
| Author: | Domino [ Tue Jan 10, 2006 7:37 pm ] |
| Post subject: | |
Xsecrets wrote: have you tried checking the database for corruption and repairing if necessary? there is a sticky post in either howto or tips and tricks.
I have now-- no database corruption found. All my .MYI files are apparently fine. Anyone have any other ideas? This obviously makes my whole Myth system unusable, since communication between mythfrontend and mythbackend is kind of how it works. What would cause mythbackend to be incommunicado like this? Frontend is trying to talk to backend on 127.0.0.1:6543, and backend is listening on that port as well. But nothing is apparently getting through... Anyone know why just disabling that fourth tuner would have screwed something up so badly? Or is it merely a coincidence that this problem developed after I did that? Help! EDIT: Oh, and I saw some reference to problems being caused when a disk fills up. That hasn't happened here. I've got 600Gb for /myth, and only about 40% is used. |
|
| Author: | tkoster [ Tue Jan 10, 2006 11:12 pm ] |
| Post subject: | |
If the front end is working, I'd recommend going to the knoppmyth menu and doing a backup. Then do an upgrade install. It should at least get all of your hardware working correctly. But you will still have the extra card's channel info in your database (see mythtv-setup with the back-end stopped) and its zap2it account to remove. |
|
| Author: | fiete [ Wed Jan 11, 2006 12:00 am ] |
| Post subject: | |
Is your network up and running? Can you just ping 127.0.0.1? |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|