Plugin: Sage Job Queue (SJQ)

[Skirge01]

Am I the only person who think that this switch is worded backwards?

The interface reads:

SJQ should ignore failed tasks (allows for automatic requeuing):

My--admittedly, often flawed--thinking read this to be asking me: Do you want SJQ to perform any action on a task which has failed?

In my mind, a setting of yes meant that when a task fails, SJQ should ignore the failed task and not do anything to it, including attempting to requeue the task. Therefore, I had this set to "no", because I wanted SJQ to requeue the failed tasks. Clearly, once I noticed that nothing was requeueing, no matter what I tried, I eventually read the user guide and figured out that I had the question backwards.

Just curious if I'm the only one who got this all confused.

[fabiotv]

Originally Posted by nyplayer

Moving files by title to different drives...

I recently discovered I have the same problem.
Do you mind giving me some hints on how to get the task done? Maybe you can share some snippets of your working script?

My recording files are named like: 55_6_0721_0755-0.mpg.

I would like to move them like this:

from 55_6_0721_0755-0.mpg to L:\Italia uno\09 07 luglio 21 ore 07.55.mpg where:

- the first two characters define the folder (55=Italia uno)
- than I put the year (09)
- than, after the second "_" there is the month (07=07 luglio) and the day 21
- in the end there is the starting time (0755=ore 07.55)

The folders already exists.

At the beginning I would delete the old files manually but after the script will pass some test I would like to delete the originals automatically.

Thank you for your attention.

[fabiotv]

Sorry to ask again for help.
I read the guide of SJQ but I couldn't find any example, or even a list of commands, to help me understand how to move files to a new location and how to rename them according to their original file names.

So, if anybody has already done that, please consider to give me some help or some sample code.

Thanks again.

[nyplayer]

Fabio,

We need more info... SJQ does not move recordings(by Itself) you need to create a batch job that SJQ will run or transcode them within sage.

1. What type of operating system?
2. What type of recordings you want to move mpg mp4 etc...
3. Do you still want to keep them in Sage?
4. Do you want to transcode them or keep(move) the original recording?
5. Do your recordings contain multiple audio?

[fabiotv]

Originally Posted by nyplayer

1. What type of operating system?

Xp SP3

2. What type of recordings you want to move mpg mp4 etc...

mpg from DVB-T

3. Do you still want to keep them in Sage?

They can "become" videos but, if it doesn't make things more complicated, I'd like to keep them as recordings (for the "group per channel name" function there).

4. Do you want to transcode them or keep(move) the original recording?

For now I'm not interested in transcoding them because they have a life length of only a few days.

5. Do your recordings contain multiple audio?

How do I check this? Gspot is OK?


The most basic task I would like to start with is just the renaming of the files in a more readable format in order to be able to deal with them as videos (I imported the recording folder into videos too).

Thanks.

[nyplayer]

Here is a script I put together for you. If you save it as a bat file and drag a file to it it should work. If this does what you want automatically ... then we can work on setting SJQ. This will do a copy not a move want to make sure it works first.


move.bat

set filein=%~n1
if %filein:~-11,2% EQU 01 set mese=gennaio
if %filein:~-11,2% EQU 02 set mese=febbraio
if %filein:~-11,2% EQU 03 set mese=aprile
if %filein:~-11,2% EQU 04 set mese=marzo
if %filein:~-11,2% EQU 05 set mese=maggio
if %filein:~-11,2% EQU 06 set mese=giugno
if %filein:~-11,2% EQU 07 set mese=luglio
if %filein:~-11,2% EQU 08 set mese=agosto
if %filein:~-11,2% EQU 09 set mese=settembre
if %filein:~-11,2% EQU 10 set mese=ottobre
if %filein:~-11,2% EQU 11 set mese=novembre
if %filein:~-11,2% EQU 12 set mese=dicembre
set year=%date:~-2,2%
set day=%filein:~-9,2%
set hour=%filein:~-6,2%
set min=%filein:~-4,2%

if %filein:~0,2% EQU 55 mkdir "l:\Italia uno"
if %filein:~0,2% EQU 55 copy "%~f1" "l:\Italia uno\%year% %mese% %day% ore %hour%.%day%.mpg"

[wayner]

Hey - your Italian is even better than Brad Pitt's in "Inglourious Basterds"!

[nyplayer]

Slugger,

Thanks for adding PhysicalFileCount works great.

[fabiotv]

Originally Posted by nyplayer

Here is a script I put together for you. If you save it as a bat file and drag a file to it it should work. If this does what you want automatically ... then we can work on setting SJQ. This will do a copy not a move want to make sure it works first.

It works.

I checked and saw that Sage does not pad the channel custom number so, I can get a filename like this: 58_12_0829_0917-0.mpg.
If I understand your script (thanks a lot for helping me) the different length of the filename will complicate the script, won't it?

Thanks.

By the way: can you point me to a good e complete resource about batch programming language, please? Thanks.

[nyplayer]

One of the most useful sites is this one. You can take a look at the Set Command etc...

[fabiotv]

If I rename a recording it will loose its recording status, right?

