Plugin: SJQv4

[tmiranda]

Originally Posted by bikesquid

On another note, I keep getting "schedule not valid" when trying to commit changes and have to re-enter ON even though it's already showing that.... I assume it should maintain the existing schedule if there is one, no?

Can you explain this a little more please? Are you saying the UI shows the schedule to be "ON" but when you commit it says it's no good? If you then re-enter "ON" it works?

Thanks for the clarification.

Tom

[bikesquid]

Originally Posted by tmiranda

Can you explain this a little more please? Are you saying the UI shows the schedule to be "ON" but when you commit it says it's no good? If you then re-enter "ON" it works?

Thanks for the clarification.

Tom

Exactly. To recreate I just did the following:
Go to assigned task, select the task, go to test script line and edit it by backspacing one character and putting it back, then hit 'commit now' and get the schedule is not valid. it must be on, off, or a valid crontab pattern. Hit OK, hit schedule, hit manually edit, hit ok, hit comit now and it asks if I'm sure and goes on with life.

another oddities as well. When first entering the client page, it shows two clients (which is correct), the one I was at last is highlighted (second in the list) and when I arrow right to the detail, it shows the info for the first, go left, then right and it shows the correct info for the second on the list....

[jbuszkie]

Just when I thought I was starting to understand V3, you go and change EVERYTHING!!! Grrr.....

I do like the UI... but I think I'm going to miss the web interface.

Are there instructions to go back to V3. (even if it's manual) if I choose to do that?

I can't get V4 to work so far.. I think I've copied the Comskip app correctly..
but it's not working.

2010-12-13 18:07:50,255 INFO  [Handler]: CMD: RMTASK :: PEER: /192.168.2.58
2010-12-13 18:07:51,378 INFO  [TaskQueue]: Running queue processor now!
2010-12-13 18:07:51,398 INFO  [TaskQueue]: Assigned task 4 of type 'COMSKIP' to Client[host=htpc-3:23344,state=ONLINE,lastUpdate=Mon Dec 13 18:07:51 EST 2010]
2010-12-13 18:07:51,400 INFO[ListenerClient]: Disconnected from htpc-3:23344
2010-12-13 18:07:51,961 INFO[Listener]: Received connection from: /192.168.2.58
2010-12-13 18:07:53,622 ERROR [Handler]: IOError
java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(Unknown Source)
	at java.net.SocketInputStream.read(Unknown Source)
	at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
	at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Unknown Source)
	at java.io.ObjectInputStream$BlockDataInputStream.refill(Unknown Source)
	at java.io.ObjectInputStream$BlockDataInputStream.read(Unknown Source)
	at java.io.DataInputStream.readUnsignedShort(Unknown Source)
	at java.io.ObjectInputStream$BlockDataInputStream.readUnsignedShort(Unknown Source)
	at java.io.ObjectInputStream$BlockDataInputStream.readUTF(Unknown Source)
	at java.io.ObjectInputStream.readUTF(Unknown Source)
	at com.google.code.sagetvaddons.sjq.listener.Handler.run(Handler.java:62)
	at java.lang.Thread.run(Unknown Source)
2010-12-13 18:07:53,627 INFO[Listener]: Received connection from: /192.168.2.58
2010-12-13 18:07:53,627 INFO  [Handler]: CMD: LOGTEST :: PEER: /192.168.2.58
2010-12-13 18:07:53,641 INFO  [Handler]: CMD: QUIT :: PEER: /192.168.2.58
2010-12-13 18:08:13,379 INFO  [TaskQueue]: Scheduling queue processor for ~8 seconds from now!
2010-12-13 18:08:21,379 INFO  [TaskQueue]: Running queue processor now!
2010-12-13 18:08:43,361 INFO[ListenerClient]: Disconnected from htpc-3:23344
2010-12-13 18:08:43,361 INFO  [ActiveTaskManager]: Validated 1 running task(s)!
2010-12-13 18:08:43,379 INFO  [TaskQueue]: Scheduling queue processor for ~8 seconds from now!
2010-12-13 18:08:51,380 INFO  [TaskQueue]: Running queue processor now!
2010-12-13 18:09:13,315 INFO  [AgentManager]: Pinging Client[host=htpc-3:23344,state=ONLINE,lastUpdate=2010-12-13 18:07:51.381]
2010-12-13 18:09:13,319 INFO[ListenerClient]: Disconnected from htpc-3:23344
2010-12-13 18:09:13,379 INFO  [TaskQueue]: Scheduling queue processor for ~8 seconds from now!
2010-12-13 18:09:21,380 INFO  [TaskQueue]: Running queue processor now!
2010-12-13 18:09:43,360 INFO[ListenerClient]: Disconnected from htpc-3:23344
2010-12-13 18:09:43,360 INFO  [ActiveTaskManager]: Validated 1 running task(s)!
2010-12-13 18:09:43,379 INFO  [TaskQueue]: Scheduling queue processor for ~8 seconds from now!
2010-12-13 18:09:51,379 INFO  [TaskQueue]: Running queue processor now!
2010-12-13 18:10:13,380 INFO  [TaskQueue]: Scheduling queue processor for ~8 seconds from now!

