What am I overlooking? Error 503

[MyMediaSmartHom]

Hello,
Been trying to install Metadata Tools for SageTV Web Interface all evening without any luck. Have just went back to a fresh install and made this the first plugin before any others. I've been through the forums trying to find answer all night to this problem. Running SageTV 7 latest beta on WHS server with HD300. Plugin is installed fine. Trying to log on via web browser http://myserver:8080/bmt/ and presented with the Error 503 message. Problem accessing /bmt/. Reason: SERVICE_UNAVAILABLE
Seems i'm over looking something really simple but i'm tired and weary and not quiting until i figure it out. Any help would be appreciated.

Thanks,
William

[robogeek]

You would likely get that error if the BMT jetty .war file doesn't get deployed properly. Why it didn't get deployed properly would probably require additional logs. Enable SageTV debug logging on the SageTV server and restart SageTV, try to access the BMT web page, and then post the sagetv_0.txt debug log file that is located in the SageTV directory. I can't remember if any (or all) jetty web server core logging goes into the SageTV debug log or if it has it's own file, but I'm certain there is a setting somewhere that will allow you to increase the level of logging done by jetty that might make it easier to see exactly what is failing if it's a deployment problem.

It could be a missing dependency or a missing .jar file that is causing a plugin or dependency to fail to load. If this is the case, the SageTV debug log would have this information...if you know what to look for.

[stuckless]

I have a couple of questions...

1. What version of SageTV and what version of BMT?
2. The request log, is that the jetty request log?

from the phoenix log, it does appear the phoenix was loaded ok.

If you are installing bmt on sage7, then make sure that you have installed the Metadata Tools Web UI, which will force install jetty, bmt, pheonix, sagex-apis.

If you are installing sage6, then make sure that jetty has been fully configured and you can actually get to the jetty server.. then install the bmt files. (a restart is request after any bmt update)

Make sure that you DO NOT have another web server running on port 8080 (jetty uses port 8080 by default)

A 503, usually indicates that the program request ran into an unexpected error... ie, ie found the page, tried to execute the page, but then it just died. This probably means that you are hitting the right server. It may be a jar file issue.

could you send me the sagetv_0.txt log file as well?

[MyMediaSmartHom]

Hello,
Well I got back to try again. Read your posts and couldn't find the log file and realized logging was turned off. Turned on logging and restarted server. Entered the server address in web browser to repeat the error and Lo... behold! The WebUI appeared and is working! Maybe it was the restart of sage server that needed to be done, or logging must be turned on to work.

Thanks for your help again. Lovin Sage!

[jreichen]

I think it's probably a war extraction problem.

Right now as of Jetty plugin version 2.0.1 it logs to the sagetv debug log. You need to turn on SageTV's debug logging in the Detailed Setup menu. Then turn up Jetty's log level to debug or verbose in the Jetty Web Server plugin's configuration options screen in the Plugin Manager.