First off, I'll apologize, I am two versions back on dvd::rip (0.98.1)...but it sounds like it doesn't matter as this is more a transcode problem than a dvd::rip problem..
I have a very similar problem to the others reported under this subject
I have 3 nodes in my cluster:
1. master -- running FC5 2.6.16 x86_64 (3600+)
2. secondary -- running FC4 2.6.17 x86_64 (semperon something, sometimes i wonder why i bother with this one...)
3. secondary -- running FC6 2.6.20 i386 (old p4)
when running with the first two nodes i never had this problem -- in fact the 1st two still never have this problem... only the 3rd node has
an issue -- as noted, it seems as though it finishes the transcode job then never
picks up the next job (dvd::rip reports it as "running" -- doesn't have a status
for it, etc)
If i "stop" the node then "start" the node, it comes back to life for another pass or two, but invariably, does not run for that long (certainly not the all night/work time runs that my other two nodes are capable of)..
Note I didn't notice until reading the other post, but stopping and starting the node also seems to leave many transcode processes running on that node. Alternatively if when the node is in the "running" state (but not actually running), if i kill the older transcode process, the status on the cluster control immediately begins to show status again.
I just turned on logging for transcode on that node so maybe that will give me a bit more....
I'm just posting to this list 1st off because it seems like a couple of others had a similar issue -- I was wondering if they had come up with a fix on their own (and thus they had gone silent)...
My thanks in advance for any advice or
whatnot.
Regards,
~joe.
DOCUMENTATION
TABLE OF CONTENTS