SageTV Community  

Go Back   SageTV Community > SageTV Development and Customizations > SageTV Customizations
Reload this Page Plugin: Sage Job Queue (SJQ) v3
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

SageTV Customizations This forums is for discussing and sharing user-created modifications for the SageTV application created by using the SageTV Studio or through the use of external plugins. Use this forum to discuss customizations for SageTV version 6 and earlier, or for the SageTV3 UI.

Reply
Page 47 of 68 « First 374546 47 484957 Last »
 
Thread Tools Search this Thread Display Modes
  #921  
Old 07-02-2010, 09:28 AM
nyplayer nyplayer is offline
SageTVaholic
  
Join Date: Sep 2005
Posts: 4,997
Quote:
Originally Posted by graywolf View Post
OK. Got a RESCHED task setup. Will see how it works.

One other question, my wife usually pads this show by 1 min (start/end). Any means of maintaining that with the RESCHED task? or another task/method?
If you enable the hidden extras in Sage if you haven't yet you can set the default padding for manual recordings in details - customize. That way when a show is marked as manual it will acquire the default padding.
__________________
Channels DVR UBUNTU Server 2 Primes 3 Connects TVE SageTV Docker with input from Channels DVR XMLTV and M3U VIA Opendct.
Reply With Quote
  #922  
Old 07-02-2010, 11:22 AM
graywolf's Avatar
graywolf graywolf is offline
Sage Icon
  
Join Date: Oct 2009
Location: NC
Posts: 1,389
Thanks for the info. I'll try playing around some with those also.
Reply With Quote
  #923  
Old 07-02-2010, 02:36 PM
nyplayer nyplayer is offline
SageTVaholic
  
Join Date: Sep 2005
Posts: 4,997
Slugger,

Any reason why this doesnt work

$.GetAiringChannelNumber{} > "31"

Code:
java.lang.RuntimeException: Invalid string operator: >
	at com.google.code.sagetvaddons.sjq.server.tests.FieldString.run(FieldString.java:59)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$StringComparator.run(RulesParser.java:67)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.testInput(RulesParser.java:299)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.reflect(RulesParser.java:278)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.runTest(RulesParser.java:155)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.evalTest(RulesParser.java:143)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.(RulesParser.java:99)
	at com.google.code.sagetvaddons.sjq.server.RulesParser$Evaluator.(RulesParser.java:122)
	at com.google.code.sagetvaddons.sjq.server.RulesParser.loadQ(RulesParser.java:357)
	at com.google.code.sagetvaddons.sjq.server.RulesParser.(RulesParser.java:331)
	at com.google.code.sagetvaddons.sjq.server.MediaFileQueueLoader.run(MediaFileQueueLoader.java:73)
	at java.lang.Thread.run(Unknown Source)

Edit Never mind I see it is not numeric but a string. I have to figure out another way to ignore channels 1-31
__________________
Channels DVR UBUNTU Server 2 Primes 3 Connects TVE SageTV Docker with input from Channels DVR XMLTV and M3U VIA Opendct.
Last edited by nyplayer; 07-02-2010 at 02:45 PM.
Reply With Quote
  #924  
Old 07-02-2010, 03:13 PM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
Quote:
Originally Posted by nyplayer View Post
Edit Never mind I see it is not numeric but a string. I have to figure out another way to ignore channels 1-31
# Ignore channels 1-31 via a regex (untested, looks good to me though)
$.GetAiringChannelNumber{} !% "[1-9]|[1-2]\\d|3[0-1]"
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #925  
Old 07-06-2010, 08:55 PM
bthurber bthurber is offline
Sage User
  
Join Date: May 2005
Posts: 59
Quote:
Originally Posted by ewelin View Post
I can no longer login to SJQ... I pull up the SJQ webpage, enter in my password and it just sits there, never loading the interface.
Same thing happened to me. sjq.sqlite file was 145mb. Loaded up sqlite3.exe and looked at the log table. Had a crazy number of comskip audio panic messages. I ran the command:

delete from log;

By this time, sjq was completely out to lunch so I rebooted and was back in business. I noticed something was wrong about 2 weeks ago when comskip was no longer working.

Brad
Reply With Quote
  #926  
Old 07-11-2010, 03:40 AM
Peter_h Peter_h is offline
Sage Fanatic
  
