Plugin: Sage Job Queue (SJQ) v3

[razrsharpe]

i just noticed that SJQ is dumping alot of debug logging to the sagetv_0.txt log... Prior to me upgrading to the SJQ that is in the repository i never noticed it doing that (not that i look through the servers logs that often though ) Here's a snippit from the server log

INFO - Checking client '127.0.0.1': 100 resources free.
INFO - Servlet POST request completed [0ms]
INFO - Thread started...
INFO - Thread started.
INFO - Thread sleeping...
INFO - Thread started...
INFO - Thread sleeping...
INFO - Thread sleeping.
INFO - Run completed [0ms]
INFO - Run completed [0ms]
INFO - Checking client '127.0.0.1': 100 resources free.
INFO - Servlet POST request completed [0ms]
Fri 5/21 22:29:30.209 [PooledThread@1db9672] Seeker.finishWatch(/127.0.0.1:3610@@SAGETV_PROCESS_LOCAL_UI)
Fri 5/21 22:29:30.211 [PooledThread@1db9672] Seeker.finishWatch(/127.0.0.1:3610@@SAGETV_PROCESS_LOCAL_UI)

[Slugger]

Originally Posted by razrsharpe

i just noticed that SJQ is dumping alot of debug logging to the sagetv_0.txt log... Prior to me upgrading to the SJQ that is in the repository i never noticed it doing that (not that i look through the servers logs that often though ) Here's a snippit from the server log

INFO - Checking client '127.0.0.1': 100 resources free.
INFO - Servlet POST request completed [0ms]
INFO - Thread started...
INFO - Thread started.
INFO - Thread sleeping...
INFO - Thread started...
INFO - Thread sleeping...
INFO - Thread sleeping.
INFO - Run completed [0ms]
INFO - Run completed [0ms]
INFO - Checking client '127.0.0.1': 100 resources free.
INFO - Servlet POST request completed [0ms]
Fri 5/21 22:29:30.209 [PooledThread@1db9672] Seeker.finishWatch(/127.0.0.1:3610@@SAGETV_PROCESS_LOCAL_UI)
Fri 5/21 22:29:30.211 [PooledThread@1db9672] Seeker.finishWatch(/127.0.0.1:3610@@SAGETV_PROCESS_LOCAL_UI)

Some of that is SJQ, some of it is not. SJQ also dumps all it's log messages into sjq.log. Lines 1, 2, 8-11, inclusive are SJQ, the rest are not. At the end of the day, it's a log/debug file so it's going to get filled with lots of stuff from all over the place. Wouldn't worry too much about it. I will say, though, that for SJQ specific issues, just focus on the sjq.log file. Only SJQ messages end up in that file.

[Brent]

Originally Posted by Slugger

Go to the dir where you installed the client. In there is a dir called logs and in there is a file called wrapper.log. What does it have to say about the startup error?

PHP Code:

STATUS | wrapper  | 2010/05/20 20:35:45 | Launching a JVM...
INFO   | jvm 1    | 2010/05/20 20:35:45 | WrapperManager: Initializing...
INFO   | jvm 1    | 2010/05/20 20:35:45 | SJQ Task Client v3.0.2.771
INFO   | jvm 1    | 2010/05/20 20:35:45 | Using 'C:/sjqc' as location for configuration file...
INFO   | jvm 1    | 2010/05/20 20:35:45 | localhost:8080
STATUS | wrapper  | 2010/05/20 20:35:47 | <-- Wrapper Stopped
STATUS | wrapper  | 2010/05/21 21:49:48 | --> Wrapper Started as Service
STATUS | wrapper  | 2010/05/21 21:49:48 | Java Service Wrapper Community Edition 3.3.1
STATUS | wrapper  | 2010/05/21 21:49:48 |   Copyright (C) 1999-2008 Tanuki Software, Inc.  All Rights Reserved.
STATUS | wrapper  | 2010/05/21 21:49:48 |     http://wrapper.tanukisoftware.org
STATUS | wrapper  | 2010/05/21 21:49:48 | 
STATUS | wrapper  | 2010/05/21 21:49:48 | Launching a JVM...
INFO   | jvm 1    | 2010/05/21 21:49:52 | WrapperManager: Initializing...
INFO   | jvm 1    | 2010/05/21 21:49:52 | SJQ Task Client v3.0.2.771
INFO   | jvm 1    | 2010/05/21 21:49:52 | Using 'C:/sjqc' as location for configuration file...
INFO   | jvm 1    | 2010/05/21 21:49:52 | localhost:8080
STATUS | wrapper  | 2010/05/21 21:49:54 | <-- Wrapper Stopped 