I see an error in the log file... It doesn't really give me a lot of info... Not sure how to proceed from here.

The agent log file has this.. So it seems like it's doing the right thing??

2010-12-13 18:07:23,087 WARN  [ProcessRunner]: Removing task from active list: SJQ4Task-192.168.2.58-23347-3
2010-12-13 18:07:51,389 INFO  [Exe]: Received task 4 of type 'COMSKIP' from 192.168.2.58:23347...
2010-12-13 18:07:51,389 INFO  [192_168_2_58-23347-4]: Starting process runner for: Task[id=COMSKIP, reqRes=100, maxInst=1, sched=ON, maxTime=3600, maxTimeRatio=1.0, rc=0-1, exe=c:\comskip\comskip_nice.cmd, exeArgs="$SJQ4_PATH\$SJQ4_LAST_SEGMENT", test=c:\comskip\comskip_test.groovy, testArgs=mpg]
2010-12-13 18:07:51,389 INFO  [ProcessRunner]: Converted '"$SJQ4_PATH\$SJQ4_LAST_SEGMENT"' to '"D:\TV\IncomeProperty-9781218-0.mpg"'
2010-12-13 18:07:53,642 INFO[ListenerClient]: Disconnected from 192.168.2.58:23347
2010-12-13 18:08:43,360 WARN  [ProcessRunner]: isActive(SJQ4Task-192.168.2.58-23347-4) = true; [SJQ4Task-192.168.2.58-23347-4]

[jbuszkie]

ok It did seem to work after all.. I guess it took a while.. The error is a little worrysome... We'll see how it works on a real recording..


Jim

[MitchSchaft]

Is there a way to turn off system messages for just SJQ? I'm not ready to upgrade/donate and don't want to get the notice every day.

[bikesquid]

My client now seems to be doing a comskip on a NEW recording, probably explains the 'null' error I was getting. In the good ol' days of v3 it simply scanned the directory and tackled anything without the .edl... I liked that, how can I get that process concept back? AND how can I get it to do the things left unprocessed by post update black hole?

[Slugger]

Originally Posted by bikesquid

Well, there's some log info, wish there was an easy way to cut/paste it, but here's the jist of it... LOG4j: Configured logging for:saex-api using file: sagex-api.log4j.properties javax.script.scriptexecption:java.lang.NumberFormatException: null.

it does that a few times.

Got a couple other questions about "how to" as well.

Have a look at the metadata for any of the tasks in the queue. Is there a SJQ4_ID variable defined for them? It seems like there isn't for some reason. If not, what metadata is defined for the tasks?

1) assuming I get the task running, is there an easy way to assign it to multiple clients, or do I have to rekey it as a new task for each client?

Not at this time. I'd ticket it for tmiranda to consider.

2) maybe this is a UI issue as well, but I select a client to 'see' what's going on and it asks me if I'm sure I want to delete the client... as I'm not using a remote, a mouse makes much more sense if select selects rather than deletes.... not sure if that's a question... other than in my mind....

Clicking/selecting a client will prompt for deletion, just highlighting it will load it on the right. It's as designed, but doesn't mean it can't be improved, again, tickets are the way to go for this kind of stuff.

[Slugger]

Originally Posted by jbuszkie