Join Date: May 2008
Location: Kailua, HI
Posts: 798
Quote:
Originally Posted by bthurber View Post
Same thing happened to me. sjq.sqlite file was 145mb. Loaded up sqlite3.exe and looked at the log table. Had a crazy number of comskip audio panic messages. I ran the command:

delete from log;

By this time, sjq was completely out to lunch so I rebooted and was back in business. I noticed something was wrong about 2 weeks ago when comskip was no longer working.

Brad
I had the same thing happen today. Log in prompt, enter credentials and it just sits there. I restarted the server and it was working again.
Reply With Quote
  #927  
Old 07-16-2010, 09:14 AM
MitchSchaft MitchSchaft is offline
Sage Expert
  
Join Date: Jan 2008
Posts: 717
I have a quick question. Are the client configs stored anywhere that I can see with a text editor?
I reinstalled windows from scratch and started Sage from scratch as well with the latest beta of everything. I forgot to take a screenshot of my SJQ client configs and I forgot how I had them set up .
I do have a backup of the entire Sage directory from a previous install and was hoping I might be able to find something in there.
Reply With Quote
  #928  
Old 07-16-2010, 11:11 AM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
Quote:
Originally Posted by MitchSchaft View Post
I have a quick question. Are the client configs stored anywhere that I can see with a text editor?
I reinstalled windows from scratch and started Sage from scratch as well with the latest beta of everything. I forgot to take a screenshot of my SJQ client configs and I forgot how I had them set up .
I do have a backup of the entire Sage directory from a previous install and was hoping I might be able to find something in there.
All client configs are stored in the SJQ database file (sjq.sqlite). They cannot be viewed with a text editor, but if you know SQL you can download the SQLite CLP program and view the details via SQL.
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #929  
Old 07-16-2010, 02:56 PM
MitchSchaft MitchSchaft is offline
Sage Expert
  
Join Date: Jan 2008
Posts: 717
Cool, thanks!
Reply With Quote
  #930  
Old 07-16-2010, 05:22 PM
MitchSchaft MitchSchaft is offline
Sage Expert
  
Join Date: Jan 2008
Posts: 717
Thanks again, that saved me a lot of research! I used the SQLite Manager firefox plugin.
Reply With Quote
  #931  
Old 07-20-2010, 11:47 AM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
SJQ causing sage to be slow?
I was having an issue lately with Sage and the spinning circle of death. It was getting really bad. I also noticed that it was taking hours to back up my sage tv directory with acronis (it usually took 20 minutes). I was seeing a bunch of thread hanging in sage and was trying to debug that. then I noticed my SJQ db was 78Meg. So I started looking in that direction.

Now I'm using SJQ v3.0.1.704. I only use the file cleaner and for running comskip.

So I disabled Jetty in sage so SJQ wouldn't run and everything was fine again.
My backup times were back to 20minutes or so and now more spinning circle of death.

I renamed the DB so it would create a new on and it still seems to be writing to the log every minute or so. Should it be doing that? This is a supposedly blank db. I'm really missing comskip so I'd like to try to get to the bottom of this.....

Here is the last several line of the log file.