NOTE: I changed the above to say localhost instead of the actual address its using.

Here's the error when I try to run the service (the one it installed) from windows:

[Slugger]

Originally Posted by Brent

PHP Code:

STATUS | wrapper  | 2010/05/20 20:35:45 | Launching a JVM...
INFO   | jvm 1    | 2010/05/20 20:35:45 | WrapperManager: Initializing...
INFO   | jvm 1    | 2010/05/20 20:35:45 | SJQ Task Client v3.0.2.771
INFO   | jvm 1    | 2010/05/20 20:35:45 | Using 'C:/sjqc' as location for configuration file...
INFO   | jvm 1    | 2010/05/20 20:35:45 | localhost:8080
STATUS | wrapper  | 2010/05/20 20:35:47 | <-- Wrapper Stopped
STATUS | wrapper  | 2010/05/21 21:49:48 | --> Wrapper Started as Service
STATUS | wrapper  | 2010/05/21 21:49:48 | Java Service Wrapper Community Edition 3.3.1
STATUS | wrapper  | 2010/05/21 21:49:48 |   Copyright (C) 1999-2008 Tanuki Software, Inc.  All Rights Reserved.
STATUS | wrapper  | 2010/05/21 21:49:48 |     http://wrapper.tanukisoftware.org
STATUS | wrapper  | 2010/05/21 21:49:48 | 
STATUS | wrapper  | 2010/05/21 21:49:48 | Launching a JVM...
INFO   | jvm 1    | 2010/05/21 21:49:52 | WrapperManager: Initializing...
INFO   | jvm 1    | 2010/05/21 21:49:52 | SJQ Task Client v3.0.2.771
INFO   | jvm 1    | 2010/05/21 21:49:52 | Using 'C:/sjqc' as location for configuration file...
INFO   | jvm 1    | 2010/05/21 21:49:52 | localhost:8080
STATUS | wrapper  | 2010/05/21 21:49:54 | <-- Wrapper Stopped 


NOTE: I changed the above to say localhost instead of the actual address its using.

Here's the error when I try to run the service (the one it installed) from windows:

Hmm... that's unusual. Usually this will tell us the exact problem. Here, it's just telling us that the wrapper stopped. I'm kind of stuck now. My best guess is that it can't find java.exe, but that's only a guess. Can you get the non-service version to run? Which version of Windows was this again?

[aflat]

I'm having the same issues as TallMomof2. Upgraded from V2 to V3, and now I can't get to the web page. I don't mind cleaning up and starting for scratch, but what would I have to clean up? I'm also not using a standard port, 8580 for me, since I have another webserver on 8080.

[aflat]

Easy enough, uninstalled it via the UI, renamed the jetty dir, and removed the jars from the sagetv\jars dir, then reinstalled and I'm back in business. Maybe it was just an upgrade issue.

[Slugger]

Originally Posted by aflat

Easy enough, uninstalled it via the UI, renamed the jetty dir, and removed the jars from the sagetv\jars dir, then reinstalled and I'm back in business. Maybe it was just an upgrade issue.

