SageTV Community  

Go Back   SageTV Community > SageTV Development and Customizations > SageTV Github Development

Notices

SageTV Github Development Discussion related to SageTV Open Source Development. Use this forum for development topics about the Open Source versions of SageTV, hosted on Github.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-14-2016, 01:51 PM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
Jetty Web Server (status update)

FYI...

I've been working on a new phoenix update... which requires a new sagex api update and bmt update, and that got me into the "jetty update" to see what would be involved in getting the jetty web server to the latest build. (since I'm updating sagex and bmt I'll have to update them again for a new web server)

Currently we are using Jetty 6 and Jetty 9 is very different in terms of configurations, etc. I guess Jetty changed ownership (is now owned by eclipse) so the java packages are completely different. But, all that being said, I was able to create a new jetty 9 plugin.

After starting the server, the current web app doesn't work. So i downloaded it and made the changes to get it working. And then it "almost" worked except the groovy stuff didn't work... after spending 2 days on that... I upgraded to the latest groovy and now it works as well

At this point I have a working Jetty 9 with Java 8 and a working sagetv web app. This is still going to take some time to clean this up, but, at least it all works. I'm not sure who owns the current sagetv web app and the groovy plugins, I'll need to update those when I release a new jetty web server.

I was going to release everything together... ie, sagex, phoenix, bmt, jetty, groovy, web app, etc, but I'm thinking that'll be a never ending project

So, I'll go back to my original plan of updateing sagex and phoenix and bmt, and then work on an updated jetty.
Reply With Quote
  #2  
Old 08-14-2016, 03:30 PM
Skirge01's Avatar
Skirge01 Skirge01 is offline
SageTVaholic
 
Join Date: Jun 2007
Location: New Jersey
Posts: 2,599
Looks like it might be about time to try getting v9 running again on my system.

Thanks for the tireless work you do on Sage!

__________________
Server: XP, SuperMicro X9SAE-V, i7 3770T, Thermalright Archon SB-E, 32GB Corsair DDR3, 2 x IBM M1015, Corsair HX1000W PSU, CoolerMaster CM Storm Stryker case
Storage: 2 x Addonics 5-in-3 3.5" bays, 1 x Addonics 4-in-1 2.5" bay, 24TB
Client: Windows 7 64-bit, Foxconn G9657MA-8EKRS2H, Core2Duo E6600, Zalman CNPS7500, 2GB Corsair, 320GB, HIS ATI 4650, Antec Fusion
Tuners: 2 x HD-PVR (HTTP tuning), 2 x HDHR, USB-UIRT
Software: SageTV 7
Reply With Quote
  #3  
Old 08-14-2016, 10:00 PM
fresnoboy fresnoboy is offline
Sage Advanced User
 
Join Date: Sep 2008
Posts: 118
+1!

Thank you!
Reply With Quote
  #4  
Old 08-15-2016, 11:40 AM
dstanley's Avatar
dstanley dstanley is offline
Sage Aficionado
 
Join Date: Sep 2008
Location: LaHave, Nova Scotia, Canada
Posts: 284
Sean,
Thanks for all you do for the SageTV community - I really appreciate all your work!

Dwight
__________________
SERVER: Intel Core i7-3770 CPU @ 3.40GHz - UnRaid Server 6.8.0/DVB LibreELEC with Docker stuckless-sagetv-server-java9 MOTHERBOARD: ASRock-Z77 Extreme4 / 32GB RAM CACHE DRIVE: SSD 1TB ARRAY: 24TB/7 DRIVES PARITY: 8TB
EXTERNAL DEVICES: 4x HD-PVR's Firewire Channel Changing
TUNERS:NO LONGER RECORDING LIVETV
CLIENTS: 2xHD300 2xHD200 SONY ANDROIDTV MINI-CLIENT
Reply With Quote
  #5  
Old 08-15-2016, 02:21 PM
Taddeusz Taddeusz is offline
SageTVaholic
 
Join Date: Nov 2004
Location: Yukon, OK
Posts: 3,919
I installed the sagex v9 update on my Windows system and now I'm getting the following message whenever a sagex query is done:

Code:
HTTP ERROR 500

Problem accessing /sagex/api. Reason:

    Sage Servlet Failed: null
