Wanted: Developer for Web Interface Mobile

[Brent]

Originally Posted by jreichen

Looks good, Brent..

Could you check my steps #5 and #6 to see if I have those listed correctly?

Thanks for the help - I meant to get started on this earlier this week, but the HD-PVR work took a bit more than I had expected...

[matt91]

What about the requirement for Nielms www server?

Are the jar files from nielm's webserver in the JARs folder? Right now it depends on those. I forgot to mention that.

It would seem that should be listed as either a prerequisite, or a discrete step in Brent's list.

Matt

[Brent]

Originally Posted by matt91

What about the requirement for Nielms www server?
It would seem that should be listed as either a prerequisite, or a discrete step in Brent's list.

Matt

Matt,
I added the requirement to have Neilm's Web User Interface installed and running. I think as long as you install it as per Nielm's instructions you're good to go.

[jreichen]

Originally Posted by Brent

Could you check my steps #5 and #6 to see if I have those listed correctly?

Thanks for the help - I meant to get started on this earlier this week, but the HD-PVR work took a bit more than I had expected...

#5 - The filename is JettyStarter.properties. With 1.0.02, the jetty.configfiles property shouldn't need to be modified. And just remove the quotes from the jetty.logs property. If those don't work, I have some more work to do.

#6 - The properties file is Sage.properties. I'm sure you knew that but it wouldn't hurt to give the actual name. Also, it would be clearer to state that the value is being added to the value of the load_at_startup_runnable_classes key (rather than changing one to the other).

Matt, thanks for catching the jar dependency.

[LehighBri]

Originally Posted by jreichen

I've seen that if I try accessing the page while Jetty is extracting the war. Usually waiting a few seconds and then refreshing fixes it. That doesn't seem to be the case here, though.

Is there anything in sagetv_0.txt log?

I don't see anything out of the ordinary when I search the log. I searched for jetty and copied my sagetv_0.txt log below:

Fri 6/6 18:09:36.320 Loading startup runnable:net.sf.sageplugins.jetty.starter.Main
Fri 6/6 18:09:36.321 Loaded startup runnable:net.sf.sageplugins.jetty.starter.Main
Fri 6/6 18:09:36.323 JettyStarter: Starting Jetty
Fri 6/6 18:09:36.324 Starting webserver with args: [-p, 8888, -root, webserver, -t, throttles.properties, -s, servlets.properties, -r, realms.properties, -a, aliases.properties, -nohup]
Fri 6/6 18:09:36.360 JettyStarter properties
Fri 6/6 18:09:36.360 -- listing properties --
Fri 6/6 18:09:36.360 jetty.logs="C:\Program Files\SageTV\SageTV\jetty...
Fri 6/6 18:09:36.361 jetty.configfiles="C:\Program Files\SageTV\SageTV\jetty...
Fri 6/6 18:09:36.361 jetty.home=C:\Program Files\SageTV\SageTV\jetty
Fri 6/6 18:09:36.362 Starting Jetty from the following configuration files: 'C:\Program Files\SageTV\SageTV\jetty/etc/jetty.xml'
Fri 6/6 18:09:36.431 Acme httpd BRI-HTPC:8888 listening.

[LehighBri]

Ignore my previous post... I got so frustrated that I started with a new fresh JettyStarter.properties file and didn't modify it at all. I started Sage and it now seems to work! With no changes to that properties file... very weird. The properties are below:

#jetty.home=jetty
#jetty.configfiles="$(jetty.home)/etc/jetty.xml" "$(jetty.home)/etc/jetty-ssl.xml"
jetty.configfiles="$(jetty.home)/etc/jetty.xml"
jetty.logs=logs
#jetty.restart.allow=true
#jetty.restart.port=8081
#jetty.restart.bindaddress=127.0.0.1

[Brent]

Hmm. Not working so I'm doing something wrong. I'm following the procedures I listed in my earlier post with the exceptions of the following points you made:

Originally Posted by jreichen

#5 - The filename is JettyStarter.properties. With 1.0.02, the jetty.configfiles property shouldn't need to be modified. And just remove the quotes from the jetty.logs property. If those don't work, I have some more work to do.

I opened up jettystarter.properties and made only one change. I removed the quotes from the jetty.logs property. Should I also remove it from the config property? Any other changes needed in jettystarter.properties?


I don't know what else I'm missing, but the sagetv properties file doesn't seem to help me and it doesn't seem to be creating anything in jetty/logs either. Going to sleep and will try some more tomorrow.

[jreichen]

The instructions in your earlier post look fine. Does sagetv_0.txt have any errors?

Those are the only two properties used in the file right now. The jetty.configfiles property needs the quotes because the path has spaces in Windows, and there could be multiple files specified in that property. Let's try a couple things in JettyStarter.properties:

1. Change the jetty.logs property to this:

   jetty.logs=logs

   Restart Sage and see if that fixes it. Check sagetv_0.txt if it still doesn't work.
2. If that didn't fix it, try modifying both settings like Rick did in post #15. Restart Sage again and check the log.

Unfortunately the logs generated in the jetty.logs folder are only request logs. They're not very useful for troubleshooting. I need to do some more research on that.

[Brent]

Originally Posted by jreichen

The instructions in your earlier post look fine. Does sagetv_0.txt have any errors?

Those are the only two properties used in the file right now. The jetty.configfiles property needs the quotes because the path has spaces in Windows, and there could be multiple files specified in that property. Let's try a couple things in JettyStarter.properties:

