Seemingly out of the blue, I'm having consistent problems with my mythtv setup. I have one machine only, running R4V5. Things have been going smoothly for a few weeks now, but suddenly for the past two days, every time I try accessing recorded shows or watching live tv, I get an error message saying that it's unable to connect to the master backend, and to make sure it's running and the ip address set for it is correct. I've reset the computer, and I get the same error immediately. I can't think of anything that has changed in setup, as I haven't tinkered with the setup in a while now. The only thing I get curious about is the fact that I believe the hard drive may have completely filled up...(my auto-expire doesn't work for some reason, so instead of deleting old shows to make room for new, the newest show tries recording, then maxes out the hd...)

I still need to find the command for getting into the myth config stuff, so I can check to see that the ip address is still correct and hasn't changed or anything like that, but my other question is, what command can I use to restart the backend?

Here's an update...I found the command to restart the mythbackend, and here's what happens:



When that has run it's course, I try again, and it's already down again. Any ideas what that Segmentation fault is about, or how to resolve it?

Other folks have complained about some issues with auto expire in 0.16, you'd have to search the forums for more details. Is your limit on the number of episodes to keep set really low?

Well, for the programs I've actually witnessed cause the problem, I have the limits set to 2 or 3. However, I actually tried starting the backend, watched what show it was trying to delete, manually deleted it, tried again...a few times, and finally it worked. However, I then went back to the TV and used the menus, got to the recorded programs section...saw 3 concurrent recordings of the same program that was trying to be recorded (I only have 1 tuner..) and tried deleting them one by one as well. The first two were fine, but deleting the third and final occurrence froze up the computer. After a restart, it was like I was back where I started, with the backend crashing every time it was started.

As I spend more time on the problem, I've also noticed that if I start the backend while there are no recordings scheduled, it still crashes even without any recordings to delete. (I also have found posts mentioning a segmentation fault when trying to auto-flag commercials, but my setup is not having that same scenario.) The last two times I tried starting the backend, this is what happened:



Any suggestions?

Might not help at all, but you may want to check your database tables to see if they need repair. Search this forum for the work myisamchk.

That fixed it! Thanks very much. I've only played with it for a couple seconds...looked at the recordings, played one, exited, looked again...all seems fine. If I check it out again tomorrow and it seems like everything is still working, I'll assume it's completely fixed.

So...does anyone know what would have caused this problem in the first place?

A crash or power loss while the DB was in an inconsistent state.