Larry
I know, these always seem to be a problem. My problem seems to be that anytime a job is run that requires write access to the database (specifically when scheduling shows or when deleting a previous recording) quite often the mythbackend will simply up and die. I've checked the logs and nothing seems amiss... since I use binary packages is there a way I can up the verbosity of these logs to see if anything weird is going on?
Another time the backend dies is if I've been using Mythweb, that seems to cause more crashes than it's sometimes worth (though I do prefer using Mythweb to locate shows that I want to record).
One other I've noticed is that occasionally the backend will also die upon completing a recording. Now, since I've tuned my recording settings recently I no longer transcode, I leave my recordings as mpeg2, so obviously the problem is occurring right at the moment that it should be starting to commercial flag those shows (I run automatically in my recordings). It's very inconsistent though, and in the logs I never see the commflag starting at all, just showing the Mythbackend restarting (I have a job that checks every minute if the process is running and restarts it if not). Of course, this means that I have to manually schedule the commflag job, but once I do that it works fine. I'd say the commflag works fine about 85% of the time, just sometimes it completely fails. Note that stuff recorded from commercial-free channels never seems to cause a mythbackend crash, so I think I'm pretty safe saying it's the commflagging.
Currently I'd say I lose backend about twice per day on average at the moment. Version 0.18.0 (not had time to do 0.18.1, but doesn't seem like it fixes any backend or commflag bugs).
Any thoughts?
_______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