Powered by Jetty://
It seems to be working fine on my unRAID test system though.
__________________
Server: i5 8400, ASUS Prime H370M-Plus/CSM, 16GB RAM, 15TB drive array + 500GB cache, 2 HDHR's, SageTV 9, unRAID 6.6.3
Client 1: HD300 (latest FW), HDMI to an Insignia 65" 1080p LCD and optical SPDIF to a Sony Receiver
Client 2: HD200 (latest FW), HDMI to an Insignia NS-LCD42HD-09 1080p LCD
Reply With Quote
  #6  
Old 08-15-2016, 03:04 PM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
Quote:
Originally Posted by Taddeusz View Post
I installed the sagex v9 update on my Windows system and now I'm getting the following message whenever a sagex query is done:

Code:
HTTP ERROR 500

Problem accessing /sagex/api. Reason:

    Sage Servlet Failed: null
Powered by Jetty://
It seems to be working fine on my unRAID test system though.
Could you look in the sagetv_0.txt log file and see if there are any errors? I just tried it on my unRAID setup and my test dev server and it works there... Could be a Java 8 thing... ie, I use Java 8 for development, but I tell the compiler to compile down to Java 1.7... so I think it should still work with Java 1.7.
Reply With Quote
  #7  
Old 08-15-2016, 03:44 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,561
I'm running Java 1.7 on my Windows 7 x64 server and I'm seeing the same error and one other unexpected one.

Here's 1 unsuccessful, 2 successful and the results:

/sagex/api?c=IsDoingLibraryImportScan
This one doesn't accept any parameters.
Code:
<error sagex-version="9.0.0">
<message>
<![CDATA[
Too few args; Your Arg Count: 0; Required Arg Count: 1
]]>
</message>
<exception>
<![CDATA[
java.lang.RuntimeException: Too few args; Your Arg Count: 0; Required Arg Count: 1
 at sagex.remote.xmlrpc.RequestHelper.createParameters(RequestHelper.java:28)
 at sagex.remote.xmlrpc.RequestHelper.createRequest(RequestHelper.java:19)
 at sagex.remote.factory.request.GlobalFactory.createRequest(GlobalFactory.java:480)
 at sagex.remote.factory.request.SageRPCRequestFactory.createRequest(SageRPCRequestFactory.java:1298)
 at sagex.remote.api.ApiHandler.callSageAPI(ApiHandler.java:208)
 at sagex.remote.api.ApiHandler.handleRequest(ApiHandler.java:150)
 at sagex.remote.SagexServlet.doPost(SagexServlet.java:87)
 at sagex.remote.SagexServlet.doGet(SagexServlet.java:41)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
 at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
 at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
 at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
 at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
 at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
 at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
]]>
</exception>
</error>
/sagex/api?c=RunLibraryImportScan&1=false
It also did successfully kick off a library import.
Code:
<Result/>
/sagex/api?c=SageCommand&1=Up&context=0023a500070e
It moved the the cursor up on the extender.
Code:
<Result/>
It seems that the issues are with methods that return values. I strangely see nothing in the logs.

Update: I take that back, I saw the following after running /sagex/api?c=GetMediaFiles&1=T:
Code:
Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] Calling: Api: Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] nullMon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] ; Command: Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] GetMediaFilesMon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] ;
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG

Last edited by EnterNoEscape; 08-15-2016 at 03:50 PM.
Reply With Quote
  #8  
Old 08-15-2016, 04:19 PM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
Quote:
Originally Posted by EnterNoEscape View Post
I'm running Java 1.7 on my Windows 7 x64 server and I'm seeing the same error and one other unexpected one.

Here's 1 unsuccessful, 2 successful and the results:

/sagex/api?c=IsDoingLibraryImportScan
This one doesn't accept any parameters.
Code:
<error sagex-version="9.0.0">
<message>
<![CDATA[
Too few args; Your Arg Count: 0; Required Arg Count: 1
]]>
</message>
<exception>
<![CDATA[
java.lang.RuntimeException: Too few args; Your Arg Count: 0; Required Arg Count: 1
 at sagex.remote.xmlrpc.RequestHelper.createParameters(RequestHelper.java:28)
 at sagex.remote.xmlrpc.RequestHelper.createRequest(RequestHelper.java:19)
 at sagex.remote.factory.request.GlobalFactory.createRequest(GlobalFactory.java:480)
 at sagex.remote.factory.request.SageRPCRequestFactory.createRequest(SageRPCRequestFactory.java:1298)
 at sagex.remote.api.ApiHandler.callSageAPI(ApiHandler.java:208)
 at sagex.remote.api.ApiHandler.handleRequest(ApiHandler.java:150)
 at sagex.remote.SagexServlet.doPost(SagexServlet.java:87)
 at sagex.remote.SagexServlet.doGet(SagexServlet.java:41)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
 at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
 at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
 at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
 at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
 at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
 at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
 at org.mortbay.jetty.Server.handle(Server.java:326)
 at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
 at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
 at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
 at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
 at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
 at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
 at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
]]>
</exception>
</error>
/sagex/api?c=RunLibraryImportScan&1=false
It also did successfully kick off a library import.
Code:
<Result/>
/sagex/api?c=SageCommand&1=Up&context=0023a500070e
It moved the the cursor up on the extender.
Code:
<Result/>
It seems that the issues are with methods that return values. I strangely see nothing in the logs.

Update: I take that back, I saw the following after running /sagex/api?c=GetMediaFiles&1=T:
Code:
Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] Calling: Api: Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] nullMon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] ; Command: Mon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] GetMediaFilesMon 8/15 17:47:20.622 [9540670@qtp-30512421-6@91943e] ;
Thanks... I found the issue... I "cleaned up" the generator (a little) in v9 and I introduced a bug I've created a unit test around it now.

I'll try to generate and publish a new build tonight.
Reply With Quote
  #9  
Old 08-15-2016, 04:43 PM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
Quote:
Originally Posted by Taddeusz View Post
I installed the sagex v9 update on my Windows system and now I'm getting the following message whenever a sagex query is done:

Code:
HTTP ERROR 500

Problem accessing /sagex/api. Reason:

    Sage Servlet Failed: null
Powered by Jetty://
It seems to be working fine on my unRAID test system though.
It would appear that until you access the web server (ie, the /sage/ or /bmt/) paths, the /sagex path is not activated.


FYI... updated sagex apis to 9.0.0.1 to fix the previous issue.
Reply With Quote
  #10  
Old 08-15-2016, 05:19 PM
EnterNoEscape's Avatar
EnterNoEscape EnterNoEscape is offline
SageTVaholic
 
Join Date: Jun 2010
Location: Harrisburg, PA
Posts: 2,561
Thanks for maintaining this incredibly useful API!
__________________
SageTV v9 Server: ASRock Z97 Extreme4, Intel i7-4790K @ 4.4Ghz, 32GB RAM, 6x 3TB 7200rpm HD, 2x 5TB 7200rpm HD, 2x 6TB 7200rpm HD, 4x 256GB SSD, 4x 500GB SSD, unRAID Pro 6.7.2 (Dual Parity + SSD Cache).
Capture: 1x Ceton InfiniTV 4 (ClearQAM), 2x Ceton InfiniTV 6, 1x BM1000-HDMI, 1x BM3500-HDMI.

Clients: 1x HD300 (Living Room), 1x HD200 (Master Bedroom).
Software: OpenDCT :: WMC Live TV Tuner :: Schedules Direct EPG
Reply With Quote
  #11  
Old 08-15-2016, 07:06 PM
wayner wayner is offline
SageTVaholic
 
Join Date: Jan 2008
Location: Toronto, ON
Posts: 6,767
Quote:
Originally Posted by stuckless View Post
I'm not sure who owns the current sagetv web app and the groovy plugins, I'll need to update those when I release a new jetty web server.
I think skiingwiz took over the web app from Slugger. I am not sure if anyone took over the groovy stuff.
__________________
New Server - Sage9 on unRAID 2xHD-PVR, HDHR for OTA
Old Server - Sage7 on Win7Pro-i660CPU with 4.6TB, HD-PVR, HDHR OTA, HVR-1850 OTA
Clients - 2xHD-300, 8xHD-200 Extenders, Client+2xPlaceshifter and a WHS which acts as a backup Sage server
Reply With Quote
  #12  
Old 08-15-2016, 08:41 PM
KryptoNyte's Avatar
KryptoNyte KryptoNyte is offline
Sage Icon
 
