There have been a few threads about the problem with mythcommflag
getting stuck and backing up the job queue. A while back I posted a
script I wrote to detect and kill the stuck jobs, but I wanted to find
the cause and did some more research, to no avail. The message, below,
contained the information I needed to find the .ts file so I could check
it for problems, but I found no problems with the files and, in fact,
manually initiated the exact same command as the hung process and it
always works. I have tested this perhaps five or six times, trying
variations on the commands, and it has always functioned normally; never
hangs or fails in any other way.
Another problem I've had (and posted about) is the "Decoder Error" and
frontend crashes on programs recorded over the firewire connection to
our cable box. I have "solved" that problem with a script I wrote that
detects corrupt files based on unrealistic duration reported by ffprobe
and discards the beginning of the file using dd. Since all of my hung
mythcommflag processes were also on firewire recordings, I figured it
was likely the same problem and I could fix it with the same technique
(hence the need to find the .ts file that caused the hang). No luck.
All I have to do is run mythcommflag again (no dd required) and it just
works.
Someone posted a while back that if mythcommflag runs during a DB
backup that it could cause it to hang, so I moved the time of my backup
to a time when I KNOW there are no jobs running and it didn't help; I
still get hung mythcommflag processes.
So, I figured I'd post the results of my efforts in case anyone else is
interested. I'm just adding the same command to my script that detects
the hung processes and, assuming the new process doesn't hang, I'll call
it "fixed" (or at least dealt with).
Dave D.
On 8/1/20 10:37 PM, DaveD wrote:
>
> On 8/1/20 1:35 PM, Bill Meek wrote:
>> On 8/1/20 1:15 PM, DaveD wrote:
>>> What's the -j argument in my process list for mythcommflag? I can't
>>> find any mention of a -j command line argument anywhere and --help
>>> doesn't list it, either. When mythcommflag hangs and my script to
>>> check for hung mythcommflag processes detects it, the script just
>>> kills the process and I get no commercial flagging on that
>>> recording. I would like to try repairing the recording with the
>>> same technique I use to repair the "Decoder error" recordings using
>>> dd to remove the first three blocks of the recording. I'm guessing
>>> a hung mythcommflag is the same problem, just not as severe, where
>>> the highly compressed h264 recording is not handled properly by
>>> MythTV. So I'm trying to figure out what file is being commflagged
>>> when the process hangs based on the ps output so I can remove the
>>> first few blocks and see if it will then comm flag without hanging.
>>>
>>> Dave D.
>>
>> Use mythcommflag --help j (or jobid).
>
> Ah, I figured it was a job number and Leo's reply pointed me at the
> right table (jobqueue). A join with the recorded table yields the
> basename:
>
> SELECT basename from jobqueue, recorded where recorded.chanid =
> jobqueue.chanid AND recorded.starttime = jobqueue.starttime AND
> jobqueue.id = NUMBER_FROM_HUNG_PROCESS (the -j parameter sent to
> mythcommflag).
>
> Thanks! I'll post the results of my attempts to repair (or prepare?)
> the recording so mythcommflag can process it without hanging.
>
> Dave D.
>
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
getting stuck and backing up the job queue. A while back I posted a
script I wrote to detect and kill the stuck jobs, but I wanted to find
the cause and did some more research, to no avail. The message, below,
contained the information I needed to find the .ts file so I could check
it for problems, but I found no problems with the files and, in fact,
manually initiated the exact same command as the hung process and it
always works. I have tested this perhaps five or six times, trying
variations on the commands, and it has always functioned normally; never
hangs or fails in any other way.
Another problem I've had (and posted about) is the "Decoder Error" and
frontend crashes on programs recorded over the firewire connection to
our cable box. I have "solved" that problem with a script I wrote that
detects corrupt files based on unrealistic duration reported by ffprobe
and discards the beginning of the file using dd. Since all of my hung
mythcommflag processes were also on firewire recordings, I figured it
was likely the same problem and I could fix it with the same technique
(hence the need to find the .ts file that caused the hang). No luck.
All I have to do is run mythcommflag again (no dd required) and it just
works.
Someone posted a while back that if mythcommflag runs during a DB
backup that it could cause it to hang, so I moved the time of my backup
to a time when I KNOW there are no jobs running and it didn't help; I
still get hung mythcommflag processes.
So, I figured I'd post the results of my efforts in case anyone else is
interested. I'm just adding the same command to my script that detects
the hung processes and, assuming the new process doesn't hang, I'll call
it "fixed" (or at least dealt with).
Dave D.
On 8/1/20 10:37 PM, DaveD wrote:
>
> On 8/1/20 1:35 PM, Bill Meek wrote:
>> On 8/1/20 1:15 PM, DaveD wrote:
>>> What's the -j argument in my process list for mythcommflag? I can't
>>> find any mention of a -j command line argument anywhere and --help
>>> doesn't list it, either. When mythcommflag hangs and my script to
>>> check for hung mythcommflag processes detects it, the script just
>>> kills the process and I get no commercial flagging on that
>>> recording. I would like to try repairing the recording with the
>>> same technique I use to repair the "Decoder error" recordings using
>>> dd to remove the first three blocks of the recording. I'm guessing
>>> a hung mythcommflag is the same problem, just not as severe, where
>>> the highly compressed h264 recording is not handled properly by
>>> MythTV. So I'm trying to figure out what file is being commflagged
>>> when the process hangs based on the ps output so I can remove the
>>> first few blocks and see if it will then comm flag without hanging.
>>>
>>> Dave D.
>>
>> Use mythcommflag --help j (or jobid).
>
> Ah, I figured it was a job number and Leo's reply pointed me at the
> right table (jobqueue). A join with the recorded table yields the
> basename:
>
> SELECT basename from jobqueue, recorded where recorded.chanid =
> jobqueue.chanid AND recorded.starttime = jobqueue.starttime AND
> jobqueue.id = NUMBER_FROM_HUNG_PROCESS (the -j parameter sent to
> mythcommflag).
>
> Thanks! I'll post the results of my attempts to repair (or prepare?)
> the recording so mythcommflag can process it without hanging.
>
> Dave D.
>
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org