--- Comment #10 from Bawolff (Brian Wolff) <bawolff...@gmail.com> ---
(In reply to Bawolff (Brian Wolff) from comment #9)
> >(I think its related to how we temporarily stopped making 160p
> > files. When re-renabled it I don't think jobs got re-added despite what that
> > page says).
> Err, actually we didn't do that. So never mind....
> Anyways, it looks like a bunch of jobs disappeared, and then there's an
> inconsistent state with TimedMediaHandler thinking they are just pending,
> not gone. Which may or may not be the same bug as this one. I'm not sure.
Ugh, sorry. Cannot read. Thought this was bug 61401. Ignore everything I said.
This is quite likely the right bug.
(In reply to Andre Klapper from comment #6)
> (In reply to comment #0 by jgerber)
> > videoscalers run "jobs-loop.sh ... webVideoTranscode" to process video
> > transcoding jobs. there are unprocessed jobs in the queue that never run.
> (In reply to comment #1 by aschulz4587)
> > Seems to be jobs failing rather that not ever getting run.
> Is this still a problem, and how to find out?
Someone with access to job queue log (I believe that's basically the folks with
shell access) can find out if there are failing jobs that do not have their
"failed" status reflected in the transcode table.
It would be interesting to see if those 6723 queued transcodes ever ran and
failed, or if they just never ran.
It might be good to do something like - If there are transcodes that have been
pending for more than 10 days, and if the job queue for webVideoTranscode is
empty, then automatically re-add the jobs for those videos
You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list