Mailing List Archive: Super-slow Commercial Flagging Job

Super-slow Commercial Flagging Job

Aug 16, 2023, 10:46 AM

Post #1 of 4 (171 views)

Hi Folks!

Before I do something stupid I want to check with the group. I have a
job in the Job Queue that’s been ‘stuck’ – actually it says it is
running, just super-slow:

Job: Flag Commercials Status: Running (BE4)

51% Completed @ 0.0225428 fps

“BE4” is the oh-so-clever name of the Backend

Poor thing is slowing down as four days ago was 51% @ 0.026-something fps.

Good news: other jobs are running and completing fine The show in
question was recorded July 17, so the job has been running for a month.
(And so finish by the end of August? <jk>)

Tangent: Machine Status > Server > Swap will sometimes say ‘Unknown”,
especially during recordings and for a little while (several minutes)
after recording and/or playback; otherwise reports normally. Figure
might have something to do with the Job Queue issue.

I don’t see the show listed in the AutoExpire Listing.

Backend Information:

Ubuntu 20.04 Myth version 31

RAM 32 GB

$ free -h

total    used    free shared   buff/cache   available

Mem:     31Gi   7.4Gi   505Mi      64Mi 23Gi        23Gi

Swap:   2.0Gi   2.0Gi      0B

So the question is what to do? I don’t see an option to kill it (can
pause, stop, or no change). What about OS updates, especially if needs
to reboot the Backend? (The latter is my main concern.)

Thanks!

Barry

Re: Super-slow Commercial Flagging Job [ In reply to ]

stephen_agent at jsw

Aug 16, 2023, 11:53 AM

Post #2 of 4 (171 views)

Permalink

On Wed, 16 Aug 2023 12:46:03 -0500, you wrote:

>
>Hi Folks!
>
>
>Before I do something stupid I want to check with the group. I have a
>job in the Job Queue that?s been ?stuck? ? actually it says it is
>running, just super-slow:
>
>Job: Flag Commercials Status: Running (BE4)
>
>51% Completed @ 0.0225428 fps
>
>
>?BE4? is the oh-so-clever name of the Backend
>
>Poor thing is slowing down as four days ago was 51% @ 0.026-something fps.
>
>
>Good news: other jobs are running and completing fine The show in
>question was recorded July 17, so the job has been running for a month.
>(And so finish by the end of August? <jk>)
>
>
>
>Tangent: Machine Status > Server > Swap will sometimes say ?Unknown?,
>especially during recordings and for a little while (several minutes)
>after recording and/or playback; otherwise reports normally. Figure
>might have something to do with the Job Queue issue.
>
>
>I don?t see the show listed in the AutoExpire Listing.
>
>
>Backend Information:
>
>Ubuntu 20.04 Myth version 31
>
>RAM 32 GB
>
>$ free -h
>
>total??? used??? free shared?? buff/cache?? available
>
>Mem:???? 31Gi?? 7.4Gi?? 505Mi????? 64Mi 23Gi??????? 23Gi
>
>Swap:?? 2.0Gi?? 2.0Gi????? 0B
>
>
>So the question is what to do? I don?t see an option to kill it (can
>pause, stop, or no change). What about OS updates, especially if needs
>to reboot the Backend? (The latter is my main concern.)
>
>
>
>Thanks!
>
>Barry

Back when I used to have commercial skip processing working, when I
got a job like that it was usually actually stuck and unable to
process past a patch of bad data in a file. The gradual "slowing
down" effect is caused by time going by - speed = amount of data
divided by time, so if no more data is processed but time is still
going by, the speed calculated gets gradually slower and slower.

You will need to just kill the job - run:

ps -ef | grep mythcommflag

If there are multiple mythcommflag jobs, there should be one with a
massively bigger elapsed time value. Find its PID and do:

sudo kill <pid>

and if that does not work:

sudo kill -9 <pid>
_______________________________________________
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

Re: Super-slow Commercial Flagging Job [ In reply to ]

keemllib at gmail

Aug 16, 2023, 12:07 PM

Post #3 of 4 (171 views)

Permalink

On Wednesday 16 August 2023 01:53:49 PM (-05:00), Stephen Worthington wrote:

> On Wed, 16 Aug 2023 12:46:03 -0500, you wrote:
>
> >
> >Hi Folks!
> >
> >
> >Before I do something stupid I want to check with the group. I have a
> >job in the Job Queue that’s been ‘stuck’ – actually it says it is
> >running, just super-slow:
> >
> >Job: Flag Commercials Status: Running (BE4)
> >
> >51% Completed @ 0.0225428 fps
> >
> >
> >“BE4” is the oh-so-clever name of the Backend
> >
> >Poor thing is slowing down as four days ago was 51% @ 0.026-something fps.
> >
> >
> >Good news: other jobs are running and completing fine The show in
> >question was recorded July 17, so the job has been running for a month.
> >(And so finish by the end of August? <jk>)
> >
> >
> >
> >Tangent: Machine Status > Server > Swap will sometimes say ‘Unknown”,
> >especially during recordings and for a little while (several minutes)
> >after recording and/or playback; otherwise reports normally. Figure
> >might have something to do with the Job Queue issue.
> >
> >
> >I don’t see the show listed in the AutoExpire Listing.
> >
> >
> >Backend Information:
> >
> >Ubuntu 20.04 Myth version 31
> >
> >RAM 32 GB
> >
> >$ free -h
> >
> >total used free shared buff/cache available
> >
> >Mem: 31Gi 7.4Gi 505Mi 64Mi 23Gi 23Gi
> >
> >Swap: 2.0Gi 2.0Gi 0B
> >
> >
> >So the question is what to do? I don’t see an option to kill it (can
> >pause, stop, or no change). What about OS updates, especially if needs
> >to reboot the Backend? (The latter is my main concern.)
> >
> >
> >
> >Thanks!
> >
> >Barry
>
> Back when I used to have commercial skip processing working, when I
> got a job like that it was usually actually stuck and unable to
> process past a patch of bad data in a file. The gradual "slowing
> down" effect is caused by time going by - speed = amount of data
> divided by time, so if no more data is processed but time is still
> going by, the speed calculated gets gradually slower and slower.
>
> You will need to just kill the job - run:
>
> ps -ef | grep mythcommflag
>
> If there are multiple mythcommflag jobs, there should be one with a
> massively bigger elapsed time value. Find its PID and do:
>
> sudo kill <pid>
>
> and if that does not work:
>
> sudo kill -9 <pid>
> _______________________________________________

While you're at it, I'd check for a huge mythcommflag.log. Typically
in /var/log/mythtv.
--
Bill
_______________________________________________
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

Re: Super-slow Commercial Flagging Job [ In reply to ]

barry3martin at gmail

Aug 16, 2023, 3:43 PM

Post #4 of 4 (170 views)

Permalink

Stephen and Bill:

Thanks for the replies; I’ll do some preliminary looking around based on
your information tonight but not do anything until tomorrow when nothing
is recording/being played back. (Better safe than yelled at!)

Stephen: your consideration of the job getting stuck due to a bad patch
is probably correct: I do have some major signal issues with that station.

Barry