SJQ opening log problem

[raffmanlt]

SJQ hangs cpu at max when trying to open the server log file, I think it does this on other files as well but right now it is doing that every time on the server one. It will eventually open but sagetvservice stays at 99-100%, extenders will play but pause, then skip ahead. It normally stays this way unless I restart computer or restart sagetvservice. Then as long as I do not try to do anything in sjq I am ok except lately have been haveing an issue with the colors being off. I found one article that mentioned using snapshot 280 or 283 to fix log issues. I could not find that but did try the sjq 2.1.5.492 snapshot and it did not help.

I am using windows xp and orig was on the sjq 2.1.4.466 build.

[Slugger]

What makes you say it's having problems opening the log file? Do you have error messages or exception dumps from Jetty? Log entries in the SJQ logs? Out of curiosity, are your Sage media files stored on a network drive?

Also, keep messages about SJQ in the SJQ thread - I get email notifications of new posts in that thread and will definitely see your message. I just happened to notice this thread by accident. If you want a single thread of discussion for your issue to avoid clutter/noise then consider posting a new thread in the project Google Group (see end of user guide for details). I also get email notifications of posts to that Google Group.

[raffmanlt]

I think it is the log file causing it because it only hangs as far as I know when I click on the server log file, and it is doing it every time and it might take 15 minutes to open it. When I first starting using SJQ it had no problem opening the logs. However sometimes the completed logs section and the failed log section as well as the active log showed nothing but said it was complete loading. The other reasons I think it may be that is when I managed to get to where I could click on the clear log it flashed an error trying to do so. It disappeared b4 I had time to read it but think it was error 500.

I went back just now to check it once again in hopes of actually being able to scroll to the bottom of the log file. Wouldn't you know now that I finally opened a thread it is working ok now and the log has been cleared, was very little in it. Perhaps when I changed it to clear log every day instead of once a week it was able to fix itself.?

ok got you on the google post, was not sure whether to go ahead and reply to this here or do a duplicate over there?

[Slugger]

Let's just wrap this thread up and leave it at that. Older versions of SJQ logged excessive amounts of data, which could cause the symptoms you've been seeing. I don't remember if build 466 was affected by that, but I do know that any recent build (492, for example) should have the fix that keeps the log data reasonably sized in the database. The fact that the db has cleaned itself up after upgrading to 492 means you should be good to go now.

This thread is dead... keep SJQ messages in the SJQ thread here or (actually preferred) move to the Google Group.

(In case someone wonders why I make this request, it's because I'm subscribed to the SJQ thread linked to on this site and I'm also subscribed to the Google Group meaning that I'll definitely see messages about SJQ posted to either location. Starting your own thread on this site is a crap shoot as to whether or not I'll actually see it.)