1. Change the jetty.logs property to this:

   jetty.logs=logs

   Restart Sage and see if that fixes it. Check sagetv_0.txt if it still doesn't work.

That didn't work. Nothing in the jetty/log so here's what I found in the sagetv log:

Sat 6/7 7:27:48.183 Loading startup runnable:net.sf.sageplugins.jetty.starter.Main
Sat 6/7 7:27:48.192 RecordingXmlGenerator: Started RecordingXmlGenerator thread version 1.1 using SageXML version 1.3
Sat 6/7 7:27:48.194 Starting webserver with args: [-p, 8129, -root, webserver, -t, throttles.properties, -s, servlets.properties, -r, realms.properties, -a, aliases.properties, -nohup]
Sat 6/7 7:27:48.203 Loaded startup runnable:net.sf.sageplugins.jetty.starter.Main
Sat 6/7 7:27:48.265 JettyStarter: Starting Jetty
Sat 6/7 7:27:48.266 RecordingXmlGenerator: Monitoring recordings every 86400 seconds
Sat 6/7 7:27:48.270 JettyStarter properties
Sat 6/7 7:27:48.270 -- listing properties --
Sat 6/7 7:27:48.271 jetty.logs=logs
Sat 6/7 7:27:48.271 jetty.configfiles="C:\Program Files\SageTV\SageTV\jetty...
Sat 6/7 7:27:48.271 jetty.home=C:\Program Files\SageTV\SageTV\jetty
Sat 6/7 7:27:48.272 RecordingXmlGenerator: Updating XML files for recordings
Sat 6/7 7:27:48.296 Starting Jetty from the following configuration files: 'C:\Program Files\SageTV\SageTV\jetty/etc/jetty.xml'

I've tried with the changes in #15 as well with the same results.

Just to be sure I'm not messing the port thing up. I changed the port to 8129 which is the same port I use for nielm's web server. Is that the right thing to do?

[LehighBri]

Originally Posted by Brent

Just to be sure I'm not messing the port thing up. I changed the port to 8129 which is the same port I use for nielm's web server. Is that the right thing to do?

I believe it needs to be set up on a different port from nielm's server. They are two seperate web servers and you can't have them listening on the same port.

EDIT: A way to tell if the server is listening on the port you designate is go to the command prompt and use the "netstat -a" command to see what ports are being used. If it's working properly, you should see both your nielm web server and jetty ports on the list.

[Brent]

Originally Posted by LehighBri

I believe it needs to be set up on a different port from nielm's server. They are two seperate web servers and you can't have them listening on the same port.

That was it - I was just being stupid. Thanks for the tip!!!

[Sparhawk6]

I'm testing out the mobile interface as per Brent's nice instructions. It looks pretty good!

Few things in my wishlist:
- Being able to fast forward to other days faster in the Listings section.
- Having all the info shown to stream the show to the phone, (you know, how it looks on the web interface normally...the different bitrates, etc.)

I'm loving it so far. Good work!

[Sparhawk6]

By the way, is anyone able to see this using Opera Mini 4.1? For some reason, Opera Mini won't load up this mobile version, and it won't load up the normal web interface either. It just sits there at "processing" and then times out.

[Brent]

This is working good for me inside my home network, but I can't access outside of the network across the internet. Other than forward the port I chose for this is there anything else I should be doing?

[Sparhawk6]

You have the correct port typed in the web address?

[Brent]

Originally Posted by Sparhawk6

You have the correct port typed in the web address?

Yes, I can access from my home browser just fine as long as I use localhost, but when I use the ip address like I would from a remote location it won't work.

[jreichen]

Originally Posted by Brent

This is working good for me inside my home network, but I can't access outside of the network across the internet. Other than forward the port I chose for this is there anything else I should be doing?

You shouldn't need to do anything else. I am able to access it from the outside.

Originally Posted by Brent

Yes, I can access from my home browser just fine as long as I use localhost, but when I use the ip address like I would from a remote location it won't work.

What does your jetty.host setting in jetty.xml have? Here is mine.

<Set name="host"><SystemProperty name="jetty.host" /></Set>

I think there have been reports in nielm's webserver forum about people not being able to access the webserver using the external IP from within the network. Apparently some routers don't let you do that.

Can you access it from your phone?

[jreichen]

Can someone using Windows just remove the quotes from the jetty.logs setting in JettyStarter.properties file and verify the server still works and there aren't any errors in sagetv_0.txt? SageTV will need to be restarted. Thanks!

jetty.logs=$(jetty.home)/logs

[Sparhawk6]

Originally Posted by jreichen

Can someone using Windows just remove the quotes from the jetty.logs setting in JettyStarter.properties file and verify the server still works and there aren't any errors in sagetv_0.txt? SageTV will need to be restarted. Thanks!

jetty.logs=$(jetty.home)/logs

There weren't any quotes in mine when I looked at it. It just read

jetty.logs=logs

[Brent]

Got mine working across the internet finally. Had messed up my port forwarding while troubleshooting - all is great now. I really like the mobile pages you've made here - looks great on my blackberry curve. Excellent job
I also agree with Rickw's suggestion:

Originally Posted by rickw

I think you've done a good job of formatting the displays for a mobile browser. My only suggestion right now is related to the guide listing. There needs to be some method for jumping to a specific date and time slot. For example it's morning right now, but I'd like to see the primetime listing. It takes a while to "Next>" through the entire day.

By the way, I've tried it with the log property set as this:

jetty.logs=logs

and as this (without the quotes from the original file):

jetty.logs=$(jetty.home)/logs

Both ways work fine for me.