Code:
2010-07-20 13:20:48,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:20:48,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:20:58,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:20:58,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:08,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:08,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:18,577 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:18,577 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:27,077 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:27,077 INFO  [SJQServlet]: Checking client '127.0.0.1': 100 resources free.
2010-07-20 13:21:27,077 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:28,577 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:28,577 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:35,843 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:35,843 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:38,530 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:38,546 INFO  [SJQServlet]: Servlet POST request completed [16ms]
2010-07-20 13:21:43,249 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:21:43,264 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:21:48,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:48,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:21:58,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:21:58,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:08,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:08,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:18,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:18,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:28,577 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:28,577 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:38,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:38,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:22:43,280 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:22:43,296 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:22:48,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:48,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:22:58,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:22:58,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:08,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:08,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:18,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:18,561 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:28,577 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:28,577 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:35,858 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:35,858 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:38,530 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:38,530 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:43,296 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:23:43,311 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:23:48,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:48,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:23:58,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:23:58,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:24:08,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:24:08,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:24:18,561 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:24:18,561 INFO  [SJQServlet]: Servlet POST request completed [15ms]
2010-07-20 13:24:28,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:24:28,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:24:38,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:24:38,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:24:41,921 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:24:41,921 WARN  [Butler]: Tue Jul 20 13:24:41 EDT 2010: SJQ Application Dump
	MediaQueueLoader thread is alive...
		java.lang.Thread.sleep(Native Method)
		com.google.code.sagetvaddons.sjq.server.MediaFileQueueLoader.run(MediaFileQueueLoader.java:97)
		java.lang.Thread.run(Unknown Source)
	SysMsgQueueLoader thread is alive...
		java.lang.Thread.sleep(Native Method)
		com.google.code.sagetvaddons.sjq.server.SystemMessageQueueLoader.run(SystemMessageQueueLoader.java:79)
		java.lang.Thread.run(Unknown Source)
	ClientMonitor thread is alive...
		java.lang.Thread.sleep(Native Method)
		com.google.code.sagetvaddons.sjq.server.ClientMonitor.run(ClientMonitor.java:38)
		java.lang.Thread.run(Unknown Source)
	InteralTaskClient thread is alive...
		java.lang.Thread.sleep(Native Method)
		com.google.code.sagetvaddons.sjq.server.InternalTaskClient.run(InternalTaskClient.java:68)
		java.lang.Thread.run(Unknown Source)
	Most recent LogCleaner thread is dead (this is normal behaviour)!
	Most recent FileCleaner thread is dead (this is normal behaviour)!
	Most recent VacuumCleaner thread is dead (this is normal behaviour)!

2010-07-20 13:24:41,921 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:24:42,593 INFO  [ClientMonitor]: Run completed [0ms]
2010-07-20 13:24:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:24:43,311 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:24:43,327 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:25:38,546 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:25:38,546 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:25:43,327 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:25:43,358 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:26:27,077 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:26:27,077 INFO  [SJQServlet]: Checking client '127.0.0.1': 100 resources free.
2010-07-20 13:26:27,077 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:26:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:26:43,358 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:26:43,374 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:27:38,530 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:27:38,530 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:27:43,374 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:27:43,405 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:28:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:28:43,421 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:28:43,452 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:29:38,514 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:29:38,514 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:29:42,593 INFO  [ClientMonitor]: Run completed [0ms]
2010-07-20 13:29:43,452 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:29:43,483 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:30:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:30:43,483 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:30:43,514 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:31:27,093 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:31:27,093 INFO  [SJQServlet]: Checking client '127.0.0.1': 100 resources free.
2010-07-20 13:31:27,093 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:31:38,499 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:31:38,499 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:31:43,514 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:31:43,530 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:32:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:32:43,530 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:32:43,546 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:33:38,483 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:33:38,483 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:33:43,546 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:33:43,561 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:34:42,593 INFO  [ClientMonitor]: Run completed [0ms]
2010-07-20 13:34:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:34:43,577 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:34:43,593 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:35:38,468 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:35:38,468 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:35:43,593 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:35:43,624 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:36:27,093 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:36:27,093 INFO  [SJQServlet]: Checking client '127.0.0.1': 100 resources free.
2010-07-20 13:36:27,093 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:36:42,624 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:36:43,624 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:36:43,639 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:37:38,452 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:37:38,452 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:37:43,655 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:37:43,686 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:38:43,546 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:38:44,609 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:38:44,625 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:39:39,625 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:39:39,625 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:39:43,515 INFO  [ClientMonitor]: Run completed [0ms]
2010-07-20 13:39:44,625 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:39:44,656 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:40:43,546 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:40:44,656 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:40:44,671 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:41:28,015 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:41:28,015 INFO  [SJQServlet]: Checking client '127.0.0.1': 100 resources free.
2010-07-20 13:41:28,015 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:41:39,359 WARN  [SJQServlet]: All client connections are being accepted and processed, please consider setting up client restrictions in SJQ settings
2010-07-20 13:41:39,359 INFO  [SJQServlet]: Servlet POST request completed [0ms]
2010-07-20 13:41:44,671 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:41:44,703 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
2010-07-20 13:42:43,546 INFO  [InternalTaskClient]: Run completed [0ms]
2010-07-20 13:42:44,703 WARN  [SystemMessageQueueLoader]: Skipping SystemMessageQueueLoader run: ruleset is empty!
2010-07-20 13:42:44,734 WARN  [DataStore]: Thread 'SJQ-SystemMessageQueueLoader' attempted to return a timed out connection!  Dropping connection.
Full log attached...
Attached Files
File Type: zip sjqlog.zip (10.9 KB, 161 views)
Reply With Quote
  #932  
