Could anyone please tell me how to set something up where the backend will be restarted every time it crashes? -- My backend crashes about once a week (but not a predictable time) and it really sucks to find how this out AFTER all the showes you wanted to record have passed.

Please search the mythtv archives. This has been discussed various times with various recommendations on how to set this up. Anything in the log as to why it is crashing?

_________________
cesman

When the source is open, the possibilities are endless!

Just remember sometimes you *want* to stop the backend (setup etc). What do you mean you never tinker with your box?

_________________
HP VL400 (PIII 866), Skystar2 2.6D, PVR350, Nvidia FX5200, 384MB, 200GB, KnoppMyth R5.5

I followed the link i posted above and monit seems to work pretty well for mythbackend.

If you need to run setup you could go to the monit webpage and click the stop button for the backend and then run setup so monit won't restart it automatically.

I'm having a little trouble getting it to monitor mythfrontend because unlike the backend there is no pidfile like /var/run/myth/myth-backend.pid
for mythfrontend. I think mythfrontend is invoked with knoppmyth-run script instead of an /etc/init.d/mythfrontend script and doesn't have the pid file.

Obviously i'm not a guru and couldn't get this working quickly.

cool thing is that monit emails you the log when things it monitors crash and it restarts them.

It would be cool for myth to use monit and then pop-up a transparent alert that the backend was restarted. Really its usually obvious when i can't reach the database, but when my slave backend or something goes down and the recording device is "unavailable" i often am unaware that it is missing recordings until it is too late. that is why i like the idea of using monit and receiving the log files to my email.