Join Date: Dec 2006
Posts: 2,317
Thank you for doing this work, Sean.
Reply With Quote
  #13  
Old 08-15-2016, 08:43 PM
fresnoboy fresnoboy is offline
Sage Advanced User
 
Join Date: Sep 2008
Posts: 118
Quote:
Originally Posted by stuckless View Post
It would appear that until you access the web server (ie, the /sage/ or /bmt/) paths, the /sagex path is not activated.


FYI... updated sagex apis to 9.0.0.1 to fix the previous issue.
I am seeing exactly the same problem, running 9.0.0.1. I still get this error after accessing BMT or Sage's normal webserver pages (both of those work fine too).

I am running the latest java 8 under linux.

Thanks!
Mike
Reply With Quote
  #14  
Old 08-16-2016, 05:07 AM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
Quote:
Originally Posted by fresnoboy View Post
I am seeing exactly the same problem, running 9.0.0.1. I still get this error after accessing BMT or Sage's normal webserver pages (both of those work fine too).

I am running the latest java 8 under linux.

Thanks!
Mike
I didn't change anything in terms of when/how sagex/api is activated... I just noticed that after I restarted my server, and then hit /sages/api I got the 404 error page. I then hit /sage/ and then went back to /sagex/api and then it worked.... it could have been a timing thing on my part (ie, the web server was not fully started when I first hit it). This update for the sagex-api to v9 is just a jar file change that adds/updates apis that have changed since v7.

But, if you are still having the issue, then check the sagetv_0.txt logs and see if there is an issue there.
Reply With Quote
  #15  
Old 08-16-2016, 07:55 AM
Taddeusz Taddeusz is offline
SageTVaholic
 
Join Date: Nov 2004
Location: Yukon, OK
Posts: 3,919
I upgraded to 9.0.0.1 this morning and I'm still getting this error on my Windows server. I don't see an error in the log. I'm seeing this entry:

Code:
Tue 8/16 8:52:59.379 [5625690@qtp-5352340-3@55d75a] Calling: Api: Tue 8/16 8:52:59.380 [5625690@qtp-5352340-3@55d75a] nullTue 8/16 8:52:59.380 [5625690@qtp-5352340-3@55d75a] ; Command: Tue 8/16 8:52:59.380 [5625690@qtp-5352340-3@55d75a] GetMediaFilesTue 8/16 8:52:59.380 [5625690@qtp-5352340-3@55d75a] ;
__________________
Server: i5 8400, ASUS Prime H370M-Plus/CSM, 16GB RAM, 15TB drive array + 500GB cache, 2 HDHR's, SageTV 9, unRAID 6.6.3
Client 1: HD300 (latest FW), HDMI to an Insignia 65" 1080p LCD and optical SPDIF to a Sony Receiver
Client 2: HD200 (latest FW), HDMI to an Insignia NS-LCD42HD-09 1080p LCD
Reply With Quote
  #16  
Old 08-16-2016, 08:37 AM
fresnoboy fresnoboy is offline
Sage Advanced User
 
Join Date: Sep 2008
Posts: 118
Here's what my sagetv_0.txt says (copied from my ssh window):

