Plugin: SJQv4

[dadavo]

Originally Posted by Slugger

Are you using the plugin version of the task client? If so, it seems the groovy jar file is missing from your JARs folder. Ensure the groovy plugin is installed (under library plugins). If it is, ensure the groovy jar file is in JARs folder. Assuming it's not, uninstall/reinstall the groovy plugin. If it is, ensure there are no duplicates of that jar in the JARs folder. Stop Sage and remove duplicates if there are.

Yes I am using the SageTV 7 plugin only, I am not using the Windows service. I have a groovy-all-1.7.5.jar. After uninstalling Sage Task Client and then groovy this file disappear. I reinstalled and the file is back but still the same error.

[Slugger]

Originally Posted by rlvogel322

Does SJQv4 use the lobs.db? I have had my WHS system crash twice now because there is a lobs.db directory in the SageTV directory with all kinds of db files. Took up the remaining 10gig I had on the sytem partition twice.

Yes, lobs.db is used by SJQ. That's how H2 stores CLOB columns and CLOB columns is what's used to store task output. 10GB is crazy unless your tasks are dumping tonnes of output (and I mean tonnes) and the tasks are failing. By default, failed tasks will retain their output for 21 days (so as to allow time for investigation, if necessary). Successful tasks retain output for 7 days and skipped tasks for 1 day. That's all configurable in the SJQ plugin config options. I'd be having a look at the contents of some of those files, what process/task is dumping that quantity of output? Hopefully, you're not just toasting off that directory? I would assume that would corrupt your H2 database and then who knows what happens in that case. For me, my lobs.db dir contains 14KB of data in it, I've seen it get up to 500KB, but then it cleans itself up. 10GB is beyond comprehension (to me).

[Slugger]

Originally Posted by dadavo

Yes I am using the SageTV 7 plugin only, I am not using the Windows service. I have a groovy-all-1.7.5.jar. After uninstalling Sage Task Client and then groovy this file disappear. I reinstalled and the file is back but still the same error.

Is the groovy script you're using named with a .GROOVY extension (as opposed to .groovy)? If so, change the case and see if that fixes it up.

[rlvogel322]

Originally Posted by Slugger

Yes, lobs.db is used by SJQ. That's how H2 stores CLOB columns and CLOB columns is what's used to store task output. 10GB is crazy unless your tasks are dumping tonnes of output (and I mean tonnes) and the tasks are failing. By default, failed tasks will retain their output for 21 days (so as to allow time for investigation, if necessary). Successful tasks retain output for 7 days and skipped tasks for 1 day. That's all configurable in the SJQ plugin config options. I'd be having a look at the contents of some of those files, what process/task is dumping that quantity of output? Hopefully, you're not just toasting off that directory? I would assume that would corrupt your H2 database and then who knows what happens in that case. For me, my lobs.db dir contains 14KB of data in it, I've seen it get up to 500KB, but then it cleans itself up. 10GB is beyond comprehension (to me).

Unfortunately, I have had to toast the directory. It is difficult to even RDP into it when it happens. What steps should I take to get back to a clean version of SJQ if the H2 db is hosed?

[Slugger]

Stop Sage completely. Delete *.db.* (files and dirs) in the plugins/sjq/ dir, restart Sage. (You will lose all settings/config/task assignments/etc.)

[rlvogel322]

Originally Posted by Slugger

Stop Sage completely. Delete *.db.* (files and dirs) in the plugins/sjq/ dir, restart Sage. (You will lose all settings/config/task assignments/etc.)

Just to be clear, when I said I deleted the lobs.db directory it was at the SageTV/SageTV level and not the plugins/sjq/ directory. Could this mean something else is wrong?

[Slugger]

Originally Posted by rlvogel322

Just to be clear, when I said I deleted the lobs.db directory it was at the SageTV/SageTV level and not the plugins/sjq/ directory. Could this mean something else is wrong?

That means something else is using H2. The H2 db for SJQ is only ever stored in plugins/sjq/

You should see a folder under plugins/sjq named lobs.db - that's the folder where SJQ stores task output and I'd be shocked if that ever reached 10GB. I'm not the provider of the H2 db plugin, I just use it. It was there before I started SJQv4, which probably means at least one other plugin is using an H2 database for something and is probably what's filling your disk.

[Spectrum]

I've noticed that when going through the queued and completed tasks using the SJQ UI plugin that the entries will sometimes just disappear. It usually happens when scrolling up/down using the mouse wheel and it has persisted from initial install across several restarts of the SageTV service and client. It doesn't seem to affect task execution, but when it happens I have to back out of the current menu then re-enter it causing it to refresh. I made a viedeo screen cap of what is happening and through it up on a box at school. http://web.eecs.utk.edu/~rdeaver1/fi...s_Disapear.avi (~2.5MB)

I didn't see this listed as a current issue on the google code site for SJQ and couldn't find any issues re SJQ UI on tmiranda's google code site so I thought I would bring this up here to see if anyone else is seeing this or if slugger/tmiranda already know about it before logging it.

If needed I can provide logs, just let me know which logs you want

[Slugger]

Best to ticket it. Tom will need the UI logs (sageclient_0.txt). Add the link to the screencast, etc. in the ticket. Thanks.

[dadavo]

Originally Posted by Slugger

Is the groovy script you're using named with a .GROOVY extension (as opposed to .groovy)? If so, change the case and see if that fixes it up.

The file name is comskip_test.groovy. I downloaded the file from the user guide site unmodified. I changed the extension for the script to uppercase, It did not help.

[Slugger]

Originally Posted by dadavo

The file name is comskip_test.groovy. I downloaded the file from the user guide site unmodified. I changed the extension for the script to uppercase, It did not help.