ok It did seem to work after all.. I guess it took a while.. The error is a little worrysome... We'll see how it works on a real recording..


Jim

The connection reset errors can be ignored (usually, almost always). It's just the client disconnected from the server before the server's processed the command; not a big deal.

[jbuszkie]

Originally Posted by bikesquid

My client now seems to be doing a comskip on a NEW recording, probably explains the 'null' error I was getting. In the good ol' days of v3 it simply scanned the directory and tackled anything without the .edl... I liked that, how can I get that process concept back? AND how can I get it to do the things left unprocessed by post update black hole?

ditto for me! Also the file cleaner ability would be nice.. or a walk through on how to implement it!

[Slugger]

Originally Posted by jbuszkie

ditto for me! Also the file cleaner ability would be nice.. or a walk through on how to implement it!

Still shouldn't be getting the null pointer on a new recording.

Best way to get the file cleaner: install my Sage Artifact Delete plugin. If you would rather implement it in SJQ then open a ticket and I'll write a tutorial on one way to do it (but it probably won't be before Christmas).

[Slugger]

Originally Posted by bikesquid

My client now seems to be doing a comskip on a NEW recording, probably explains the 'null' error I was getting. In the good ol' days of v3 it simply scanned the directory and tackled anything without the .edl... I liked that, how can I get that process concept back? AND how can I get it to do the things left unprocessed by post update black hole?

A new recording does not have an edl so it qualifies. I assume you've attached your comskip tasks to your favourites? You can move them to the RecordingStopped event instead of RecordingStarted and that'll delay when comskip starts, but it's still going to start on new recordings.

You could skip attaching tasks to favs and write a script that periodically scans your recordings and queues up comskip tasks like the old way. This is also how you'd have to cover the black hole scenario you talk about.

[tmiranda]

Originally Posted by bikesquid

Exactly. To recreate I just did the following:
Go to assigned task, select the task, go to test script line and edit it by backspacing one character and putting it back, then hit 'commit now' and get the schedule is not valid. it must be on, off, or a valid crontab pattern. Hit OK, hit schedule, hit manually edit, hit ok, hit comit now and it asks if I'm sure and goes on with life.

another oddities as well. When first entering the client page, it shows two clients (which is correct), the one I was at last is highlighted (second in the list) and when I arrow right to the detail, it shows the info for the first, go left, then right and it shows the correct info for the second on the list....

I found what was causing the first bug but I'm not so sure about the second. I think I have a fix.

Please download the attached file, unZip and put it in the Sage install directory of your Sage SERVER (do not put it in the install directory of your SageClient if you are using one.) You should then see an "Update Available" message for the Sage Job Queue UI. Install the update and let me know if your issues are fixed.

If they are not, please zip up you log file and post the attachment.

Thanks,

Tom

Edit - I have updated the plugin in the repository. No need to download and install the attached zip file.

[bikesquid]

Originally Posted by Slugger

Have a look at the metadata for any of the tasks in the queue. Is there a SJQ4_ID variable defined for them? It seems like there isn't for some reason. If not, what metadata is defined for the tasks?

No info beyond time and queuetasknow=manual

It did run when there was a 'new' recording. This seems to be an issue with prior recordings.... which I'd obviously like to have run through the comskip if they've not got the edl.

[Slugger]

Originally Posted by MitchSchaft

Is there a way to turn off system messages for just SJQ? I'm not ready to upgrade/donate and don't want to get the notice every day.

Should only generate a message when the SageTV or the plugin starts up. Is it spamming perodically without a restart of Sage and/or the plugin? It shouldn't do that.

[Slugger]

Originally Posted by bikesquid

My client now seems to be doing a comskip on a NEW recording, probably explains the 'null' error I was getting. In the good ol' days of v3 it simply scanned the directory and tackled anything without the .edl... I liked that, how can I get that process concept back? AND how can I get it to do the things left unprocessed by post update black hole?

Originally Posted by Slugger

A new recording does not have an edl so it qualifies. I assume you've attached your comskip tasks to your favourites? You can move them to the RecordingStopped event instead of RecordingStarted and that'll delay when comskip starts, but it's still going to start on new recordings.

