Updated Sage v9 jar and bmt

[RBraverman]

I've V9 installed months ago and haven't been able to update anything as everything gets borked, BUT until recently BMT was working - not now. As it appeared that it couldn't find it, I uninstalled it and when I go back to re-install it it is "not longer compatible".

I'm at V8 update 111 - downgraded to V7.65 and Core V9.0.9.441 which allowed me to install BMT, but I get:

HTTP ERROR: 503

Problem accessing /bmt/. Reason:

SERVICE_UNAVAILABLE

Powered by Jetty://

Actually I'm getting errors on most of the Web Interface - now with the downgrade THAT is working fine - just not BMT.


As usual I'm lost.

[RBraverman]

Originally Posted by CollegeProject

Now the webserver is not responding after updating BMT to latest version.

Nothing shows failed or update available in the plugins. I restarted sagetv service/computer and even the webbrowser through jetty. Any others seeing this?

I get the following error when trying to access

HTTP ERROR: 503

Problem accessing /bmt/. Reason:

    SERVICE_UNAVAILABLE

Powered by Jetty://

FWIW, you're not alone. Upped the core to V9.09.441 and down'd Java to V7.64, and, while I can now install it, I get the same error.

[pilotguy7ca]

I'm using Java 1.8.0_111 and am having issues, the BMT web interface says:

Phoenix: Error Failed to get status
SageTV: Error Failed to get status

All the links give up some type of error.

I'm seeing a few of these in the log file when this happens:

Fri 1/6 22:33:45.491 [11303092@qtp-32470813-2@ac78b4] ::INFO: global: ERROR: The serialization policy file '/bmtweb/CAB30916FB101D8663A32179CC025D55.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.492 [28018489@qtp-32470813-3@1ab8739] ::INFO: status: ERROR: The serialization policy file '/bmtweb/3227B78F2EA91C182438B85AA835316B.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.492 [8978272@qtp-32470813-5@88ff60] ::INFO: status: ERROR: The serialization policy file '/bmtweb/3227B78F2EA91C182438B85AA835316B.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.493 [9538190@qtp-32470813-7@918a8e] ::INFO: status: ERROR: The serialization policy file '/bmtweb/3227B78F2EA91C182438B85AA835316B.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.493 [19812509@qtp-32470813-6@12e509d] ::INFO: status: ERROR: The serialization policy file '/bmtweb/3227B78F2EA91C182438B85AA835316B.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.493 [6231331@qtp-32470813-4@5f1523] ::INFO: status: ERROR: The serialization policy file '/bmtweb/3227B78F2EA91C182438B85AA835316B.gwt.rpc' was not found; did you forget to include it in this deployment?
Fri 1/6 22:33:45.493 [19812509@qtp-32470813-6@12e509d] ::INFO: status: WARNING: Failed to get the SerializationPolicy '3227B78F2EA91C182438B85AA835316B' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Fri 1/6 22:33:45.494 [9538190@qtp-32470813-7@918a8e] ::INFO: status: WARNING: Failed to get the SerializationPolicy '3227B78F2EA91C182438B85AA835316B' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Fri 1/6 22:33:45.494 [8978272@qtp-32470813-5@88ff60] ::INFO: status: WARNING: Failed to get the SerializationPolicy '3227B78F2EA91C182438B85AA835316B' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Fri 1/6 22:33:45.494 [28018489@qtp-32470813-3@1ab8739] ::INFO: status: WARNING: Failed to get the SerializationPolicy '3227B78F2EA91C182438B85AA835316B' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Fri 1/6 22:33:45.495 [11303092@qtp-32470813-2@ac78b4] ::INFO: global: WARNING: Failed to get the SerializationPolicy 'CAB30916FB101D8663A32179CC025D55' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
Fri 1/6 22:33:45.495 [6231331@qtp-32470813-4@5f1523] ::INFO: status: WARNING: Failed to get the SerializationPolicy '3227B78F2EA91C182438B85AA835316B' for module 'http://10.10.12.15:8080/bmt/bmtweb/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.

[stuckless]

I do clean installs of sagetv almost weekly for various testing scenarios.

I have seen the "unavailable" error a few times, and for me, it has boiled down a couple of things...

1. My impatience. When you start sagetv, it starts all the plugins (one of them being jetty). Then, Jetty needs to install the webapps. So if start sagetv and then hit /bmt/ or /sage/ within the first minute... you can sometimes get this error, because, Jetty hasn't finished installing the web apps. Typically when I start sagetv, I tail the sagetv_0.txt log and I can watch the startup and I've seen for whatever reasons, jetty taking a long time to deploy the apps, so I wait for it to finish before hitting the server.

2. Clear browser caches.

3. Clear the jetty/webapps/ exploded war directories. You'll want to shutdown sagetv, and then go to the jetty/webapps/ directory. In there you'll see a bmt.war and a bmt/ folder. Delete the bmt/ folder. Restart sagetv, wait for full jetty startup, clear browser caches, hit the /bmt/ url.

If none of that fixes the issue, then likely in the sagetv_0.txt log file there are other errors.

Some of the more common errors, especially if you are upgrading an old system, is duplicate jars in the JARs folder. So for that, you need to look in the jars folder for jar files that have the same name but different versions (ie, you might see commons-io-1.2.jar and commons-io-2.3.jar).. delete the jar with the older version. Restart sagetv, and test again.

[pilotguy7ca]

Originally Posted by stuckless

I have seen the "unavailable" error a few times, and for me, it has boiled down a couple of things...

2. Clear browser caches.

Yup, that did it Thanks!.

[thomaszoo]

Originally Posted by stuckless

I have seen the "unavailable" error a few times, and for me, it has boiled down a couple of things...

2. Clear browser caches.

That did it for me, too. Thanks for the advice!