Can I think to first rename the file and then apply the _MANUALREC task to make Sage treat it as a recording again but with the new name?
Will Sage be able to still use the channel name as a grouping parameter?

Thanks.

And thanks for the interesting link, too.

[Skirge01]

Slugger, I'm still having the issues we discussed here. I have not had the file cleaner turned on for quite some time, but still have the hanging issues. I'm attaching the most recent data from both the wrapper.log and jetty log on the server. Around the time of these logs, I had several comskip processes hang on the server.

One thing I'm wondering is if jumbo frames being turned on is causing some sort of choke point at the server. But, that doesn't really make sense because when the server is writing to it's own drives, I'm still having the issue. Theoretically, the server shouldn't be using the NIC in that instance.

Any ideas for what I can try for troubleshooting?

[Slugger]

It's not the 2009_08_xx.request.log file I need from Jetty, it's the 2009_08_xx.stderrout.log file that I need. This will be the file that logs the exceptions that are being thrown. If you are not seeing this file (it's in the same location as the 2009_08_xx.request.log file) then you must enable debug logging in Jetty - see JettyStarter.properties.

While you stop Sage to enable debug logging, also upgrade the SJQ server and task client to the latest versions. Server is snapshot 511 and task client is snapshot 504. Then when you start seeing the HTTP 500 errors again, get the stderrout log and send that to me, please.

[Skirge01]

Sorry about that, Slugger. I went ahead and upgraded and am waiting to report back results. In the mean time, can you tell me how I get SJQ to recognize that a client rebooted (i.e. crashed) while running some comskip instances and that those instances were also crashed and not restarted? I have yet to figure out a way to do this without stopping SageTV, but when I do stop Sage, SJQ then doubles up the comskip instances on the clients which didn't crash.

[Slugger]

Originally Posted by Skirge01

Sorry about that, Slugger. I went ahead and upgraded and am waiting to report back results. In the mean time, can you tell me how I get SJQ to recognize that a client rebooted (i.e. crashed) while running some comskip instances and that those instances were also crashed and not restarted? I have yet to figure out a way to do this without stopping SageTV, but when I do stop Sage, SJQ then doubles up the comskip instances on the clients which didn't crash.

Currently not possible, but is (indirectly) involved with issue 69.

The best way to handle this now is to clear out jobs that are waiting in the queue, let the current running jobs finish, then restart SJQ - that will get everything back in sync. You shouldn't have to stop Sage to restart SJQ for this. Just go to the \jetty\contexts directory and update the time stamp of the sjq.context.xml file - that will force Jetty to restart the app. If you're on Windows, this can be achieved by simply opening the file and saving it (on Linux use the touch command).

I assume the task client isn't making your client machines reboot? If so, I'd really like to dig into that.

[Skirge01]

That's definitely at least one scenario in which I have seen this happen for me, so at least I now know one way to prevent this from happening.

And you are correct, it's definitely not the SJQC that's causing the reboot.

[JimmyBalboa]

On the BLANK SAVE BUTTON issue.

Originally Posted by Slugger

You're not the first person to report this problem. What version are you running? Unfortunately, I'm just not able to reproduce this problem and so I have no way to track it down at the moment. Could you try installing the GWT debug build (sjq-gwtdbg-2.1.5.389.zip) and then reproducing this and getting me the JavaScript error?

I am new to SJQ. Installed it last night and am having the same issue. I can't save the settings. Could this be a Vista issue? I am ruining Vista(x64).

Do you have a resolution for this yet?

Thanks,

[Slugger]

I'm still not able to reproduce the problem myself so I'm just not able to track it down.

[Peter_h]

Originally Posted by Slugger

Currently not possible, but is (indirectly) involved with issue 69.

The best way to handle this now is to clear out jobs that are waiting in the queue, let the current running jobs finish, then restart SJQ - that will get everything back in sync. You shouldn't have to stop Sage to restart SJQ for this. Just go to the \jetty\contexts directory and update the time stamp of the sjq.context.xml file - that will force Jetty to restart the app. If you're on Windows, this can be achieved by simply opening the file and saving it (on Linux use the touch command).

I assume the task client isn't making your client machines reboot? If so, I'd really like to dig into that.

Would you be opposed to adding a "Restart SJQ" button?

My reasoning is the same as in issue 69 that I posted on your code site. My server is headless and I only allow one machine in the house to RDP into the server.

If I needed to restart SJQ I would need to go to the test machine, RDP into the Server and then change the timestamp on the txt file.

[Slugger]

Originally Posted by Peter_h

Would you be opposed to adding a "Restart SJQ" button?

My reasoning is the same as in issue 69 that I posted on your code site. My server is headless and I only allow one machine in the house to RDP into the server.

If I needed to restart SJQ I would need to go to the test machine, RDP into the Server and then change the timestamp on the txt file.

Hmm... a button that restarts itself, not a big fan of that idea. Though I suppose I could do it, I'd be more interested in a Jetty manager type app that lets you load/stop/restart any of the other plugins you've installed on it. That makes more sense to me. Now you've just got to find someone to write it.