On Wed, February 16, 2005 8:17 am, Neil Bird said: > > Since upgrading to 0.17 last W/E [ATrpms], mythbackend has died > without logs twice. Both times, I'd been fiddling around in mythweb > looking at recorded items & schedules shortly beforehand. > > *May* not be related, just very suspicious. I'll check over the W/E > when I'm not worried about losing the backend to see if I can trigger > it, but in the meantime, anyone else seen anything like this recently?
I have. Did the same upgrade and have noticed the same thing -- mythbackend quietly died on my FE/BE box. I started it up with "-v all" and it ran fine the rest of that day and all night long. A few hours ago I restarted it normally (service mythbackend start) and have since accessed things via mythweb a couple times. So far so good.... Something else I did and was suspicious of was a cron job running on another box (more processing power & less noise) to do the mythcommflag grunt work. I've since made it a Slave BE and let it run as designed under 0.17. Thinking that may have had something to do with the mysterious terminations. -mS _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
