Utility: SageTray - SageTV tray application

[ToonGal]

Originally Posted by k10ck3r

Hmm .. I just noticed that there are two flavors that can be downloaded: One uses the legacy TJWS server and the other uses Jetty. Do you know which one you are using?

So far, I'm trying to stay on the legacy Java side. I haven't done anything with Jetty yet, and am waiting until I have my system stable, before I start bleeding edge.

Thanks again, K!

[k10ck3r]

Ok, I just updated my webserver to 2.25 and it seems to be working fine (with SageTv version 6.6.2.11). So, if you are using the latest SageTV/webserver versions, it "should" work.

One thought I have is that perhaps the new server returns a null feed when nothing is scheduled. Do you know if anything is scheduled? If not, could you use the web interface and navigate to the Scheduled Recordings - Upcoming Recordings page. Click on the orange XML button and let me know if anything is returned. If not, then this is the culprit and is something I could probably work around with an updated build. (I would test it myself, but my wife will kill me if I cancel all of her scheduled recordings...). Thanks

If nothing is scheduled, you could also add something to see if SageTray is happy again.

[jreichen]

Originally Posted by k10ck3r

Well, I checked nielm's webserver wiki and it seems like 2.24 is the latest version...

FYI, I updated the wiki to 2.25.

The older TJWS configuration is still supported for those who don't want to change to Jetty yet. However, my builds are done a little different than nielm's were but I tried to make sure the resulting files were compatible.

In addition to the TJWS downloads, there's a new download that can be deployed on Jetty. Jetty deployment is different than TJWS but I was able to preserve compatibility for the existing XML and RSS URLs used by other apps.

[ToonGal]

Originally Posted by k10ck3r

If not, could you use the web interface and navigate to the Scheduled Recordings - Upcoming Recordings page. Click on the orange XML button and let me know if anything is returned. If not, then this is the culprit and is something I could probably work around with an updated build.

Son has this week off school, so haven't had time to get to this until now...

Clicking the orange XML button on "Recording Schedule" has some sort of error. Wish I could be specific, but not sure exactly what it is supposed to do. Here's the actions, after clicking:
- dialog box offering file "recording_schedule.xml"
- clicking save or open create same error message: IE cannot DL RecordingSchedule?xml-yes from sagetv.

Looks like the XML part is not working here. Not sure if that helps, but that might be the issue. I'm going to upgrade back to webserver v2.25 files, since you said it works on your side, when the recordings are done.

I always have lots in my daily / 2 week queue, so that will never be the issue for me

