[mythtv-users] mythlogserver multiple copies high cpu

[Frank Phillips]

On Sat, Mar 2, 2013 at 7:24 PM, Andrei Rjeousski <arjeousski at gmail.com>wrote:

> On Sat, Mar 2, 2013 at 1:43 AM, David Farmer <remrafevad at gmail.com> wrote:
>
>>  I have been having this as an ongoing problem since I installed MythTV
>> 0.26 on an Arch Linux x86_64 box. There is a current bug report<http://code.mythtv.org/trac/ticket/11230>(ticket #11230) but it's priority is marked at low, I'm hoping that this
>> could possibly change! Trouble is, I don't know how to reproduce it. As the
>> subject says, I get multiple copies of mythlogserver and they smash the cpu
>> at a combined total of almost 100% for each core.
>>
>> My typical MythTV usage is to have it wake itself, record a program and
>> then use a HandBrakeCLI user job to transcode this, and finally shut itself
>> down. Typically a 2 hour SD recording takes 2 hours to transcode using my
>> settings, and a 2 hour HD takes about 6 hours. But since 0.26 I get up in
>> the morning and the the user jobs aren't finished and there are around 4
>> copies of mythlogserver all running, using so much cpu that HandBrakeCLI
>> only used 0.3%. But the worst example was a few days ago, I had 14
>> instances all at the same time.
>>
>
> What kind of video card do you have? I know it may sound irrelevant, but
> I've had the same issue and spend a night trying to find out what was going
> on. On my system the issue was actually caused by a bad nvidia driver (310
> or 313 i believe). The process would stall with the following call stack:
>
> (gdb) where
> #0 0x00007fd12211fd15 in _nv012tls () from /usr/lib64/libnvidia-tls.so.
> 313.18
> #1 0x00007fd12880ab58 in ?? () from /usr/lib64/libGL.so.1
> #2 0x00007fd1287e5fda in ?? () from /usr/lib64/libGL.so.1
> #3 0x00007fd1303faa63 in ?? () from /lib64/ld-linux-x86-64.so.2
> #4 0x00007fd125b8cee9 in ?? () from /lib64/libc.so.6
> #5 0x00007fd125b8cf35 in exit () from /lib64/libc.so.6
> #6 0x00007fd125b774c4 in __libc_start_main () from /lib64/libc.so.6
> #7 0x0000000000401ea9 in _start ()
>
> Since then I've downgraded to "304.64" driver and have not has any issues
> since then (4 days so far). Prior to downgrading the drive, I would get
> 10-15 instances of mythlogserver whenever the server was busy.
>
> If you are running nvidia, give it a try.
>
> This helped me. I downgraded nvidia 313.18 -> 304.64 a week ago and have
not seen more than one mythlogserver at a time since. Previously I was
having to run killall mythlogserver in a loop to let my commflagging jobs
finish.

mythtv-0.26-fixes, Arch x86_64 with 8400GS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130311/d2e54c50/attachment.html>