Tue 8/16 7:31:09.881 [main@271053e1] Error discovering servers:java.net.SocketTi
meoutException: Receive timed out
Tue 8/16 7:31:10.401 [main@271053e1] detect 3
INFO - Configured Root Logger
Tue 8/16 7:20:36.643 [SageTV@47b6e73] LOG4J: Configured Root Logger
INFO - Configured Logging for: sagex-api using file: sagex-api.log4j.properties
Tue 8/16 7:20:36.692 [SageTV@47b6e73] LOG4J: Configured Logging for: sagex-api u
sing file: sagex-api.log4j.properties
Tue 8/16 7:20:36.740 [SageTV@47b6e73] ::INFO: Logging to sagex.jetty.log.JettyS
tarterLogger@1d1e09c5 via sagex.jetty.log.JettyStarterLogger
Tue 8/16 7:20:36.740 [SageTV@47b6e73] ::INFO: Jetty Starter plugin version 2.3.
0.14
Tue 8/16 7:20:37.129 [SageTV@47b6e73] ::INFO: Starting Jetty
Tue 8/16 7:20:37.130 [SageTV@47b6e73] ::INFO: Jetty Plugin log level: INFO
Tue 8/16 7:20:37.337 [SageTV@47b6e73] ::INFO: jetty-6.1.19
Tue 8/16 7:20:37.409 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/mediastreaming.xml -> org.mortbay.jetty.webapp.WebAppContext@2b1a6de7{/s
tream,/opt/sagetv/server/jetty/webapps/MediaStreaming.war}
Tue 8/16 7:20:37.426 [SageTV@47b6e73] ::INFO: mime.types file not found in over
ride location /opt/sagetv/server/webserver/mime.types. Checking default locatio
ns.
Tue 8/16 7:20:37.451 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/nielm_websrv.context.xml -> org.mortbay.jetty.webapp.WebAppContext@2d526
e96{/sage,/opt/sagetv/server/jetty/webapps/nielm_sagewebserver.war}
Tue 8/16 7:20:37.459 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/bmt.xml -> org.mortbay.jetty.webapp.WebAppContext@57e85914{/bmt,/opt/sag
etv/server/jetty/webapps/bmt.war}
Tue 8/16 7:20:37.472 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/apps.xml -> org.mortbay.jetty.webapp.WebAppContext@7a114eb9{/apps,/opt/s
agetv/server/jetty/webapps/apps.war}
Tue 8/16 7:20:37.533 [SageTV@47b6e73] Media Servlet Handler Created.
Tue 8/16 7:20:37.540 [SageTV@47b6e73] Sagex ApiServlet Created for version: 9.0.
0
Tue 8/16 7:20:37.656 [SageTV@47b6e73] SAGEX-API: Starting Http Context
Tue 8/16 7:20:37.657 [SageTV@47b6e73] SAGEX-API: Updated Constrant Authenticatio
n: true
Tue 8/16 7:20:37.657 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/sagex.xml -> org.mortbay.jetty.servlet.Context@37be0d29{/sagex,null}
Tue 8/16 7:20:37.676 [SageTV@47b6e73] ::INFO: Deploy /opt/sagetv/server/jetty/c
ontexts/sagewebapp.xml -> org.mortbay.jetty.webapp.WebAppContext@7c744411{/sagem
,/opt/sagetv/server/jetty/webapps/SageWebApp.war}
Tue 8/16 7:20:37.759 [SageTV@47b6e73] ::INFO: Extract /opt/sagetv/server/jetty/
webapps/MediaStreaming.war to /opt/sagetv/server/jetty/webapps/MediaStreaming/we
bapp
Tue 8/16 7:20:38.360 [SageTV@47b6e73] ::INFO: SegmenterProcess transcoder for H
TTPLS web streaming is /opt/sagetv/server/ffmpeg
Tue 8/16 7:20:38.360 [SageTV@47b6e73] ::INFO: SegmenterProcess segmenter for HT
TPLS web streaming is /opt/sagetv/server/jetty/webapps/MediaStreaming/webapp/WEB
-INF/bin/linux32/ffmpeg
Tue 8/16 7:20:38.456 [SageTV@47b6e73] ::INFO: Extract /opt/sagetv/server/jetty/
webapps/nielm_sagewebserver.war to /opt/sagetv/server/jetty/webapps/nielm_sagewe
bserver/webapp
Tue 8/16 7:20:38.602 [SageTV@47b6e73] ::INFO: Extract /opt/sagetv/server/jetty/
webapps/bmt.war to /tmp/Jetty_0_0_0_0_8080_bmt.war__bmt__9xmt47/webapp
Tue 8/16 7:20:39.083 [SageTV@47b6e73] ::INFO: Extract /opt/sagetv/server/jetty/
webapps/apps.war to /opt/sagetv/server/jetty/webapps/apps/webapp
Tue 8/16 7:20:39.216 [SageTV@47b6e73] ::INFO: Extract /opt/sagetv/server/jetty/
webapps/SageWebApp.war to /opt/sagetv/server/jetty/webapps/SageWebApp/webapp
Tue 8/16 7:20:39.507 [SageTV@47b6e73] ::INFO: Opened /opt/sagetv/server/jetty/l
ogs/2016_08_16.request.log
Tue 8/16 7:20:39.516 [SageTV@47b6e73] ::INFO: Started SelectChannelConnector@0.
0.0.0:8080
INFO - Configured Logging for: phoenix using file: phoenix.log4j.properties
Tue 8/16 7:20:39.536 [SageTV@47b6e73] LOG4J: Configured Logging for: phoenix usi
ng file: phoenix.log4j.properties
INFO - Configured Logging for: phoenix-metadata using file: phoenix-metadata.log
4j.properties
Tue 8/16 7:20:39.536 [SageTV@47b6e73] LOG4J: Configured Logging for: phoenix-met
adata using file: phoenix-metadata.log4j.properties
Aug 16, 2016 7:20:39 AM org.fourthline.cling.UpnpServiceImpl <init>
INFO: >>> Starting UPnP service...
Aug 16, 2016 7:20:39 AM org.fourthline.cling.UpnpServiceImpl <init>
INFO: Using configuration: org.fourthline.cling.DefaultUpnpServiceConfiguration
Aug 16, 2016 7:20:39 AM org.fourthline.cling.transport.RouterImpl <init>
INFO: Creating Router: org.fourthline.cling.transport.RouterImpl
Aug 16, 2016 7:20:39 AM org.fourthline.cling.transport.impl.MulticastReceiverImp
l init
INFO: Creating wildcard socket (for receiving multicast datagrams) on port: 1900
Aug 16, 2016 7:20:39 AM org.fourthline.cling.transport.impl.MulticastReceiverImp
l init
INFO: Joining multicast group: /239.255.255.250:1900 on network interface: eth0
Aug 16, 2016 7:20:39 AM org.fourthline.cling.transport.impl.StreamServerImpl ini
t
INFO: Created server (for receiving TCP streams) on: /10.0.8.130:46198
Aug 16, 2016 7:20:39 AM org.fourthline.cling.transport.impl.DatagramIOImpl init
INFO: Creating bound socket (for datagram input/output) on: /10.0.8.130
Aug 16, 2016 7:20:39 AM org.fourthline.cling.UpnpServiceImpl <init>
INFO: <<< UPnP service started successfully
Tue 8/16 7:20:41.164 [SageTV@47b6e73] SLF4J: Failed to load class "org.slf4j.imp
l.StaticLoggerBinder".
Tue 8/16 7:20:41.164 [SageTV@47b6e73] SLF4J: Defaulting to no-operation (NOP) lo
gger implementation
Tue 8/16 7:20:41.164 [SageTV@47b6e73] SLF4J: See http://www.slf4j.org/codes.html
#StaticLoggerBinder for further details.
Aug 16, 2016 7:20:54 AM org.fourthline.cling.binding.xml.UDA10DeviceDescriptorBi
nderImpl hydrateSpecVersion
WARNING: Unsupported UDA minor version, ignoring: 1
Tue 8/16 7:21:07.212 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateShow): 105ms
for 0 items in 1 loops, lock time 0 ms
Tue 8/16 7:21:07.276 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateTitle): 1ms f
or 12 items in 1 loops
Tue 8/16 7:21:07.333 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateYears): 0ms f
or 1 items in 1 loops
Tue 8/16 7:21:07.436 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdatePeoples): 5ms
for 58 items in 1 loops
Tue 8/16 7:21:07.497 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateCategories):
0ms for 0 items in 1 loops
Tue 8/16 7:21:07.564 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateSubCategories
): 0ms for 0 items in 1 loops
Tue 8/16 7:21:07.624 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateRated): 0ms f
or 0 items in 1 loops
Tue 8/16 7:21:07.684 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdatePRs): 0ms for
0 items in 1 loops
Tue 8/16 7:21:07.744 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateERs): 0ms for
0 items in 1 loops
Tue 8/16 7:21:07.805 [EPG@63534aeb] MaintenceMetric(MediaMaskUpdateBonus): 0ms f
or 0 items in 1 loops
INFO - Configured Logging for: bmtweb using file: bmtweb.log4j.properties
Tue 8/16 7:24:39.108 [877171180@qtp-284912954-5@344891ec] LOG4J: Configured Logg
ing for: bmtweb using file: bmtweb.log4j.properties
Reply With Quote
  #17  