Old 07-20-2010, 01:14 PM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
Looks like your task client is misconfigured. Seems to be trying to connect to the server every 10 seconds and then timing out. Look for the wrapper.log file in the install dir of the task client (assuming you're running the Windows service version). I need stack traces, error messages, etc. But definitely a misconfigured client problem of some kind. DB file is probably so big because it contains all the client stack traces... have a look at the client log within the GUI then if nothing there then look at wrapper.log in the task client install.
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #933  
Old 07-20-2010, 01:38 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Nothing in the client log.. But I'll attach the wrapper log...

the properties file is:
Code:
#Auto generated by SJQC
#Mon Jul 19 19:42:56 EDT 2010
buffer=199000
port=8081
host=localhost
sleep=300
is_ssl=false
My config is:
Code:
COMSKIP 
{
:CPU NORMAL

"\"C:\\Program Files\\SageTV\\SageTV\\STVs\\SageTV3\\Externals\\Comskip_nice.cmd\" \"%c%\""
}
Thanks for looking at this, Slugger!

Jim
Attached Files
File Type: zip wrapper.zip (22.4 KB, 130 views)
Reply With Quote
  #934  
Old 07-20-2010, 01:48 PM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
Is the task client on the same machine as the SJQ server? Doesn't look like it based on the log (connection refused errors all throughout wrapper.log). Ensure the host value is correct in sjqc.properties (if it is localhost change it to 127.0.0.1). Still doesn't explain what's trying to connect every 10 seconds. Might want to look at the Jetty request logs to see what's pinging the SJQ server every 10 seconds. That ping every 10 seconds is the cause of the massive amount of log data.

Are you still using Sage 6? Technically, I don't support Sage 6 anymore (because I don't have a Sage 6 server to test against) so I can't even fix a bug should one be discovered (though I will fix it in SJQ 3.1.x, which is only available for Sage 7).
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #935  
Old 07-20-2010, 01:53 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Quote:
Originally Posted by Slugger View Post
Is the task client on the same machine as the SJQ server?
Yes.. Same Machine...
Quote:
Originally Posted by Slugger View Post
Ensure the host value is correct in sjqc.properties (if it is localhost change it to 127.0.0.1).
Ok.. I'll change it to 127.0.0.1

Quote:
Originally Posted by Slugger View Post
Still doesn't explain what's trying to connect every 10 seconds. Might want to look at the Jetty request logs to see what's pinging the SJQ server every 10 seconds. That ping every 10 seconds is the cause of the massive amount of log data.
I'll look at the logs to see if I can see anything..

Quote:
Originally Posted by Slugger View Post
Are you still using Sage 6? Technically, I don't support Sage 6 anymore (because I don't have a Sage 6 server to test against) so I can't even fix a bug should one be discovered (though I will fix it in SJQ 3.1.x, which is only available for Sage 7).
I haven't found a good time yet to upgrade.. I plan on.. someday... Maybe this will prompt me to do so...

Jim
Reply With Quote
  #936  
Old 07-20-2010, 02:20 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
Here is the jetty request log.. it's an older one.. but I get a ton of these....