Thanks again for the help, K. Thanks to you too J, for helping me with your webserver work. (I'll be bothering you for Jetty questions soon enough, once this is done / stable.)

UPDATE: Tried the XML button from a different computer, accessing the server. The first info was from the server itself, which is also where I am trying to make SageTray work. Here's the resulting web page:

The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.


--------------------------------------------------------------------------------

XML document must have a top level element. Error processing resource 'http://sagetv:9203/sage/RecordingSchedule?xml=yes'.

[jreichen]

On your first computer, there should be an equals sign between 'xml' and 'yes' in the URL. On the second computer, try either "View Source" or right-clicking on the XML icon and "Save As..." then look at the output that's being produced. It should look something like this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE sageShowInfo PUBLIC "-//NIELM//DTD SAGESHOWINFO XML 1.3//EN" "http://sageplugins.sourceforge.net/nielm_modules/sagexmlinfo/sageshowinfo_1_3.dtd">
<sageShowInfo version="1.3">
    <channelList>
    ...
    </channelList>
    <favoriteList>
    ...
    </favoriteList>
    <showList>
    ...
    </showList>
</sageShowInfo>

[ToonGal]

Originally Posted by jreichen

On your first computer, there should be an equals sign between 'xml' and 'yes' in the URL.

Quite right you are. It is an =, but was a '-' in my typo. Still doesn't work... After that, the dialog failure box says: "IE was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later. Didn't change from yesterday; sorry about the initial typo.

Originally Posted by jreichen

On the second computer, try either "View Source" or right-clicking on the XML icon and "Save As..." then look at the output that's being produced. It should look something like this:

Should. Doesn't. *sigh* It generates a 0 byte file entitled "recording_schedule.xml".

Would it help for me to document the date / size of the JAR file directory? I can do a directory listing and post that if it helps. I'm guessing SageTray is no longer at fault on my server, but rather that I have some incompatibility on some JAR file (or other) along the way.

Thanks for the next step, J. Ready to follow whatever is suggested next.

UPDATE: JAR directory listing, in case useful, to save time:

# Generated on 2009-10-06 14:36:59 by Directory Lister v0.7.2

----------------------------------------------------------------------------------------
c:\Program Files\SageTV\SageTV\JARs\ (28) 3 869 767 2009-10-03 16:30 -----
----------------------------------------------------------------------------------------
activation.jar 54 829 2004-05-11 12:54 -a---
commons-jxpath-1.1.jar 268 794 2006-03-29 10:26 -a---
commons-logging.jar 31 605 2006-03-29 10:26 -a---
commons-logging-api.jar 22 327 2006-03-29 10:26 -a---
df_sageplugins.jar 13 239 2006-06-17 11:36 -a---
df_sageutils.jar 17 477 2008-02-22 17:16 -a---
df_sleep_timer.jar 2 166 2008-02-22 18:16 -a---
gkusnick.sagetv.jar 539 093 2007-12-03 13:35 -a---
jcifs-1.1.6.jar 258 345 2004-12-27 21:44 -a---
jdic.jar 72 906 2005-03-23 10:45 -a---
log4j.jar 358 085 2005-08-29 23:28 -a---
mail.jar 355 030 2005-09-09 15:28 -a---
mailcheck.jar 13 893 2006-05-27 16:21 -a---
mtsa.jar 9 604 2006-05-21 12:53 -a---
mx4j-impl.jar 148 179 2006-03-29 10:26 -a---
mx4j-jmx.jar 261 135 2006-03-29 10:26 -a---
mx4j-remote.jar 167 500 2006-03-29 10:26 -a---
mx4j-tools.jar 491 164 2006-03-29 10:26 -a---
nielm_getrssnews.jar 28 080 2005-10-20 16:00 -a---
nielm_getstatus.jar 7 962 2006-01-24 22:22 -a---
nielm_sageimdb.jar 41 036 2007-02-21 11:50 -a---
nielm_sagemenureader.jar 32 094 2006-10-24 01:57 -a---
nielm_sageutls.jar 14 081 2009-09-11 18:24 -a---
nielm_sagewebserver.jar 377 707 2009-09-18 16:29 -----
nielm_sagexmlinfo.jar 52 380 2009-09-11 18:24 -a---
sbbi-jmx-1.0.jar 89 764 2006-03-29 10:26 -a---
sbbi-upnplib-1.0.3.jar 109 503 2006-05-12 11:28 -a---
servlet.jar 31 789 2005-12-04 15:25 -----

[gplasky]

I wonder if the fact you're running SageTV v5 might be causing some of the issue.

Gerry

[jreichen]

Could you turn on logging and see if there are any errors related to the web server?

[ToonGal]

Originally Posted by jreichen

Could you turn on logging and see if there are any errors related to the web server?

The answer is obviously 'yes'. But...

- How do I "turn it on"? The SageTV one with registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\Common]
"consolewin"=dword:00000001

- How do I identify "errors"? A log I can post, or watch the DOS window looking for something, or other?

Anything else you want me to do, I'm happy to try to help. The webserver is the key to my SageTV happiness. I hope v5 isn't the issue. I might be willing to try to upgrade to v6, but I have so much invested in v5 and not sure how stable / similar to my current setup I can retain with v6 (never mind the financial investment...)

Thanks again J for helping make SageTV as great as it is for me.

[jreichen]

I doubt v5 is the issue. If it is, there's usually a way to fix the code to maintain backward compatibility.

It would probably be best to generate a log file and post it here. To get SageTV to generate a log file:

1. Shut down SageTV
2. Add/set the property debug_logging=TRUE in Sage.properties. Note that TRUE is in all caps. SageTV will create a sagetv_0.txt file in your SageTV installation directory.
3. Start SageTV
4. Browse to the web server and click on the orange XML image that you're having trouble with. Hopefully something helpful will be written to the log file
5. Post the log file here and I'll look at it.

[ToonGal]

Originally Posted by jreichen

It would probably be best to generate a log file and post it here. To get SageTV to generate a log file:
Add/set the property debug=TRUE in Sage.properties.