Old 08-16-2016, 08:47 AM
fresnoboy fresnoboy is offline
Sage Advanced User
 
Join Date: Sep 2008
Posts: 118
and here is the sagex-api log file:

2016-08-16 07:31:43,060 [1382164443@qtp-284912954-7] WARN sagex.remote.SagexServlet - Failed to process Sage Handler!
java.lang.StackOverflowError
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3776)
at java.util.regex.Pattern$Curly.match(Pattern.java:4227)
at java.util.regex.Pattern$Start.match(Pattern.java:3461)
at java.util.regex.Matcher.search(Matcher.java:1248)
at java.util.regex.Matcher.find(Matcher.java:637)
at java.util.regex.Matcher.replaceAll(Matcher.java:951)
at java.lang.String.replaceAll(String.java:2223)
at sagex.remote.builder.SageAPIBuilder.makeName(SageAPIBuilder.java:237)
at sagex.remote.builder.SageAPIBuilder.buildSimpleData(SageAPIBuilder.java:84)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:33)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildChannel(SageAPIBuilder.java:100)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:63)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)


this last set of lines just keeps on repeating - probably because my plex server is doing a query for all the recordings as part of the plex plugin running.

thx,
mike
Reply With Quote
  #18  
Old 08-16-2016, 09:03 AM
Taddeusz Taddeusz is offline
SageTVaholic
 
