not working, not sure how to troubleshoot

[thatbradguy]

i just installed the jetty plugin and upgraded to sre2, however i'm
getting a "connection timeout" error when i try to connect to the sre
url. i've repeated the installation instructions for both plugins, and
got the same result. i'm not sure how to troubleshoot the problem.

how can i test to make sure jetty is running correctly?

if it is running correctly, how can i find out why it's not loading
sre2?

thanks.

[Derek Battams]

1) Did you add the jetty class to the load_at_startup_runnable_classes
setting in Sage.properties? The class to be added is:
net.sf.sageplugins.jetty.starter.Main

1a) If so, did you make the changes after first stopping SageTV? You
can only edit Sage.properties when SageTV has been stopped.

1b) If you also have Niel's web server plugin installed did you change
the default port for the jetty plugin? By default jetty also uses
port 8080, which is the same as the web server plugin and will cause a
conflict. Edit JettyStarter.properties and modify the "jetty.port"
setting (be sure to remove the leading # character from the line).
Follow step 5 of the jetty installation procedure:
http://tools.assembla.com/sageplugins/wiki/JettyInstall

Once that's all done then restart SageTV. Test the jetty installation
by going to the URL http://<server_ip>:<jetty_port>/

If you're server's IP is 192.168.0.1 and you setup jetty to run on
port 8000 then the URL to visit is http://192.168.0.1:8000/

Be sure this loads something before trying to install SRE. You should
get an error message saying something like "No contexts on this server
matched... Contexts known to this server are...". If you get that
error then jetty is running and you can proceed to installing SRE. If
you're getting this message from jetty and you've installed SRE, but
SRE is not loading then let me know and we can dig into
troubleshooting that. But we first need to know that you've got the
jetty plugin installed, setup, and running properly as it's the base
requirement for everything else.

[brad simmons]

i did all those things, and did them again, and double checked everything.

here's my sage.properties file line:
load_at_startup_runnable_classes=net.sf.sageplugins.webserver.StartServer;net.sf.sageplugins.jetty.starter.Main

i do have nielm's webserver working properly, and changed the
jettystarter.properties file to run on port 8000, but i'm still
getting a connection timeout. so i guess it is an issue with jetty?

> --~--~---------~--~----~------------~-------~--~----~

[Derek Battams]

Yes, it sounds like a problem with jetty.  If you can't get the initial url to load then that means jetty isn't running so you need to get jetty running first.  Stop sage, enable debug logging, restart sage and watch the output as jetty loads - that should give you the info you need if there are indeed problems loading jetty.