Plugin: SageTV Web Interface V2 for Jetty

[jreichen]

Originally Posted by rmac321

I know part of the beauty of jetty is that you don't have to stop the jetty server when you install a new app. But, does the Jetty Server need to be running when you install/extract jetty apps?

No. If you turn on SageTV's debug log and enable the DEBUG line in JettyStarter.properties, Jetty will print details about the web apps it's deploying.

[sleonard]

OK, I migrated Nielm's webserver to Jetty and it was a smooth transition. Three things, 1) What about the nielm/webserver lines in the sage.properties file? 2) Hopefully you will find a way to replace the aliases.properties functionality. SageAlert names the extenders. 3) This has more to do with the HD-PVR than Jetty. Since replacing my mpeg2 encoders with HD-PVRs I haven't tried to stream the H.264 files from the webserver but last night I gave it a go. If I try to watch (Local file) from a PC on the LAN it works OK but none of the stream options work. Is VLC unable to transcode these on the fly? Also can it take advantage of multiple cores to do so?

Awesome job, I know it took a lot of hard work and I thank all of you that put in the effort.

S

PS - Is Nielm still around? I haven't seen him post in months.

[mkanet]

jreichen thanks so much for helping. I modified JettyStarter.properties per the Jetty SSL instructions; skipping the Generating an SSL Certificate section. The instructions were very simple. However, I'm not sure if I need to change or how I need to change the lines with:
jetty.ssl.truststore=$(user.home)/.keystore
I just left those lines the same.

(See attached JettyStarter.properties)

Since I wasn't sure where to put the .keystore file I had from the previous webserver version, I put it in both:
C:\Program Files\SageTV\SageTV\jetty\etc & C:\Program Files\SageTV\SageTV folders.

I deleted the webserver folder and the nielm_sagewebserver.jar file. I wasn't sure which other jar files I can delete without breaking other sageTV addons (servlet.jar, nielm_sagexmlinfo.jar, nielm_sagewebserver.jar, nielm_sageutls.jar). Which ones can I delete here safely? Then, I restarted the sageTVservice and sageTV.exe.


** The end result **

1. I now can't get to http://localhost:8380/bmt/ (which I used to before). I just gets stuck on "Waiting for localhost..." in the browser status bar for a while, then returns a blank page.

2. I'm not sure what URL to go to. But I've tried a couple of different ways, and I cant get the new webserver to show up in my web browser:

(Port 8090 is my SSL port specified in JettyStarter.properties
https://localhost:8090/sage/ (doesnt work)
https://localhost:8090 (doesn't work either)

What am I missing? I am CERTAIN I did everything exactly as how I said above; so, hopefully there's something that's very obvious that I'm missing or doing wrong.

-Michael

Originally Posted by jreichen

Check out the Jetty SSL instructions. You can skip the Generating an SSL Certificate section and proceed to the JettyStarter.properties section.

[sleonard]

One more thing.

Idea #1 - Simplest:

The URL http://localhost:8080/ currently opens a 404 error page with ugly links to the known contexts. It would be nice if this was a formatted page (that looks nice in both mobile and full browsers) with proper links to all of the installed apps (Mobile site, Full site, SageAlert, etc.) Then you could use a single URL and still get to where you want to go.

Idea #2 - The URL http://localhost:8080/ has a browser check and redirects you to the appropriate site (full or mobile.) The links to other installed apps could be added to both the full and mobile versions.

S

[jreichen]

sleonard and mkanet,

I don't have any time the next couple days to research your questions. They're going to have to wait unless somebody else can answer them, sorry.

A couple things I can say quickly: delete servlet.jar and the url has not changed https://localhost:8090/sage/Home.

So far there have been a lot of good questions (and a lot of success!) that will help me put together a wiki to help users get it running.

[mkanet]

Thanks jreichen for replying back. I'll wait until youre ready to help. But, please dont forget about me. All the information is there in case someone else is kind enough to give it a shot and help. I gave it my best shot with the information given. It probably didnt help that I was trying to migrate over SSL capability as well.

Originally Posted by jreichen

sleonard and mkanet,

I don't have any time the next couple days to research your questions. They're going to have to wait unless somebody else can answer them, sorry.

A couple things I can say quickly: delete servlet.jar and the url has not changed https://localhost:8090/sage/Home.

So far there have been a lot of good questions (and a lot of success!) that will help me put together a wiki to help users get it running.

[rmac321]

Originally Posted by sleonard

One more thing.
The URL http://localhost:8080/ currently opens a 404 error page with ugly links to the known contexts.
S

Interesting. That is different than what I'm getting. When I go to:
http://sageserver:8080/
I get

HTTP ERROR: 403
FORBIDDEN
RequestURI=/
Powered by Jetty://

Perhaps the difference will be a clue to why I can't get the jetty version to work.

Here is what gets added to my sagetv_0.txt log when I enter
http://sageserver:8080/
and then
http://sageserver:8080/sageHome/

Tue 9/22 21:49:19.043 [btpool0-3 - /@1930ebb] (org.mortbay.log) <DEBUG> REQUEST / on org.mortbay.jetty.HttpConnection@1cd6bf
Tue 9/22 21:49:19.044 [btpool0-3 - /@1930ebb] (org.mortbay.log) <DEBUG> RESPONSE /  403
Tue 9/22 21:49:24.429 [btpool0-3 - /sage/Home@1930ebb] (org.mortbay.log) <DEBUG> REQUEST /sage/Home on org.mortbay.jetty.HttpConnection@1cd6bf
Tue 9/22 21:49:24.430 [btpool0-3 - /sage/Home@1930ebb] (org.mortbay.log) <DEBUG> RESPONSE /sage/Home  404

Edit: Problem Solved! I was still running v1.5 of the Jetty Starter. I wasn't subscribed to that thread and my other jetty apps were working fine, so I missed the 1.6 upgrade. Upgraded Jetty Starter to v1.6 and all is good.
Thanks jreichen for Jetty Starter and the new Jetty version of the Web Interface.
Thanks Brent for the upgrade instructions.
Thanks nielm for the Web User Interface.

[Taddeusz]

Maybe this is a dumb question... I don't know. I've moved over to the jetty version. How do you set up a username and password for jetty? I see the realms.properties file but how do you enable using that user and password?

[Fuzzy]

Originally Posted by Taddeusz

Maybe this is a dumb question... I don't know. I've moved over to the jetty version. How do you set up a username and password for jetty? I see the realms.properties file but how do you enable using that user and password?

All jetty interfaces (new WebUI, BMT, SJQ, etc) use the same login info. They are setup in the jetty/etc/real.properties file. The format is actually :

username: password,group

by default, the interfaces all use the 'user' group, so an entry would be

Fuzzy: FuzzysPW,user

then restart the server, and it should require using that login.

[Taddeusz]

Strange, the SageTV web interface needs the password I set but BMT doesn't for some reason.

I like having it all in one server though. Now with the addition of the PlayOn feed updater I still have two web servers on my SageTV server rather than the three I would have. Now if only it would work with Jetty.

[Fuzzy]

Originally Posted by Taddeusz

Strange, the SageTV web interface needs the password I set but BMT doesn't for some reason.

I like having it all in one server though. Now with the addition of the PlayOn feed updater I still have two web servers on my SageTV server rather than the three I would have. Now if only it would work with Jetty.

rel;ax.. it's been out for what, 2 days? hehe... I think eventually, for standardization sake, most web based interfaces in sage should move to jetty.. that said, I think things like the feed updated really shouldn't reside in the web anyways, and just be in an stvi.

[nstocke]

I just installed 2.25 and it seems to work fine with Firefox. However when using Google Chrome everytime I click on something in the WebUI it wants me to authenticate with my UserID and Password. I'm the first to admit I could do something wrong. Any suggestions appreciated.

I ran the installer found above. Is that enough to get it running on Jetty or do I need to do some additional install & config?

[toricred]

Something's not right about that. I use Chrome and it works beautifully.

[jreichen]

Originally Posted by sleonard

OK, I migrated Nielm's webserver to Jetty and it was a smooth transition.

That's good to hear, I'll try to address each of your questions below.

Originally Posted by sleonard

1) What about the nielm/webserver lines in the sage.properties file?

I don't have a complete breakdown, I guess it needs to go onto the growing list of things to be documented on the wiki. Jetty doesn't need them but they can be broken down into categories: some are no longer used (e.g. nielm/webserver/port), some are still used but if deleted a default will be used (e.g. nielm/webserver/rss_ttl_mins - these are used in nielm's servlets and might be recreated), and some aren't used but you might need to remember their values to use them elsewhere (e.g. the location of the keystore file in nielm/webserver/ssl_args needs to be entered into JettyStarter.properties when transferring SSL settings).

Originally Posted by sleonard

2) Hopefully you will find a way to replace the aliases.properties functionality. SageAlert names the extenders.

Aliases.properties was used by the old embedded server to map URLs to file locations on the server. It doesn't have anything to do with SageAlert's client aliases, those are stored in SageAlert's database.

Originally Posted by sleonard

3) This has more to do with the HD-PVR than Jetty. Since replacing my mpeg2 encoders with HD-PVRs I haven't tried to stream the H.264 files from the webserver but last night I gave it a go. If I try to watch (Local file) from a PC on the LAN it works OK but none of the stream options work. Is VLC unable to transcode these on the fly? Also can it take advantage of multiple cores to do so?

I don't know. I hate to be so brief about it but VLC is too unstable for me so I don't use it.

Originally Posted by sleonard

PS - Is Nielm still around? I haven't seen him post in months.

I haven't heard from him in a while either. Last I knew he was still a happy Sage user but didn't have time to write plugins anymore.

[jreichen]

Originally Posted by mkanet

Thanks jreichen for replying back. I'll wait until youre ready to help. But, please dont forget about me.

OK you're next Sorry to leave you hanging, I'm sure glad that week's over with!

It looks like Jetty's not pointing to your .keystore file. At the bottom of JettyStarter.properties, it's using the default value of $(user.home)/.keystore. This means it's looking under the user's home directory (that's where Java's keytool command puts it by default) for that file (C:\Documents and Settings\.... in Windows) but you put it in a different location.

