> >#996: mythjobqueue fails to transition from "stopping" to "finished" if new > >jobs > >enter queue
> I've seen something similar that might give someone an idea: I had 40 > programs orso scheduled for transcode. Halfway trough I had to restart > mythbackend to try a few changes I made. when I restarted mythbackend > (old=.18 new=svn head) the last program it was busy with transcoding was > now marked "stopping". the next one would actually be running. It would > stay like that for maybe an hour orso.. maybe the OP did the same thing? No, his jobs actually ran, went to "stopping" and never made it out, the backend stayed up the whole time. I've looked at his logs and can't tell what is happening by looking at them, I do know though that the JobQueue should print out a success/fail message after the myth_system() call finishes, so it appears that may not be finishing. The transition to JOB_STOPPING is just about the last thing that mythtranscode does before exitting, so I'm not 100% sure that this is the case, but want to verify since I know the JobQueue should also be printing out something right after mythtranscode finishes but I don't see this in the logs. -- Chris _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