I'm starting to run out of ideas. For some reason, Sage doesn't appear to be loading the groovy jar file at start up. Enable Sage debug logging, if not already on. At the start of the sage log file (sagetv_0.txt) it will list all of the jar files it's loaded into its classpath. Does the groovy jar get listed? The problem is that the JRE is not loading the groovy jar and therefore doesn't recognize groovy as a supported scripting language. Get Sage/the JRE to load that jar file properly and the problem should be fixed. Why isn't the jar being loaded? That's the real mystery. The SageTV classpath from the sage debug log might start to lead us to an answer...

[toricred]

I had a similar issue when I first set this up. For me the solution had to do with using lower case for the groovy extension in both the SJQ4 configuration and in Windows. To change the case in Windows you have to first change it to a completely different name and then back with the correct case.

[wayner]

Originally Posted by Spectrum

I've noticed that when going through the queued and completed tasks using the SJQ UI plugin that the entries will sometimes just disappear. It usually happens when scrolling up/down using the mouse wheel and it has persisted from initial install across several restarts of the SageTV service and client. It doesn't seem to affect task execution, but when it happens I have to back out of the current menu then re-enter it causing it to refresh.

I see this as well.

[Spectrum]

Originally Posted by wayner

I see this as well.

I posted a bug on the SJQ google code site and provided a log. Hopefully it won't be too hard for Tom to sort out, and if more than one person is seeing it maybe duplicating the issue won't be to hard

[Slugger]

Originally Posted by dadavo

The file name is comskip_test.groovy. I downloaded the file from the user guide site unmodified. I changed the extension for the script to uppercase, It did not help.

Originally Posted by toricred

I had a similar issue when I first set this up. For me the solution had to do with using lower case for the groovy extension in both the SJQ4 configuration and in Windows. To change the case in Windows you have to first change it to a completely different name and then back with the correct case.

Interesting... I've made a code change that should address this then, but I'm not sure when the next build will be released. In the meantime, I'd follow through with toricred's suggestion.

[bikesquid]

I'm running into a lot of queue management issues, I have to restart sage fairly often (once a day or so) and of coarse everything it was working on just stops. This is where V3 worked more the way I'd like, just scanning the recording directory and queuing up anything that didn't pass the test (existance of a comskip output file in my case). In v4 is there a way to restart whatever was being worked on rather than having to re-add the jobs manually?

Also, has anyone gotten the v3 'search and destroy' method up and running?

[Slugger]

Originally Posted by bikesquid

I'm running into a lot of queue management issues, I have to restart sage fairly often (once a day or so) and of coarse everything it was working on just stops. This is where V3 worked more the way I'd like, just scanning the recording directory and queuing up anything that didn't pass the test (existance of a comskip output file in my case). In v4 is there a way to restart whatever was being worked on rather than having to re-add the jobs manually?

Also, has anyone gotten the v3 'search and destroy' method up and running?

I'd probably try not to have to restart Sage every day, that seems like the bigger issue worth solving. With the plugin version of the task client, you kill Sage and you lose everything. With the standalone version (console or Win service), you stop Sage and the task client will continue. When you restart Sage it'll try to figure out what was running when Sage was stopped and resync itself. I say "try" because I didn't really fully test that feature so its reliability shouldn't be trusted. There is a big issue with it if a task completes before the SJQ server is restarted... the task client will try to update the task on the server and fail and then the results are lost (though the task does complete successfully). If you have to restart Sage every day and that's not going to change then I'd probably suggest moving to the standalone task client (with its associated drawbacks).

[bikesquid]

Well I 'm having a lot of problems with Sage that have started recently, running out of memory, directv serial control issues, etc... once I track down the problem it'll be stable....

I was sorta hoping sjq4 would 'log' where it's at somewhere, what job has started, etc, and simply clear that or over-write it when task is completed sucessfully, checking that list and restarting anything there before starting new tasks.... oh well.

I think I'm going to try and get the old v3 version of doing things up and running. I believe you wrote up a quick example... I'll try that first. One additional question: I'd like to do a channel test and skip if it matches the recording.... I've tried several things but I obviously just don't get it.... Any help appreciated!

[tmiranda]

Originally Posted by Spectrum

I posted a bug on the SJQ google code site and provided a log. Hopefully it won't be too hard for Tom to sort out, and if more than one person is seeing it maybe duplicating the issue won't be to hard

I'll investigate, but not until the weekend. Thanks for the log file and video!

[Slugger]

Originally Posted by bikesquid

Well I 'm having a lot of problems with Sage that have started recently, running out of memory, directv serial control issues, etc... once I track down the problem it'll be stable....

I was seeing a lot of issues then I moved from Java 6 update 22 to 6u23 and I've seen a lot of improvement since. I'd recommend moving off of 6u22 if you happen to be on it.

I was sorta hoping sjq4 would 'log' where it's at somewhere, what job has started, etc, and simply clear that or over-write it when task is completed sucessfully, checking that list and restarting anything there before starting new tasks.... oh well.

I does keep track, but it doesn't restart anything because it assumes that the task client is still running - this was before I made a last minute decision to make the task client a plugin as well. I might be able to implement something like this in the future.

I think I'm going to try and get the old v3 version of doing things up and running. I believe you wrote up a quick example... I'll try that first. One additional question: I'd like to do a channel test and skip if it matches the recording.... I've tried several things but I obviously just don't get it.... Any help appreciated!

So look at that example and I've commented where you need to add your extra constraints in that inner if statement.

So you'll want to use something like:

if(!(AiringAPI.GetAiringChannelName(mediaFile) =~ /HBO.*|SHOW.*|PPV.*|WPBS/)) {
   // This block is entered only if the channel callsign of the media file does not match the given regex
}