What is the proper way to diagnose a runaway commflag job? I was running 0.22-fixes and now I'm running 0.23-fixes. I've noticed a commflag job that survives reboots. Last time I looked (before rebooting), it had been running for 4 days straight. <br>
<br>/usr/bin/mythcommflag -j 23279 -V 1<br><br>How do I determine which show is causing this and how to stop it? Should I just restart the backend with -v commflag?<br><br>I also see things in my backend log like this:<br>
ProgramInfo(3244_20100517170000.mpg), Error: GetPlaybackURL: '3244_20100517170000.mpg' should be local, but it can not be found.<br><br>I have Storage Groups enabled for recordings, videos, screenshots, etc. I also just saw this happen:<br>
AutoExpire: CalcParams(): Max required Free Space: 7.0 GB w/freq: 15 min<br>2010-05-17 19:49:56.526 Expiring 1111 MBytes for 1059 @ Thu Apr 15 11:00:00 2010 => Designed to Sell. Too many episodes, we only want to keep 6.<br>
2010-05-17 19:49:56.528 ProgramInfo(): Updated pathname '':'' -> '1059_20100415110000.mpg'<br>2010-05-17 19:49:56.544 ProgramInfo(1059_20100415110000.mpg), Error: GetPlaybackURL: '1059_20100415110000.mpg' should be local, but it can not be found.<br>
2010-05-17 19:49:56.545 ERROR when trying to delete file: GetPlaybackURL/UNABLE/TO/FIND/LOCAL/FILE/ON/lorien/1059_20100415110000.mpg. File doesn't exist. Database metadata will not be removed.<br><br>