Also, don't forget to remove the servlet.jar from the JARs folder.

After that, restart SageTV, then see if it works. If not, turn on SageTV's debug logging and enable the DEBUG line in JettyStarter.properties. See if the log has any error messages about Jetty.

[jreichen]

Originally Posted by Taddeusz

Strange, the SageTV web interface needs the password I set but BMT doesn't for some reason.

Security is enabled on an app-by-app basis. I'd like to standardize it if it's possible with Jetty, but for now that's how it works. BMT doesn't currently enable security but I think stuckless is considering changing that in the next release. See the BMT thread for more info.

Originally Posted by Taddeusz

I like having it all in one server though. Now with the addition of the PlayOn feed updater I still have two web servers on my SageTV server rather than the three I would have. Now if only it would work with Jetty.

I don't know much about PlayOn (esp. since I'm on Linux). If you want to follow up about this topic I'd suggest posting over in the Jetty Starter support thread and we can discuss it there.

[jreichen]

Originally Posted by nstocke

I just installed 2.25 and it seems to work fine with Firefox. However when using Google Chrome everytime I click on something in the WebUI it wants me to authenticate with my UserID and Password. I'm the first to admit I could do something wrong. Any suggestions appreciated.

I ran the installer found above. Is that enough to get it running on Jetty or do I need to do some additional install & config?

The installer will not run the web interface in Jetty. That will install it with its own embedded server that must be on a different port than Jetty. To run in Jetty you need to remove the one you just installed then download the zip file that's built for running it on Jetty and extract it to the SageTV directory.

Get that working before trying to fix the Chrome issue. I'm able to run it fine on Chrome.

[mkanet]

Thanks for getting back to me. I cant wait to get this going!

Since there were no examples on how to change the location of the .keystore file in the jettystarter.properties, I tried my best to change it to: C:\Program Files\SageTV\SageTV which is the correct location.

I changed the line to:
jetty.ssl.keystore=C\:\\Program Files\\SageTV\\SageTV\\.keystore

However, that results in the following:

When I type: http://localhost:8380/bmt/
It sits there waiting for reply with a white screen and eventually times out.

When I type: https://localhost:8380/bmt/
Immediately, the browser returns with a: "Secure Connection failedAn error occurred during a connection to localhost:8380. SSL received a record that exceeded the maximum permissible length."

When I type: https://localhost:8090
The browser returns with a: "Failed to connect"... which is what I get when there's nothing detected at all.

I already included a copy of my jettystarter.properties file in my last post. I have the secure port set at 8090 and default port set at 8380. However, maybe you can make sure I have that set right.

Thanks,
-MKANET

Originally Posted by jreichen

OK you're next Sorry to leave you hanging, I'm sure glad that week's over with!

It looks like Jetty's not pointing to your .keystore file. At the bottom of JettyStarter.properties, it's using the default value of $(user.home)/.keystore. This means it's looking under the user's home directory (that's where Java's keytool command puts it by default) for that file (C:\Documents and Settings\.... in Windows) but you put it in a different location.

Also, don't forget to remove the servlet.jar from the JARs folder.

After that, restart SageTV, then see if it works. If not, turn on SageTV's debug logging and enable the DEBUG line in JettyStarter.properties. See if the log has any error messages about Jetty.

[jreichen]

Let's forget about the SSL for now and get a normal connection to work. To do that, remove jetty-ssl.xml from the jetty.configfiles line in JettyStarter.properties.

Make sure SageTV is stopped, then delete all the directories (but not the war files) in jetty/webapps. Jetty will recreate the directories from the war files when it starts.

Enable SageTV debug logging and enable the DEBUG line in JettyStarter.properties.

Start up SageTV and try to go to http://server:8380/bmt. If it fails, look in the SageTV debug log as well as the most recent file in the jetty/logs folder.

I noticed you've been using 'localhost' in the URL, you might try the machine's IP instead.

[sleonard]

Two weeks ago I added the Jetty webserver, SageAlerts and the Mobile web app to my Sage server. I got everything up and running OK and had no problems. Then, about a week later, the port for Nielms webserver to Jetty was released so I followed the steps to migrate that to Jetty as well. It seemed to go smoothly and was working OK but every night after I got home from work the Sage service was locked up. Clients and extenders could not connect, I could not connect to any of the web apps, and scheduled recordings were not starting. In addition, I could not even restart or even just stop the Sage service from services.msc without an error that the Sage service could not be properly stopped. I was forced to reboot the whole server to get it working again.

The first night it happened I assumed it was due to my trying to stream recordings from Nielms links using the required VLC server so I gave up on that. I did continue to use the Nielm web app from work and Sage continued to be in a locked up state when I returned home from work.

Last night I removed the sagex.jetty.starter.Main entry in the load_at_startup_runnable_classes= line of Sage.properties and so for Sage is continuing to run OK. If it continues to run OK for another day I'm going to re-enable Jetty but remove the Nielm web app since all the problems started after that was installed.

I'll post the results as I get them.

S