Mythbacked is seg faulting on startup after auto upgrading to .16 .. Here's the output when I kick it off from the shell:

mythtv@mythtv:~ $ mythbackend
Starting up as the master server.
getattr: Input/output error
2004-09-24 22:32:57 mythbackend version: 0.16.20040906-1 www.mythtv.org
2004-09-24 22:32:57 Enabled verbose msgs : important general
2004-09-24 22:32:59 Found changes in the todo list.
2004-09-24 22:32:59 Scheduled 59 items in 0.087196 seconds.
2004-09-24 22:32:59 Recording starts soon, AUTO-Startup assumed
2004-09-24 22:33:07 Started Commercial Flagging for "Unscrewed With Martin Sargent" recorded from channel 1354 at Wed Sep 15 00:29:00 2004
Segmentation fault



I ran the 'mysqlcheck -u root mythconverg ' to check the integrity of my database and all was well. Does anyone know how I can tell the backend not to worry about the commerical flagging it's choking on?

I thought I figured it out. I changed the commercial flagging for that program from 0 to 1 and it worked. I was able to watch live tv and all seemed well until I rebooted.

Now I get this:

mythtv@mythtv:~ $ mythbackend
Starting up as the master server.
2004-09-24 22:54:06 mythbackend version: 0.16.20040906-1 www.mythtv.org
2004-09-24 22:54:06 Enabled verbose msgs : important general
2004-09-24 22:54:08 Found changes in the todo list.
2004-09-24 22:54:08 Scheduled 59 items in 0.08864 seconds.
2004-09-24 22:54:08 Recording starts soon, AUTO-Startup assumed
Segmentation fault


Not much to go on. How can I tell what's causing the grief? /var/log/mythtv/mythbackendlog doesn't provide any additional information.

*EDIT* Okay, so I figured out that if you use the verbose option it tells you what's going on .. Again it was a problem with the commercial flagging.

Now the backend starts fine and stays running, BUT now all my previous recordings are screwed. When I try to play them, it gives me a file not found error on the backend. Indeed, the file that it is trying to play is not there, but the number of nuv files in /myth/tv match the number reported from mythweb/gui (I assume) ... Any ideas on what might have brought about this 'corruption' and what might be done to 'fix' it? TIA

I'm having the same problem, I think I am going to wipe out the database and recreate it. I've been having issues with it anyways. My myth box is in my entertainment center and I did the update from my office using ssh. The problem is I left mythfrontend running with mythweather on it while updating and that may be the cause of all these problems.

I found the problem. My timezone was set to Pacific instead of Central when the database import took place. I looked at one of my recordings and noticed that the time in the filename (20040923185900) and the time listed in the database (20040923205900) was off by two hours.

I then renamed the file /mythtv/tv/2011_20040923185900_20040923200000.nuv to match the database:

mv 2011_20040923185900_20040923200000.nuv 2011_20040923205900_20040923220000.nuv


Now all is well with that file. Unfortunately, I've got about 60 more files that will need to be modified. I guess I'll try and write a little script to rename the files instead of doing it all by hand.

This problem also occured in the R4V4 upgrade. You can just fix the time setting, restart the affected servers, and restore from your DB back up again to resolve it. Search for an old message by me with the details.

mythrestore worked perfectly! Thanks for the tip. The only problem I have now is :

Warning at /usr/share/mythtv/mythweb/recorded_programs.php, line 103:
symlink(): Permission denied

This is located at the top of the recorded programs page under mythweb

Looks like the ownership of /usr/share/mythtv/mythweb doesn't match the user running mythweb. I'm fighting other battles and don't have time to sort out the "right" answer so I've just hacked it. As the mythtv user:

Also see this thread: http://www.gossamer-threads.com/lists/mythtv/users/73258

It was a permissions problem. Thanks again for pointing me in the right direction.

Argh!!! Where are the details!!! Seriously, don't just say that you fixed something, include enough details for someone else to do the same. Did you change the ownership of the directory and everything in it to "www-data"? Make apache run as "mythttv"? Use the hack shown? Something entirely different?

tjc: thanks for the hack, that did it. I'm also just had a problem where a recorded program crashed my mythbackend, so I've turned off commercial flagging. Bummer.

No need to turn it off. You just need to change the value for that program's commercial flag from 0 to 1 in the database. This will trick the backend into thinking it flagged that program. The recording that is causing the problem can be found in the backend log.

My main concern is that it not happen again... in particular that it not happen on Wednesday night, where I had BETTER record Lost, West Wing AND Law & Order or I will be in deep trouble. If there's some instability now in commercial flagging I'm not going to risk having it kill my backend completely and miss a recording.

For what it's worth, my mythbackend has not had problems since I fixed the offending entries. My uptime is something like two and half days.

2.5 days doesn't fill me with confidence... before this problem, my KnoppMyth box had never crashed on me, and we're talking months of operation. Only time I needed to reboot it was after changing something that required it. I will probably just run mythcommflag manually because then (I assume) it won't bring down the backend if it crashes.

Uptime of 2.5 days is pretty good if you consider I fixed the backend 2.5 days ago! What I'm trying to tell you is that I haven't had any problems with the backend since I fixed the offending recordings. Take it for what it's worth.