[mythtv-users] fixes branch: can't kill mythbackend

Steven Adeff adeffs.mythtv at gmail.com
Wed Nov 19 14:07:19 UTC 2008

On Wed, Nov 19, 2008 at 8:34 AM, George Mari
<george_mythusers at mari1938.org> wrote:
> Steven Adeff wrote:
>> lately mythbackend has gone rogue on me. it sits the computer at 100%
>> on the wa meter in top and doesn't respond to any of the frontends, as
>> well I can't kill -9 it, I *have* to reboot. I have no idea why it
>> gets like this or why it's only been lately that this happens, but
>> being that it forces me to reboot the computer manually I then have to
>> wait for my RAID array to resync which is not fun.
>> anyone have any ideas?
>> thanks!
> If it's 100% on wa, that means its waiting for some IO operation to
> complete.  Use lsof to see what files that PID has open.
> Any messages in /var/log/messages or the mythbackend log?
> Does it only happen while it's recording, or playing back, or doing
> nothing, all of the above?

Ah, I tried fuser but did not think of using lsof... damnit.

I can't tell what it's doing other than it stops writing to the log
and puts a lock on my RAID array such that I can't stop it. I have not
noticed it happen during playback, so far it has only occured when no
frontend is streaming anything (they may be on, but just at a menu),
and at least the last few times mythcommflag had two processes running
(which is what I have it capped to).

I'll try lsof next time it happens. If it is a file operation on the
RAID array, is there a way to see why it cannot complete the IO

Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -

More information about the mythtv-users mailing list