I have a recent install of knoppmyth R4V5. I got my PVR350 working and was letting the system run in Live TV mode several times to see if I had any of the various crash scenarios.

Without any change on my part (that I know of ) the system on reboot will no longer run the backend. The front end come up OK. But if I try to Watch Live TV I get the error: Could not connect to master backend server...

ps -ax tells me mythbackend is not running.

/var/log/mythtv/mythbackend.log has 5 entries telling me it started (i.e. the version message etc.) but nothing indicating why it quit. (There is the error creating /.qt message, but other posts here indicate that is innocuous).

I've tried the mysql fix ups listed here:
http://mysettopbox.tv/phpBB2/viewtopic.php?t=1043
with no change.

I can start mythbackend from the console:
#/usr/bin/mythbackend&
and it runs and Live TV works. (Can't say for how long yet)

Any ideas or clues?

HW:
TYAN Trinity 100AT MB
AMD K6-2 500
VIA MVP chipset
160G WD HD
168 MB RAM
PVR 350


Thanks

This happens to me when I shut down my myth system while it's doing commercial flagging. If there's no flagging going on when I shut down, it starts up cleanly. When mythbackend fails to start, I have to kick start it manually, sometimes several times before it stays around.

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

I updated mine from the debs and twice now (only on a startup) the backend failed to start. I had to start it manually (/etc/init.d/mythbackend start) then rebooted and it worked (knock on wood) and has been working now for several weeks.

I don't know what caused it to not work.

_________________
Retired KM user (R4 - R6.04); friend to LH users.

Thanks for the replies.

I started it manuallay shortly after my post. After the next reboot it was good. I guess this is "normal" for the current level of code. Maybe a future release will solve it.

Back to investigating the dreaded "blinking lights crash"....

What do you type and where do you type it to 'manually kick start' your backend in this situation? I have a single computer (frontend/backend) system.

Thanks.

well graysky has already posted that.

this has to be run from a root console.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Sorry, I'm so new that I didn't know how to do any of that or where to do it.

There's step by step info for those like me at: http://knoppmythwiki.homelinux.org/index.php?page=TroubleShooting

Thanks for your patience.

I just upgraded from mythtv 0.15.1 to 0.16 via debs. I had the exact same problem - through two reboots, the backend would not stay up. From an SSH session, I was able to /etc/init.d/mythtv-backend start and it stayed up.

I looked at the logs to see why it was crashing, and saw that during the two reboots, the first thing the backend did was to resume commercial flagging on two programs. I assume that now that the commercial flagging has completed on those two programs, the backend will come up fine after the next reboot. I can't test it now, as the wife is getting her HGTV fix.

If this doesn't fix the problem, I'll write back with more findings.

_________________
R5Fxx

Home-Brewed Mythic Dragon Clone
200GB WD IDE /myth
2x250GB WD IDE (lvm) /myth/tv