For some reason mythbackend is failing, I'd like someway to restart it automatically. Any suggestions?

Thanks


As an aside here's the log when the crash occured

2006-01-19 10:00:02.409 Started recording "Living in the Sun" on channel: 1005 on cardid: 1, sou
rceid 1
2006-01-19 10:00:02.459 scheduler: Schedule Change
2006-01-19 10:00:03.122 DVB#0 DVB signal 4a | snr ffff | ber 0 | unc 0
2006-01-19 10:00:03.129 DVB#0 Status: LOCK.
2006-01-19 10:00:03.135 DVB#0 Multiplex Locked
2006-01-19 10:00:04.417 DVB#0 Successfully tuned to channel 1.
2006-01-19 10:00:04.560 Changing from None to RecordingOnly
2006-01-19 10:00:04.646 DVB#0 Recorder: Card opened successfully (using PS mode).
2006-01-19 10:00:04.670 DVB#0 Data read from DMX - This is for debugging with transform.c
2006-01-19 10:08:14.370 DVB#0 WARNING - No data from card in 1 second.
2006-01-19 10:08:15.379 DVB#0 WARNING - No data from card in 1 second.
2006-01-19 10:09:36.159 DVB#0 WARNING - No data from card in 1 second.
2006-01-19 10:43:39.496 DVB#0 WARNING - No data from card in 1 second.
2006-01-19 10:43:40.506 DVB#0 WARNING - No data from card in 1 second.

QSettings::sync: filename is null/empty
2006-01-19 20:29:45.020 New DB connection, total: 1
Starting up as the master server.
2006-01-19 20:29:45.276 mythbackend: MythBackend started as master server
QSettings::sync: filename is null/empty
2006-01-19 20:29:45.311 New DB connection, total: 2
2006-01-19 20:29:45.326 DVB#0 DVB SI Table Parser Started
2006-01-19 20:29:45.395 DVB#0 Using DVB card 0, with frontend Hauppauge Nova-T DVB-T.
QSettings::sync: filename is null/empty
2006-01-19 20:29:45.411 New DB connection, total: 3
2006-01-19 20:29:46.371 DVB#0 DVB signal 4c | snr ffff | ber 0 | unc 0
2006-01-19 20:29:46.377 DVB#0 Status: LOCK.
2006-01-19 20:29:46.385 DVB#0 Multiplex Locked
2006-01-19 20:29:47.659 DVB#0 Successfully tuned to channel 3.
QSettings::sync: filename is null/empty
2006-01-19 20:29:47.689 New DB scheduler connection
2006-01-19 20:29:47.703 mythbackend version: 0.18.1.20050523-1 www.mythtv.org
2006-01-19 20:29:47.714 Enabled verbose msgs : important general
2006-01-19 20:29:49.703 Reschedule requested for id -1.
2006-01-19 20:29:50.167 Scheduled 24 items in 0.5 = 0.37 match + 0.09 place
2006-01-19 20:29:50.189 scheduler: Scheduled items
2006-01-19 20:29:50.197 Recording starts soon, AUTO-Startup assumed
2006-01-19 20:29:57.711 mythbackend: Running housekeeping thread
2006-01-19 20:30:02.266 Started recording "Gadgets Gadgets Gadgets" on channel: 1039 on cardid: 1, sourceid 1
2

I have a simple script with this in:



Then I run it via cron every 5 mins

Sorry, but a script that automatically restarts the backend in my opinion is a bad idea. If the backend is dying, you need to find out why and resolved this. All you are accomplishing by restarting is buy filling up the log.

_________________
cesman

When the source is open, the possibilities are endless!

Yeah, what Cecil said. That script is a bad idea for several reasons, not to mention being symptomatic of knowing just enough to be dangerous.

Point taken.

How do I go about getting more information about the crashes then? I don't usually see anything in mythbackend.log.

You could try this:
http://mysettopbox.tv/phpBB2/viewtopic. ... ktrace+gdb

I use the script because my backend crashes from using a hauppauge mvp frontend with mvpmc, not a lot I can do other than not use it!

Don't really know what you mean. If you get a backtrace, the mythtv-dev guys might be able to help (although you would probably need to be running a semi recent version of SVN for them to take any notice of you).

I use a Hauppauge MediaMVP with mvpmc every day and I've never had it crash my (R5A16) backend. Heck, I wouldn't use the thing if it crashed my backend that consistently.

Its wasn't that often, about once a week. I have a r5a22 backend so maybe thats why yours doesn't crash