Yes, some users that have upgraded Jetty from an older version are seeing duplicate jars in their JARs folder, which will prevent Jetty from starting up. You will know if this is an issue by looking in SageTV\JARs\ and if you see more than one version of jetty-6.*.jar (i.e. jetty-6.1.19.jar and jetty-6.1.11.jar) then you need to stop Sage, delete the older jars then restart. You will likely see duplicates of many of Jetty's jars if you're in this situation. All the duplicates must be removed. Once you do that then restart Sage and Jetty should be able to start up.

[razrsharpe]

Originally Posted by razrsharpe

i just noticed that SJQ is dumping alot of debug logging to the sagetv_0.txt log... Prior to me upgrading to the SJQ that is in the repository i never noticed it doing that (not that i look through the servers logs that often though )

Originally Posted by Slugger

Some of that is SJQ, some of it is not.

I think this possibly has something to do with Sage not depending on commons-logging anymore (that they introduced in 7.0.9). Plucky submitted a bugrequest to sage to look at it.. because he's noticed it too. So far i have seen sjq, sagealert, and sagemymovies logging in the server's log.

[Slugger]

SageTV v7/SJQ v3.1.x users may want to disable SJQ's file cleaner in favour of my new Sage Artifact Delete (SAD) plugin. This plugin is a lot more efficient in how it finds and deletes artifacts and also has a delay built in before it deletes artifacts, which would allow things like SJQ's _MOVEREC task to copy the artifacts before they're toasted off your hard drive.

[QueOnda]

Please point me in the right direction. I installed the plugin through v7 but can't really find the how to run it or configure

I tried to connect from webbrowser mycomputerip:80/sjq but no luck

[phareous]

Originally Posted by QueOnda

Please point me in the right direction. I installed the plugin through v7 but can't really find the how to run it or configure

I tried to connect from webbrowser mycomputerip:80/sjq but no luck

Wouldn't that be 8080, not 80?

[QueOnda]

Originally Posted by phareous

Wouldn't that be 8080, not 80?

Opps mistyped. Yes, I tried this http://192.168.0.3:8080/sjq and I get "Oops! This link appears to be broken."

When I had sagetv v6, I didn't use sjq and never installed it. Only installed through program installer.

[phareous]

Did you restart sagetv? I would try to restart the service. Also did you install the Jetty web server? Make sure you have that too.

I wished I could be of more help but I already have jetty/sjq on there before I upgraded to v7

[QueOnda]

Thanks phareous, I'll give it a try.

I didn't restart the sage but will do so tonight. I do have the jetty web server 1.7.5.22 (had that installed in v6 but re-installed after v7 through plugin because of the updated files.) I will post back tomorrow to see if the restart of sage helped.

[QueOnda]

Restarted of Sagetv works. Going to post in the beta...

[QueOnda]

Ok. I see where you need to create rulesets for comskip but where do you specify where comskip is located? I currently reading the manual but cannot find my answer: http://docs.google.com/View?id=dz87g...28166432316313

[razrsharpe]

you define the COMSKIP task in the task client config.... here's an example from the manual

[toricred]

I've been trying to use SageAlert to reboot my HD-PVRs when they get a capture error and since upgrading to Sage 7 it's not working right. I started thinking that it might be much easier to do this directly from SJQ. Is there a way to trigger an external batch file based on the content of a system message's description?

[Slugger]

Originally Posted by toricred

I've been trying to use SageAlert to reboot my HD-PVRs when they get a capture error and since upgrading to Sage 7 it's not working right. I started thinking that it might be much easier to do this directly from SJQ. Is there a way to trigger an external batch file based on the content of a system message's description?

Sure.

if [IsObjSysMsg == true && $.GetSystemMessageString{} =* "whatever string you're looking for"] {
   MYTASK
}

[toricred]

So to get system messages I assume I need to tell it to connect to SageAlert. Is that correct? Also if I'm monitoring for capture failures do I need to set up the frequency to check for something like 1 minute?