Code:
127.0.0.1 -  -  [15/Jul/2010:00:00:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:01:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:01:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:01:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:01:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:02:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:02:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:02:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:02:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:03:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:03:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:03:24 +0000] "GET /sjq/SJQ?proto=4&cmd=pop HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:03:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:03:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:04:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:04:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:04:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:04:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:05:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:05:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:05:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:05:46 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:01 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:16 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:31 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658632&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:41 +0000] "POST /sjq/SJQ?proto=4&cmd=writeLog HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:41 +0000] "POST /sjq/SJQ?proto=4&cmd=writeLog HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:41 +0000] "GET /sjq/SJQ?proto=4&cmd=update&data=%7B%22taskId%22%3A%22COMSKIP%22%2C%22mediaId%22%3A%228658632%22%2C%22cmds%22%3A%5B%5B%22%5C%22C%3A%5C%5CProgram+Files%5C%5CSageTV%5C%5CSageTV%5C%5CSTVs%5C%5CSageTV3%5C%5CExternals%5C%5CComskip_nice.cmd%5C%22+%5C%22%5C%5C%5C%5Ctower%5C%5CTV%5C%5CGhostWhisperer-8443196-0.mpg%5C%22%22%5D%5D%2C%22objType%22%3A%22media%22%2C%22priority%22%3A%220%22%2C%22noRec%22%3A%22%22%2C%22state%22%3A%22DONE%22%2C%22options%22%3A%7B%22MAX%22%3A%22-1%22%2C%22RETURNCODE%22%3A%220.0%22%2C%22NORECORDING%22%3A0%2C%22MAXRUN%22%3A-1%2C%22RESOURCES%22%3A%22100%22%2C%22NOCLIENT%22%3A%22%22%2C%22CPU%22%3A%22NORMAL%22%2C%22OFFDAY%22%3A%22%22%2C%22OFFHOUR%22%3A%22%22%7D%7D HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "GET /sjq/SJQ?proto=4&cmd=pop HTTP/1.1" 200 358 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "POST /sjq/SJQ?proto=4&cmd=writeLog HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "GET /sjq/SJQ?proto=4&cmd=pop HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "GET /sjq/SJQ?proto=4&cmd=update&data=%7B%22taskId%22%3A%22COMSKIP%22%2C%22mediaId%22%3A%228658631%22%2C%22cmds%22%3A%5B%5B%22%5C%22C%3A%5C%5CProgram+Files%5C%5CSageTV%5C%5CSageTV%5C%5CSTVs%5C%5CSageTV3%5C%5CExternals%5C%5CComskip_nice.cmd%5C%22+%5C%22%5C%5C%5C%5Ctower%5C%5CTV%5C%5CFlashpoint-TheFarm-8361473-0.mpg%5C%22%22%5D%5D%2C%22objType%22%3A%22media%22%2C%22priority%22%3A%220%22%2C%22noRec%22%3A%22%22%2C%22state%22%3A%22RUNNING%22%2C%22options%22%3A%7B%22MAX%22%3A%22-1%22%2C%22RETURNCODE%22%3A%220.0%22%2C%22NORECORDING%22%3A0%2C%22MAXRUN%22%3A-1%2C%22RESOURCES%22%3A%22100%22%2C%22NOCLIENT%22%3A%22%22%2C%22CPU%22%3A%22NORMAL%22%2C%22OFFDAY%22%3A%22%22%2C%22OFFHOUR%22%3A%22%22%7D%7D HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "POST /sjq/SJQ?proto=4&cmd=writeLog HTTP/1.1" 200 0 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:42 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:06:57 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:07:12 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:07:27 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:07:42 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:07:57 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:08:12 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:08:27 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:08:42 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:08:57 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
127.0.0.1 -  -  [15/Jul/2010:00:09:12 +0000] "GET /sjq/SJQ?proto=4&cmd=keepAlive&m=8658631&t=COMSKIP&o=media HTTP/1.1" 200 4 "-" "SageTV SJQc/3.0.1.705 Java/1.6.0_20"
It seems like it's from the localhost.
Does this mean anything?
Reply With Quote
  #937  
Old 07-20-2010, 03:02 PM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
That's normal output. Nothing unusual there.
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #938  
Old 07-20-2010, 03:08 PM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
several times a minute??

Is this because I still have a SJQ browser open?

And they show up in the sage log too?

Code:
Tue 7/20 17:05:30.817 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:30.817 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:30.817 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:30.817 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:30.820 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> REQUEST /sjq/SJQ on org.mortbay.jetty.HttpConnection@1e5e28f

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> sessionManager=org.mortbay.jetty.servlet.HashSessionManager@195f463

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:30.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:31.000 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:31.506 [3634776@qtp-14806243-1@377658] (org.mortbay.log) <DEBUG> EOF

Tue 7/20 17:05:33.419 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> REQUEST /sjq/SJQ on org.mortbay.jetty.HttpConnection@1e5e28f

Tue 7/20 17:05:33.419 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> sessionManager=org.mortbay.jetty.servlet.HashSessionManager@195f463