That's funny. I have the debug log set as 'on' by default. For me, it's been runnign that way with SageTV for 6 years and I just took it as a given by now...

Anyway, in addition to sagetv_0.txt, I also included two DOS screen shots of the real time log turned on by the registry key I had above. It didn't look like the XML button did much on the log, but things did happen in that DOS screen. It's cut off, but since I can't control that, I figured more information can't hurt.

I restarted SageTV so it had the smallest log possible. I clicked the orange XML button three times, because I didn't see much in the log. The DOS window is inclusive in the two pictures, for one XML click cycle.

Let me know if there's anything else that would help. I have left both debugging on for convenience in testing. Thanks again!

PS. Uploaded in .zip format. Any reason they don't let you upload .rar? Doubled the size of the UL. Anyway...

[jreichen]

Thanks, the screenshots show where the problem is. Now just to figure out why it's happening. I don't know why the stack trace wouldn't should up in the log, but I'm glad you thought of turning on the console window.

I'll take a look into the problem when I get a chance - hopefully by this weekend. The problem may be related to a specific show in your schedule so keep an eye on it and see if the problem goes away or if that console window shows an ArrayIndexOutOfBoundsException of something other than 21 (meaning it's failing on a different recording).

[jreichen]

ToonGal,

Your issue looks like it's a bug in a Sage API. I submitted a bug report and asked them to investigate. I'll let you know when I hear back from support.

Jason

[ToonGal]

Originally Posted by jreichen

Your issue looks like it's a bug in a Sage API. I submitted a bug report and asked them to investigate. I'll let you know when I hear back from support.

Thanks for the time and the help, Jason!

Let me know if there's any add'l info I can provide to help out.

[Stuntman]

Originally Posted by k10ck3r

I'll have to look into that. At first glance, it looks like a fairly involved change, but it does look interesting. I'll let you know what I find out.

Count me as one of the new Jetty users... the webserver works great now, but, of course, I can't get the SageTray to work right... any ideas how to configure it to get there??

[jreichen]

Originally Posted by jreichen

ToonGal,

Your issue looks like it's a bug in a Sage API. I submitted a bug report and asked them to investigate. I'll let you know when I hear back from support.

Jason

I didn't have much luck with my first request to support. I followed up a second time and am waiting for another response.

[jreichen]

Originally Posted by Stuntman

Count me as one of the new Jetty users... the webserver works great now, but, of course, I can't get the SageTray to work right... any ideas how to configure it to get there??

Please look back through the problem ToonGal is having and see if you're having the same problem. If not, what version of SageTV are you using? Turn on the debug log and console window like ToonGal did and report any error messages you see when running SageTray and when clicking the XML and RSS links on the Recordings and Recording Schedule pages.

[ToonGal]

Originally Posted by jreichen

I didn't have much luck with my first request to support. I followed up a second time and am waiting for another response.

Thanks Jason!

[jreichen]

Unfortunately Sage is not going to provide a fix for their API in version 5. So I see three options:

1. Upgrade to version 6. If you're planning on doing this soon then I won't bother fixing it. If you want to stay on version 5 then I'll try one of the following two:
2. I can see if there are different APIs for getting a show's users and roles and try creating a fix using them.
3. I can create a fix that would catch the error and not print any of the role information to the xml file when the error happens.

[ToonGal]

Originally Posted by jreichen

Unfortunately Sage is not going to provide a fix for their API in version 5. So I see three options:

1. Upgrade to version 6. If you're planning on doing this soon then I won't bother fixing it. If you want to stay on version 5 then I'll try one of the following two:
2. I can see if there are different APIs for getting a show's users and roles and try creating a fix using them.
3. I can create a fix that would catch the error and not print any of the role information to the xml file when the error happens.

*sigh* Thanks for following up, Jason.

Guess I might consider v6 / Jetty / SageMC and all the new toys, but it really wasn't my plan. Any help for v5 obviously appreciated, but don't knock yourself out for working on obsolete software. I'll pester you enough once I finally do take an upgrade plunge. I was waiting for v7, as last time I paid for v5, Sage changed their upgrade policy, and don't want to miss the boat this time too.

Thanks for finding out it wasn't anything I was doing wrong on my side. I was going crazy debugging a problem that had no solution. Does the API bug affect anything on the webserver, or any other major components? That probably drives my speed to upgrade, as I haven't seen anything else to date.