503 error

[wayner]

I am getting a 503 error when I try to run BMT on SageTV 9. Jetty seems fine as the Sage web UI works.

HTTP ERROR: 503

Problem accessing /bmt. Reason:

SERVICE_UNAVAILABLE

[tvmaster2]

Originally Posted by wayner

I am getting a 503 error when I try to run BMT on SageTV 9. Jetty seems fine as the Sage web UI works.

HTTP ERROR: 503

Problem accessing /bmt. Reason:

SERVICE_UNAVAILABLE

lol - what a surprise. Wish I could help you, but I'm sadly not on 9 yet

[wayner]

This was working a few days ago, although I was having issues with metadata and fanart for some files.

[stuckless]

Originally Posted by wayner

This was working a few days ago, although I was having issues with metadata and fanart for some files.

You could try just restarting the SageTV container (I think you are unRAID with Java8). If that doesn't work, you can post the sagetv_0.txt logs... If it's just BMT, then, also make sure you are using the Java8 container... I'm pretty sure the last time I released BMT, it built it using Java8, so likely it won't run under Java7.

[SteveW]

Originally Posted by stuckless

You could try just restarting the SageTV container (I think you are unRAID with Java8). If that doesn't work, you can post the sagetv_0.txt logs... If it's just BMT, then, also make sure you are using the Java8 container... I'm pretty sure the last time I released BMT, it built it using Java8, so likely it won't run under Java7.

OK that would explain why I'm getting the same error on bmt in my version 9 testing. I must have missed the announcement that it only uses Java 8. Guess I'll have to drop the mobile web interface since it only works with 7.

[stuckless]

Originally Posted by SteveW

OK that would explain why I'm getting the same error on bmt in my version 9 testing. I must have missed the announcement that it only uses Java 8. Guess I'll have to drop the mobile web interface since it only works with 7.

There isn't anything in BMT that requires java 8... it's just that when I last built it, I think I used java 8 so it might now require java 8. I can't even say this is absolutely true... but, I recall something along those lines. I don't have time to verify that statement at the moment

[wayner]

I actually have four systems on the go right now as I a m in a transitional state. This system that is having trouble with is SageTV V9.0.12.506 on Win10 64 bit. The Java version is 1.7.0_79.

BMT was working on this system a few weeks ago. I think since then I updated the SageTV to the latest Windows version in order to be able to switch the EPG to SD.

All other Jetty applets seem to work.

In the log files I see the following relating to BMT. Is this enough info or do you need something else from the logs.

If it is a case of upgrading Java to 8 - do you remember what that breaks? Is it just the mobile web UI? If so then that is fine with me.

Sat 1/21 23:07:01.908 [SageTV@15807eb] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/livepvrdata.war to C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\livepvrdata\webapp
Sat 1/21 23:07:02.534 [SageTV@15807eb] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/apps.war to C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\apps\webapp
Sat 1/21 23:07:02.655 [SageTV@15807eb] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/bmt.war to C:\Users\wayne\AppData\Local\Temp\Jetty_0_0_0_0_8080_bmt.war__bmt__9xmt47\webapp
Sat 1/21 23:07:04.896 [SageTV@15807eb] ::WARN:  failed browsing
Sat 1/21 23:07:04.900 [SageTV@15807eb] ::WARN:  failed databrowser
Sat 1/21 23:07:04.903 [SageTV@15807eb] ::WARN:  failed debug
Sat 1/21 23:07:04.907 [SageTV@15807eb] ::WARN:  failed filechooser
Sat 1/21 23:07:04.910 [SageTV@15807eb] ::WARN:  failed global
Sat 1/21 23:07:04.913 [SageTV@15807eb] ::WARN:  failed media
Sat 1/21 23:07:04.916 [SageTV@15807eb] ::WARN:  failed phoenixconfig
Sat 1/21 23:07:04.919 [SageTV@15807eb] ::WARN:  failed preferences
Sat 1/21 23:07:04.922 [SageTV@15807eb] ::WARN:  failed sage
Sat 1/21 23:07:04.925 [SageTV@15807eb] ::WARN:  failed status
Sat 1/21 23:07:04.928 [SageTV@15807eb] ::WARN:  failed videothumbnail
Sat 1/21 23:07:04.931 [SageTV@15807eb] ::WARN:  failed view
Sat 1/21 23:07:04.934 [SageTV@15807eb] ::WARN:  failed customvideos
Sat 1/21 23:07:04.937 [SageTV@15807eb] ::WARN:  failed fanart
Sat 1/21 23:07:04.941 [SageTV@15807eb] ::WARN:  failed json
Sat 1/21 23:07:04.944 [SageTV@15807eb] ::WARN:  Failed startup of context org.mortbay.jetty.webapp.WebAppContext@56260c{/bmt,C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/bmt.war}
Sat 1/21 23:07:04.973 [SageTV@15807eb] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/phoenix-rest.war to C:\Users\wayne\AppData\Local\Temp\Jetty_0_0_0_0_8080_phoenix.rest.war__phoenix.rest__6ou8of\webapp
Sat 1/21 23:07:05.028 [LibraryImporter@13e5008] Starting to scan lib import root: \\brora\Movies
Sat 1/21 23:07:05.146 [SageTV@15807eb] ::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
Sat 1/21 23:07:05.517 [SageTV@15807eb] ::INFO:  Extract C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/MediaStreaming.war to C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\MediaStreaming\webapp
Sat 1/21 23:07:05.913 [SageTV@15807eb] ::INFO:  SegmenterProcess transcoder for HTTPLS web streaming is C:\Program Files (x86)\SageTV\SageTV\SageTVTranscoder.exe
Sat 1/21 23:07:05.916 [SageTV@15807eb] ::INFO:  SegmenterProcess segmenter for HTTPLS web streaming is C:\Program Files (x86)\SageTV\SageTV\jetty\webapps\MediaStreaming\webapp\WEB-INF\bin\win32\ffmpeg.exe
Sat 1/21 23:07:05.923 [SageTV@15807eb] ::INFO:  Opened C:\Program Files (x86)\SageTV\SageTV\jetty\logs\2017_01_22.request.log
Sat 1/21 23:07:05.929 [SageTV@15807eb] ::INFO:  Started SelectChannelConnector@0.0.0.0:8080
Sat 1/21 23:07:05.932 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.934 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.936 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.938 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.940 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.942 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.944 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.947 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.949 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.951 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.953 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.955 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.958 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.960 [SageTV@15807eb] ::INFO:  Multiple exceptions
Sat 1/21 23:07:05.962 [SageTV@15807eb] ::INFO:  Error starting web application Batch Metadata Tools - Web Interface
Sat 1/21 23:07:05.964 [SageTV@15807eb] ::INFO:  Multiple exceptions

[wayner]

Ok, I threw caution to the wind and upgraded to Java V8 but that didn't work as now I can't run any Jetty apps - I get a 500 error. Then I saw that there was a Jetty upgrade available. So I upgraded Jetty and restarted Sage. But I still get a 500 error.

Anyone have any tips on getting the Jetty Web Server running on Windows under Java 8.

I am now on Jetty Web Server version 2.3.0.17

Never mind on the above. After upgrading to Java 8 the Jetty landing page is broken but I can get to the bmt page.