sage job queue failed jobs -need help

[raffmanlt]

Ok I am trying to set this up to better control comskip, b4 used
comskip monitor which was easy. I have managed to get the server and
the client on the server to work with some problems and my other
client I have yet to get to run at all.

1st: The job queue seems to initially work, listing all of the jobs
and then assigning the 4 comskip processes I am allowing to run at
once. All the other jobs that were waiting then show up in the failed
jobs queue and it does not seem to reload them. Only 1 job shows in
the successfuly completed area, yet it did actually process some of
the others if you look at the log for the specific video that failed.
If you look at the files : it did create edl, txt, log and logo files
at least on some, others only have a log file and others that have
not been processed at all. I thing the log only ones happened when I
previously used a different version of comskip.

I think at this point it is actually processing all 4 sucessfuly but
is not reporting back that it is completed and for some reason it
dumps everything into the failed list. It does not on its own load
the next 4 to process. Any ideas?

This is my server ruleset:
if [IsTV == true && IsScheduledRecording == true && ChannelNumber !=
"23" && ChannelNumber != "17" && IsWatched == "false" && FileExists !=
"%d%/%p%.edl" && Filename =$ ".mpg"]
{
COMSKIP
}


The client file is:
:MAXPROCS 4
COMSKIP {
:MAX 0
:CPU "LOW"
"C:/comskip/comskip.exe \"%c%\""
}

[raffmanlt]

___________-
_________________update:__________________________________________

ok I have now discovered that the ones with edl files were previously
processed, new ones have the txt file instead of edl. I also noticed
that all of the ones waiting in the queue or being processed had
already been processed and had txt files, logo, and log - no edl. So
I modified my ruleset to include checking for .txt and not processing
if it existed. After saving and reloading the ruleset. I cleared out
all the failed jobs and the ones still waiting in queue and ran the
queueloader again and it still put jobs in the queue that it should
not. I then ran the debugger on a file that was still waiting to be
processed that had .txt file already and it showed it properly checked
all the conditions and recognized that a file already existed but it
still ran the comskip process..... ????
_______________________________________________________________

> }- Hide quoted text -
>
> - Show quoted text -

[Derek Battams]

Comskip, unfortunately, returns 1 on success instead of the expected
0. So add the :RETURNCODE 1 option to the client config and the jobs
should be marked as successful. If jobs are still being added to the
queue that you don't expect should be then paste the debugger output
for me to see.

[Bob Raffety]

Thank you Derek!

For some reason today it is no longer loading all of them in the queue so what you said should take care of me.  Would I include that at the very end or just before the final brackets.  I am guessing it would be:

:MAXPROCS 4
COMSKIP {
:MAX 0
:CPU "LOW"
"C:/comskip/comskip.exe \"%c%\""

:RETURNCODE 1 }

[Derek Battams]

On Tue, Aug 18, 2009 at 01:03, Bob Raffety<bdr.di...@gmail.com> wrote:
> Thank you Derek!
> For some reason today it is no longer loading all of them in the queue so
> what you said should take care of me.  Would I include that at the very end
> or just before the final brackets.  I am guessing it would be:
> :MAXPROCS 4
> COMSKIP {
> :MAX 0
> :CPU "LOW"
> "C:/comskip/comskip.exe \"%c%\""
> :RETURNCODE 1 }

It needs to go above the command line (i.e. right below the :CPU
option in the block above).