Join Date: Nov 2004
Location: Yukon, OK
Posts: 3,919
Quote:
Originally Posted by fresnoboy View Post
and here is the sagex-api log file:

2016-08-16 07:31:43,060 [1382164443@qtp-284912954-7] WARN sagex.remote.SagexServlet - Failed to process Sage Handler!
java.lang.StackOverflowError
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3776)
at java.util.regex.Pattern$Curly.match(Pattern.java:4227)
at java.util.regex.Pattern$Start.match(Pattern.java:3461)
at java.util.regex.Matcher.search(Matcher.java:1248)
at java.util.regex.Matcher.find(Matcher.java:637)
at java.util.regex.Matcher.replaceAll(Matcher.java:951)
at java.lang.String.replaceAll(String.java:2223)
at sagex.remote.builder.SageAPIBuilder.makeName(SageAPIBuilder.java:237)
at sagex.remote.builder.SageAPIBuilder.buildSimpleData(SageAPIBuilder.java:84)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:33)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildChannel(SageAPIBuilder.java:100)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:63)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)
at sagex.remote.builder.SageAPIBuilder.buildObject(SageAPIBuilder.java:156)
at sagex.remote.builder.SageAPIBuilder.buildAiring(SageAPIBuilder.java:120)
at sagex.remote.builder.SageAPIBuilder.build(SageAPIBuilder.java:57)


this last set of lines just keeps on repeating - probably because my plex server is doing a query for all the recordings as part of the plex plugin running.

thx,
mike
I see the same thing and for the time being until this can be resolved I don't have my Plex running.
__________________
Server: i5 8400, ASUS Prime H370M-Plus/CSM, 16GB RAM, 15TB drive array + 500GB cache, 2 HDHR's, SageTV 9, unRAID 6.6.3
Client 1: HD300 (latest FW), HDMI to an Insignia 65" 1080p LCD and optical SPDIF to a Sony Receiver
Client 2: HD200 (latest FW), HDMI to an Insignia NS-LCD42HD-09 1080p LCD
Reply With Quote
  #19  
Old 08-16-2016, 09:25 AM
stuckless's Avatar
stuckless stuckless is offline
SageTVaholic
 
Join Date: Oct 2007
Location: London, Ontario, Canada
Posts: 9,591
So when you got to /sagex/api without any parameters... do you get an error?
Reply With Quote
  #20  
Old 08-16-2016, 09:46 AM
fresnoboy fresnoboy is offline
Sage Advanced User
 
Join Date: Sep 2008
Posts: 118
Quote:
Originally Posted by stuckless View Post
So when you got to /sagex/api without any parameters... do you get an error?
Nope. Returns the list of possible parameters, etc...

Thx
Mike
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Plugin: Jetty Web Server 2.0 jreichen SageTV v7 Customizations 388 02-28-2019 10:53 PM
Jetty Web Server Issue Ghildebr SageTV v9 Customizations 17 09-03-2016 09:52 AM
Windows OS Update For Server? voorhees General Discussion 11 12-28-2012 03:26 PM


All times are GMT -6. The time now is 02:30 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.