You could skip attaching tasks to favs and write a script that periodically scans your recordings and queues up comskip tasks like the old way. This is also how you'd have to cover the black hole scenario you talk about.

I think it's worth mentioning at this point that one of the key goals of SJQv4 (for me) was to get out of maintaining a custom scripting environment (which is what the old SJQv3 rulesets and client configs were). Instead, I'm providing the scripting/automation environment and the burden of scripting solutions for tasks falls on the user. With that said, I'm more than willing to write some scripts for some tasks, but be aware that:

• Scripting solutions for tasks is not a priority
• My priority (for SJQv4) is providing and maintaining the environment

My hope is once we get going that some other users will start to contribute their scripts for common tasks. Until then, I`ll help out where I can, but do not expect fast turn around times, especially during the holidays.

[Slugger]

Originally Posted by bikesquid

No info beyond time and queuetasknow=manual

It did run when there was a 'new' recording. This seems to be an issue with prior recordings.... which I'd obviously like to have run through the comskip if they've not got the edl.

How are you queuing the prior recordings? Without a custom script, you'd have to manually select each recording and send it to SJQ from the recording details menu. That'd be the only way to get the proper metadata attached to each task.

[bikesquid]

Originally Posted by Slugger

How are you queuing the prior recordings? Without a custom script, you'd have to manually select each recording and send it to SJQ from the recording details menu. That'd be the only way to get the proper metadata attached to each task.

Well, I'm having two problems, how I'm queuing them is the first, that's solved. Second, I've got one client (on the server machine) working, and one client (via service on a different machine) not working. I assume it's a path issue? How do I know what the $sjq4_path value is and if that's unc or not?

[bikesquid]

Originally Posted by tmiranda

I found what was causing the first bug but I'm not so sure about the second. I think I have a fix.

Please download the attached file, unZip and put it in the Sage install directory of your Sage SERVER (do not put it in the install directory of your SageClient if you are using one.) You should then see an "Update Available" message for the Sage Job Queue UI. Install the update and let me know if your issues are fixed.

If they are not, please zip up you log file and post the attachment.

Thanks,

Tom

That worked. Very nice. Are you running a different thread regarding the UI or is this the right place to discuss those things as well?
Thanks for the quick fix.

[tmiranda]

Originally Posted by bikesquid

That worked. Very nice. Are you running a different thread regarding the UI or is this the right place to discuss those things as well?
Thanks for the quick fix.

This is the place. No sense in two threads. Slugger handles the hard issues, I handle the easy ones

[bikesquid]

Having a problem with a client running the ntservice and wonder if this wrapper.log entry has anything to do with it?
STATUS | wrapper | 2010/12/13 17:20:07 | Launching a JVM...
INFO | jvm 1 | 2010/12/13 17:20:07 | WrapperManager: Initializing...
INFO | jvm 1 | 2010/12/13 17:20:07 | LOG4J: Configured Logging for: sagex-api using file: sagex-api.log4j.properties
INFO | jvm 1 | 2010/12/13 17:20:07 | Embedded SageAPI is not functional. We are most likely running remotely.
INFO | jvm 1 | 2010/12/13 17:20:07 | Adding Remote Server: Master-PC
INFO | jvm 1 | 2010/12/13 17:20:08 | SJQv4 Agent (Task Client) v4.0.0.1325
INFO | jvm 1 | 2010/12/13 17:20:08 |
INFO | jvm 1 | 2010/12/13 17:20:08 | The following scripting engines are available in this task client:
INFO | jvm 1 | 2010/12/13 17:20:08 | Mozilla Rhino/1.6 release 2 [js]
INFO | jvm 1 | 2010/12/13 17:20:08 | Groovy Scripting Engine/2.0 [groovy]
INFO | jvm 1 | 2010/12/13 17:20:08 |
INFO | jvm 1 | 2010/12/13 17:21:01 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].
INFO | jvm 1 | 2010/12/13 17:21:01 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].
INFO | jvm 1 | 2010/12/13 17:21:01 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].
INFO | jvm 1 | 2010/12/13 17:21:02 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].
INFO | jvm 1 | 2010/12/13 17:21:02 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].
INFO | jvm 1 | 2010/12/13 17:21:31 | log4j:ERROR Attempted to append to closed appender named [sjqAgentApp].