[mythtv-users] mythlogserver multiple copies high cpu

Craig Treleaven ctreleaven at cogeco.ca
Sat Mar 2 14:55:16 UTC 2013


At 5:13 PM +1030 3/2/13, David Farmer 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 
><http://code.mythtv.org/trac/ticket/11230>current bug report (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.

I am not a dev, but...  Can you change the logging parameters for 
mythbackend (and probably mythwelcome) to '--verbose system,general' 
and capture  all the logs produced the next time this occurs?

Adding "system" to the verbose settings should cause a log entry each 
time mythlogserver is started up.  A line like:

>2013-01-22 19:31:10.371307 I [401/28931] Logger system-unix.cpp:868 
>(Fork) - Managed child (PID: 402) has started! * 
>command=/opt/local/bin/mythlogserver --daemon  --verbose none,system 
>--logpath /opt/local/var/log/mythtv.26 --loglevel debug, timeout=0

Hopefully, this will show which apps are causing mythlogserver to launch...

Craig


More information about the mythtv-users mailing list