Plex Scanner and BMT Agent for SageTV

[mgpaulus]

So, I've been using these scanners, and recently updated to the latest version. Ran into a couple of issues, and I have some patches I'd like to submit for review. What's the best way to do that? Is there a mailing list, or can I attach them here?

[wildgoose]

Originally Posted by mgpaulus

So, I've been using these scanners, and recently updated to the latest version. Ran into a couple of issues, and I have some patches I'd like to submit for review. What's the best way to do that? Is there a mailing list, or can I attach them here?

You can clone the github repo, and make the changes in your repo, then submit a pull request (this is the standard github way...) You can also send the diffs/files to me directly if you prefer.

[fresnoboy]

Guys, I just transitioned to v9 Sage and transitioned to the linux server version. I have a huge number of recordings, and the new v9 windows version completely choked for some reason.

So I finally got everything transitioned today. I still need to get comskip running, but the more pressing issue is this plugin is not working anymore.

Plex's logs indicate its talking to the linux system just fine, and it's finding all the files properly, but sagex is coming back saying it has no data for every show it's asked about. I did put the plex.js file in the sagetv/sagex/services directory and restarted sage, but no joy.

I remember I had a similar problem before that seemed to be caused by a java version mismatch. Now sage is running with a 64 bit version 8 java. Do any of you have this same setup running ok? Is there a problem with the plugin, or is there something I am missing?

Thanks!
Mike

[Sparhawk6]

For the life of me I cannot figure out where I'm going wrong in setting up the new version of the scanner/agent. I had been running fine for many months, but suddenly it stopped a couple of weeks ago. I therefore attempted to install the new version. I keep getting the following error:

2016-07-10 18:46:12,526| INFO    | [243/384] Processing H:\ModernFamily-TheVerdict-20166093-0.ts
2016-07-10 18:46:12,526| DEBUG   | Getting media info from SageTV ...
2016-07-10 18:46:12,528| DEBUG   | openUrl: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json
2016-07-10 18:46:33,553| ERROR   | openUrl: failed on: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json: [Errno socket error] [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-10 18:46:33,553| ERROR   | No media info from SageTV: ModernFamily-TheVerdict-20166093-0.ts

I'm not sure if Sage isn't configured properly, or if I simply have the wrong username, password, or port. I read in this thread that the username and password is my "sage" username and password, but I have no idea what that means. I never input a sage username and password anywhere. Is the scanner attempting to use Jetty? Is it the Jetty username and password? How do I change this username and password?

Is my problem that Jetty isn't functioning? I had Java 8 installed, but after reading of the issues with it, I downgraded to Java 7. But that did not fixed the issue. I see in the Jetty requests history the Plex box making requests to get the data, but for some reason it isn't going through. Where am I going wrong?

[fresnoboy]

Originally Posted by Sparhawk6

For the life of me I cannot figure out where I'm going wrong in setting up the new version of the scanner/agent. I had been running fine for many months, but suddenly it stopped a couple of weeks ago. I therefore attempted to install the new version. I keep getting the following error:

2016-07-10 18:46:12,526| INFO    | [243/384] Processing H:\ModernFamily-TheVerdict-20166093-0.ts
2016-07-10 18:46:12,526| DEBUG   | Getting media info from SageTV ...
2016-07-10 18:46:12,528| DEBUG   | openUrl: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json
2016-07-10 18:46:33,553| ERROR   | openUrl: failed on: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json: [Errno socket error] [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-10 18:46:33,553| ERROR   | No media info from SageTV: ModernFamily-TheVerdict-20166093-0.ts

I'm not sure if Sage isn't configured properly, or if I simply have the wrong username, password, or port. I read in this thread that the username and password is my "sage" username and password, but I have no idea what that means. I never input a sage username and password anywhere. Is the scanner attempting to use Jetty? Is it the Jetty username and password? How do I change this username and password?

Is my problem that Jetty isn't functioning? I had Java 8 installed, but after reading of the issues with it, I downgraded to Java 7. But that did not fixed the issue. I see in the Jetty requests history the Plex box making requests to get the data, but for some reason it isn't going through. Where am I going wrong?

Sage and frey are the defaults. This seems to be the failure mode when things are not working right, but I can't find any log data that describes what's wrong on the sage side.

I know the plex plugin failed when I updated the java on my sage server to v8. I thought I was only updating the 64 bit version (which sage on windows doesn't use), but the update process I did also updated the 32 bit version.

My experience is that the plugin on windows won't run with a v8 32 bit java. You should check that and see if that's causing your failures.

Of course, the linux version of java used is v8 and 64 bit, so I suspect that may be a problem I am seeing, but if someone else here has it running on v9 linux, that would help a lot in debugging.

thanks!
mike

[Fuzzy]

Originally Posted by Sparhawk6

For the life of me I cannot figure out where I'm going wrong in setting up the new version of the scanner/agent. I had been running fine for many months, but suddenly it stopped a couple of weeks ago. I therefore attempted to install the new version. I keep getting the following error:

2016-07-10 18:46:12,526| INFO    | [243/384] Processing H:\ModernFamily-TheVerdict-20166093-0.ts
2016-07-10 18:46:12,526| DEBUG   | Getting media info from SageTV ...
2016-07-10 18:46:12,528| DEBUG   | openUrl: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json
2016-07-10 18:46:33,553| ERROR   | openUrl: failed on: http://sage:frey@192.168.1.8:8080/sagex/api?c=plex:GetMediaFileForName&1=ModernFamily-TheVerdict-20166093-0.ts&encoder=json: [Errno socket error] [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-10 18:46:33,553| ERROR   | No media info from SageTV: ModernFamily-TheVerdict-20166093-0.ts

I'm not sure if Sage isn't configured properly, or if I simply have the wrong username, password, or port. I read in this thread that the username and password is my "sage" username and password, but I have no idea what that means. I never input a sage username and password anywhere. Is the scanner attempting to use Jetty? Is it the Jetty username and password? How do I change this username and password?

Is my problem that Jetty isn't functioning? I had Java 8 installed, but after reading of the issues with it, I downgraded to Java 7. But that did not fixed the issue. I see in the Jetty requests history the Plex box making requests to get the data, but for some reason it isn't going through. Where am I going wrong?

Can you connect to sagex with your browser?
http://192.168.1.8:8080/sagex/api

[fresnoboy]

Ping... Anyone here have this plugin running properly on v9 Linux?

Thx!
Mike

[stuckless]

Originally Posted by fresnoboy

Ping... Anyone here have this plugin running properly on v9 Linux?

Thx!
Mike

I don't use it now, but I have had it running under linux, before. Did you answer Fuzzy's question above? and Do you have sagex-services installed?

[fresnoboy]

Yes, sagex services are installed, and I can connect to it with a browser...

Thx
mike

[stuckless]

Originally Posted by fresnoboy

Yes, sagex services are installed, and I can connect to it with a browser...

Thx
mike

And what happens when you the URL that is complaining about... into a browser...

http://sage:frey@192.168.1.8:8080/sa...s&encoder=json

[fresnoboy]

Ah, here is what the output looks like:

{"sagexVersion":"7.1.9.1","exception":"java.lang.RuntimeException: javax.script.ScriptException: TypeError: MediaFileAPI.GetMediaFiles is not a function in <eval> at line number 46\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:200)\n\tat sagex.remote.api.ApiHandler.handleRequest(ApiHandler.java:140)\n\tat sagex.remote.SagexServlet.doPost(SagexServlet.java:87)\n\tat sagex.remote.SagexServlet.doGet(SagexServlet.java:41)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:707)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)\n\tat org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)\n\tat org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)\n\tat org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)\n\tat org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)\n\tat org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)\n\tat org.mortbay.jetty.Server.handle(Server.java:326)\n\tat org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)\n\tat org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)\n\tat org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)\n\tat org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)\n\tat org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)\n\tat org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)\n\tat org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)\nCaused by: javax.script.ScriptException: TypeError: MediaFileAPI.GetMediaFiles is not a function in <eval> at line number 46\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(NashornScriptEngine.java:467)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeImpl(NashornScriptEngine.java:389)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeFunction(NashornScriptEngine.java:190)\n\tat sagex.remote.api.ServiceFactory.callService(ServiceFactory.java:83)\n\tat sagex.remote.api.ApiHandler.callService(ApiHandler.java:198)\n\t... 22 more\nCaused by: <eval>:46 TypeError: MediaFileAPI.GetMediaFiles is not a function\n\tat jdk.nashorn.internal.runtime.ECMAErrors.error(ECMAErrors.java:57)\n\tat jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:213)\n\tat jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:185)\n\tat jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:172)\n\tat jdk.nashorn.internal.runtime.Undefined.lookup(Undefined.java:102)\n\tat jdk.nashorn.internal.runtime.linker.NashornLinker.getGuardedInvocation(NashornLinker.java:106)\n\tat jdk.nashorn.internal.runtime.linker.NashornLinker.getGuardedInvocation(NashornLinker.java:98)\n\tat jdk.internal.dynalink.support.CompositeTypeBasedGuardingDynamicLinker.getGuardedInvocation(CompositeTypeBasedGuardingDynamicLinker.java:176)\n\tat jdk.internal.dynalink.support.CompositeGuardingDynamicLinker.getGuardedInvocation(CompositeGuardingDynamicLinker.java:124)\n\tat jdk.internal.dynalink.support.LinkerServicesImpl.getGuardedInvocation(LinkerServicesImpl.java:154)\n\tat jdk.internal.dynalink.DynamicLinker.relink(DynamicLinker.java:253)\n\tat jdk.nashorn.internal.scripts.Script$Recompilation$1$1499A$\\^eval\\_.GetMediaFileForName(<eval>:46)\n\tat jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:625)\n\tat jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:494)\n\tat jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:393)\n\tat jdk.nashorn.api.scripting.ScriptObjectMirror.callMember(ScriptObjectMirror.java:199)\n\tat jdk.nashorn.api.scripting.NashornScriptEngine.invokeImpl(NashornScriptEngine.java:383)\n\t... 25 more\n","error":"javax.script.ScriptException: TypeError: MediaFileAPI.GetMediaFiles is not a function in <eval> at line number 46"}

[Taddeusz]

I'm running SageTV on Windows. I've seen this problem when I accidentally upgraded my Java to v8. I had to uninstall v8 and reinstall the latest v7 to get it working again.

[fresnoboy]

Originally Posted by Taddeusz

I'm running SageTV on Windows. I've seen this problem when I accidentally upgraded my Java to v8. I had to uninstall v8 and reinstall the latest v7 to get it working again.

Yes, that happened to me as well. No real option to use a old Java under Linux without some hacking...

Thx
Mike

[Fuzzy]

Originally Posted by fresnoboy

Yes, that happened to me as well. No real option to use a old Java under Linux without some hacking...

Thx
Mike

You can use Java 7 on Linux just fine.

[fresnoboy]

Originally Posted by Fuzzy

You can use Java 7 on Linux just fine.

Well, given most of the testing on v9 is done with java 8, I would like to keep the core running on v8. The question is whether or not you can make sagex or the plex.js run on v7 without the rest of sage doing that.

Thx
Mike

[Fuzzy]

Originally Posted by fresnoboy

Well, given most of the testing on v9 is done with java 8, I would like to keep the core running on v8. The question is whether or not you can make sagex or the plex.js run on v7 without the rest of sage doing that.

Thx
Mike

No. Jetty runs in the SageTV Server's JVM, so it will be running in the same version.

[stuckless]

Over the past couple of weeks(weekends, really), I've been working on an updated Phoenix and BMT that is compatible with Phoenix. In doing this, I've discovered that the JavaScript engine in Java 8 changed from Java 7. This broke how the JS scripts are processed by the JavaScript engine.

I've created a "work around" in the latest phoenix that should allow the "old" js scripts to run as-is under Java 8 as well.

I'm not sure I'll get the Phoenix stuff out this weekend or not, but when I do, it should fix this specific issue.

[fresnoboy]

Originally Posted by stuckless

Over the past couple of weeks(weekends, really), I've been working on an updated Phoenix and BMT that is compatible with Phoenix. In doing this, I've discovered that the JavaScript engine in Java 8 changed from Java 7. This broke how the JS scripts are processed by the JavaScript engine.

I've created a "work around" in the latest phoenix that should allow the "old" js scripts to run as-is under Java 8 as well.

I'm not sure I'll get the Phoenix stuff out this weekend or not, but when I do, it should fix this specific issue.

Thanks much Stuckless! We really appreciate it and look forward to the mods...

Thx
milo

[Sparhawk6]

Originally Posted by Fuzzy

Can you connect to sagex with your browser?
http://192.168.1.8:8080/sagex/api

No, I cannot. EDIT: Nevermind, I figured it out. I had configured my jetty port to be different than the default. That was screwing me up.

[fresnoboy]

Any updates on the fix?

Thx!