Tue 7/20 17:05:33.419 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:33.419 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:33.419 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:33.420 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:33.421 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8714352&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> REQUEST /sjq/SJQ on org.mortbay.jetty.HttpConnection@38ceb8

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> sessionManager=org.mortbay.jetty.servlet.HashSessionManager@195f463

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:36.507 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:36.509 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636250&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:40.827 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> REQUEST /sjq/SJQ on org.mortbay.jetty.HttpConnection@1c6a2e4

Tue 7/20 17:05:40.828 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> sessionManager=org.mortbay.jetty.servlet.HashSessionManager@195f463

Tue 7/20 17:05:40.828 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:40.828 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:40.828 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:40.828 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:40.832 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=showQ&sid=-1208218517@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:40.996 [3634776@qtp-14806243-1@377658] (org.mortbay.log) <DEBUG> EOF

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> REQUEST /sjq/SJQ on org.mortbay.jetty.HttpConnection@12fc1b3

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> sessionManager=org.mortbay.jetty.servlet.HashSessionManager@195f463

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> session=null

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet=SJQServlet

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> chain=null

Tue 7/20 17:05:45.997 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> servlet holder=SJQServlet

Tue 7/20 17:05:45.998 [3634776@qtp-14806243-1 - /sjq/SJQ?proto=4&cmd=keepAlive&m=8636251&t=COMSKIP&o=media@377658] (org.mortbay.log) <DEBUG> RESPONSE /sjq/SJQ  200

Tue 7/20 17:05:46.509 [3634776@qtp-14806243-1@377658] (org.mortbay.log) <DEBUG> EOF
Reply With Quote
  #939  
Old 07-20-2010, 06:34 PM
Slugger Slugger is offline
SageTVaholic
  
Join Date: Mar 2007
Location: Kingston, ON
Posts: 4,008
It's the keepAlive ops... those are what are polling every 10 seconds. Those happen when SJQ is running a task. The task client polls the server while it's running a task to see if the task has been cancelled. It is normal behaviour.

However, in your sjqc.properties file, change the buffer from 199000 to 66000 (task client restart required after changing this value). That's a known issue, but not the cause of excessive logging. If your SJQ is always running a task then the logs are going to be big. However, 78MB shouldn't be an issue for any modern hardware. If that task that is always running is a comskip, especially on an H264 recording, then that is likely what's bogging down your system. Uninstalling SJQ appears to fix the problem because uninstalling SJQ also stops running comskip on your system. Leaving SJQ installed and active, but removing the queuing up of comskip tasks is likely to achieve the same result (no more system slowdowns).
__________________
Twitter: @ddb_db
Server: Intel i5-4570 Quad Core, 16GB RAM, 1 x 128GB OS SSD (Win7 Pro x64 SP1), 1 x 2TB media drive
Capture: 2 x Colossus
STB Controller: 1 x USB-UIRT
Software:Java 1.7.0_71; SageTV 7.1.9
Clients: 1 x HD300, 2 x HD200, 1 x SageClient, 1 x PlaceShifter
Plugins: Too many to list now...
Reply With Quote
  #940  
Old 07-21-2010, 08:10 AM
jbuszkie's Avatar
jbuszkie jbuszkie is offline
Sage Fanatic
  
Join Date: Aug 2003
Location: Westminster, MA
Posts: 938
I took the localhost client away and I'm using a second machine to finish up the tasks.... It was fine last night and into this AM...

what do people have for their comskip verbose level? I just realized I have mine set to 10 and it's producing a lot of text which I probably don't need in the db.

I'll also change the value to 66000
Reply With Quote
Reply
Page 47 of 68 « First 374546 47 484957 Last »

« Previous Thread | Next Thread »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Sage Job Queue (SJQ) new release notifications Slugger Customization Announcements 3 12-17-2009 09:59 AM
Plugin: Sage Job Queue (SJQ) Slugger SageTV Customizations 991 12-11-2009 03:52 PM
Sage Job Queue Completed tasks problem raffmanlt SageTV Customizations 2 08-18-2009 07:34 PM
Comskip Monitor VS Sage Job Queue SJQ personalt SageTV Customizations 6 03-02-2009 10:27 AM
Plugin: SJQ v1.1.0RC1 Available - Testers Needed Slugger SageTV Customizations 35 04-21-2008 08:12 AM


All times are GMT -6. The time now is 10:00 AM.

Contact Us - SageTV, LLC - Archive - Privacy Statement - Top

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.