Jetty 9 for SageTV 9

[stuckless]

Originally Posted by benjamintm

I don't see anything in the log that tells me why the sage web interface isn't loading. There are references to plugins being in a failed state, but that doesn't seem to reflect the actual status of the plug in. I've attached the log for your review.


I have restarted both the jetty service, the SageTV service, and the entire server, but the web interface still doesn't load.

Ben

There is a section showing the webserver is failing...

Fri 1/13 21:32:59.887 [SageTV@33ca26] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/nielm_sagewebserver.war to C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\nielm_sagewebserver\webapp
Fri 1/13 21:33:00.297 [SageTV@33ca26] ::WARN:  failed Groovy
Fri 1/13 21:33:00.303 [SageTV@33ca26] ::WARN:  failed GspHandler
Fri 1/13 21:33:00.403 [SageTV@33ca26] ::WARN:  Failed startup of context org.mortbay.jetty.webapp.WebAppContext@73c7df{/sage,C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/nielm_sagewebserver.war}
Fri 1/13 21:33:00.470 [SageTV@33ca26] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/MediaStreaming.war to C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\MediaStreaming\webapp

It doesn't tell us why, but I think it's because of the failed dependencies. In your plugin list is groovy marked as "failed"? I'm see a large list of "Failed" plugins in the log and I'm wondering if all related.

[benjamintm]

Groovy appears to be installed and not in a fail state. Everything else appears to be working as expected. The only installed plugin that is marked as "failed" was the "sagetv-addons License Server", which I uninstalled and reinstalled and now it shows as enabled.

If I want to uninstall and reinstall SageTV9, I just need to back up my wiz.bin and sage.properties, correct? Or will the plugin information be maintained?

Thanks,
Ben

[Narflex]

You should probably take a look at the jetty log files, they'll likely tell you what went wrong. I don't think reinstalling SageTV is going to do much to fix your problem since it's plugin related.

[benjamintm]

Aside from hundreds of queries from SageTray (the 127.0.0.1 queries), the only thing showing up in my attempts from my laptop (see sample below). Is there a verbose debugging option for jetty?

127.0.0.1 - - [14/Jan/2017:04:19:05 +0000] "POST /sage/Home HTTP/1.1" 503 1297 "-" "-"
192.168.86.50 - - [14/Jan/2017:04:34:31 +0000] "GET /sage/ HTTP/1.1" 503 1293 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0"
192.168.86.50 - - [14/Jan/2017:04:34:31 +0000] "GET /favicon.ico HTTP/1.1" 404 1279 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0"

[stuckless]

Originally Posted by benjamintm

Aside from hundreds of queries from SageTray (the 127.0.0.1 queries), the only thing showing up in my attempts from my laptop (see sample below). Is there a verbose debugging option for jetty?

Jetty logs are in sagetv_0.txt and in jetty/logs/ (not sure about the second one, but I think there is separate jetty log in the jetty dir).

[benjamintm]

I cleared out the logs and restarted SageTV. Attached you will find the logs. The jetty logs don't contain much, other then an attempt by a local client trying to connect (probably SageTray). I did note in the sage logs the following:

Sat 1/28 11:57:56.998 [SageTV@1dbe6fa] ::INFO: Started SelectChannelConnector@0.0.0.0:8080
Sat 1/28 11:57:57.000 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.000 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.000 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.001 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.001 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.001 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.001 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.002 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.002 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.002 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.002 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.002 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.003 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.003 [SageTV@1dbe6fa] ::INFO: Multiple exceptions
Sat 1/28 11:57:57.003 [SageTV@1dbe6fa] ::INFO: Error starting web application SageTV Web Interface
Sat 1/28 11:57:57.003 [SageTV@1dbe6fa] ::INFO: Multiple exceptions

I can't find an output for the exceptions though. Thoughts?

Thanks,
Ben

[Narflex]

You may want to try increasing the logging level for Jetty (not that I know how to do that).