![]() |
|
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. |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#21
|
||||
|
||||
Well that would be one Mr: jreichen
I sent him a PM as well but he's on this thread for Jetty 9 . . .
__________________
AMD Ryzen 9 3900XT 12 Core+HT, 64GB DDR5, GeForce 1060, MSI Prestige x570 Creation Mobo, SIIG 4 port Serial PCIe Card, Win10, 1TB M.2 SSD OS HDD, 1 URay HDMI Network Encoder, 3 HD-PVR, 4 DirecTV STB serial tuned |
#22
|
|||
|
|||
Well, in terms of bringing the old jetty server + assorted plugins forward to Java 8, we get this additional point of interest today:
Maybe an issue with the order things are loading into memory? |
#23
|
|||
|
|||
I'm also able to access the Web Interface to Sage (and also BMT) without any problem with Java 8 (which I installed before I found out that I shouldn't). Both computers are Windows 7 and both have Java 8.
I occasionally reboot the Sage Server, but I've never done the "reset web server" thing. I do have a slight delay set for the start of the Sage Server when I boot, so it comes up after most everything else has loaded. |
#24
|
||||
|
||||
Quote:
__________________
Server: Intel Core i5 760 Quad, Gigabyte GA-H57M-USB3, 4GB RAM, Gigabyte GeForce 210, 120GB SSD (OS), 1TB SATA, HD HomeRun. Extender: STP-HD300, Harmony 550 Remote, Netgear MCA1001 Ethernet over Coax. SageTV: SageTV Server 7.1.8 on Ubuntu Linux 11.04, SageTV Placeshifter for Mac 6.6.2, SageTV Client 7.0.15 for Windows, Linux Placeshifter 7.1.8 on Server and Client, Java 1.6. Plugins: Jetty, Nielm's Web Server, Mobile Web Interface. |
#25
|
|||
|
|||
It's still a problem. I did a fresh install of SageTV 9 on Windows and the install fails with the following error:
"Plugin Install Progre Done - FAILED - Resource Download http://<SNIP>/jetty-starter-jars-2.3.0.14.zip?use_mirror= Ben |
#26
|
||||
|
||||
What's the java version? When I see this fail, it's typically because of an older Java. My server runs Java 8, and I just tested this, and it didn't fail. Sometimes sourceforge (where these are stored) will fail, and simply retrying will work.
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#27
|
|||
|
|||
I was running 1.8.30 and it failed to download (multiple times last night and this morning). I updated to 1.8.111 and the download worked and the jetty server seems to be up. I also installed the SageTV web interface and mobile web interface but I haven't gotten the web interface working as I am getting the below error:
HTTP ERROR: 503 Problem accessing /sage/Home. Reason: SERVICE_UNAVAILABLE Powered by Jetty:// Same goes for /sage. This happens both when attempting to connect from the SageTV server (via localhost) and from another system via the IP address. Thoughts? Ben Last edited by benjamintm; 01-08-2017 at 02:07 PM. |
#28
|
||||
|
||||
Quote:
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#29
|
||||
|
||||
For the people having issues... I would look at the sagetv_0.txt log file when sagetv starts... Jetty will logs the fact that it is deplying applications (or not)... and likely, if you can't access the /sage app, etc, either Jetty is not deploying them, or it runs into an error (filesystem permissions, etc).
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#30
|
|||
|
|||
Is Jetty still the best solution for the web UI for Sage or is there something better these days - even going to Apache2 since Sage seems to be moving towards Linux, at least for the server side.
__________________
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 |
#31
|
||||
|
||||
Jetty is fine. It does what it needs to do, and most cleanly, runs within the same java jvm that's running sage, so it just keeps things clean and simple. it just happened to work so well that there was no reason to upgrade it over the years, and java changes have left the old version sort of in the dust.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#32
|
||||
|
||||
I double we'll move away from a Java web server, since much of what the web apps do, require it to be running in the same vm... And I don't think SageTV is moving to linux only, just no-one has stepped up to maintain the windows native parts yet... but jusjoken is still build Windows versions as required... I hope that some day, and window person will come along and maintain the windows specific parts.
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#33
|
|||
|
|||
Quote:
__________________
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 |
#34
|
||||
|
||||
Quote:
That said, I'm pretty sure myself and others have mentioned quite a few times that a 64-bit windows build is not even being worked on, simply because the amount of native code on windows is so significant, with no devs comfortable enough to even look at, and more importantly, some things - like DirectShow - may not even function the same in 64-bit (you need to use specific 64-bit DirectShow filters/drivers to access DirectShow from a 64-bit application, and there are not very many 64-bit DirectShow filters/drivers).
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#35
|
||||
|
||||
Quote:
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#36
|
||||
|
||||
Quote:
![]()
__________________
Jeffrey Kardatzke Founder of SageTV |
#37
|
|||
|
|||
Quote:
I certainly would need to learn a lot more of the internal workings but some day i may take a shot a this but i think we should have a 32 bit client and a separate 64 bit server for windows if that will make this simpler.. then again it may be way over my head but that never stopped me before ![]() k
__________________
If you wish to see what I am up to and support my efforts visit my Patreon page |
#38
|
||||
|
||||
Quote:
This is the reason I suggested back before open sourcing an archetecture that wold allow for a seperate process for each miniclient. Something that would essentially combine the SageTVClient parts to communicate with the server process, and the MiniServer parts to communicate with a miniclient. This would really be the only way for it to serve a large number of miniclients and remain 32-bit. Alternatively, a very stripped down version of the server could be made to run 64-bit, and go without just about all the native bits - but lose all the features that the native bits provided (direct hardware tuner access, usb-uirt, power management, etc). The end result being that if you only used network encoders, it'd be fine, and you could perhaps still run a 32-bit instance as a network encoder for direct hardware access. Both of these solutions end up being far more complicated to manage than using a linux 64-bit server, but architecturally, this are the only ways I see going forward to try to improve the capabilities of the windows server. Of course, I've also recommended shifting the android minclient to a full client architecture - which would also alleviate the need for a large heap if using android clients (which are the only 'new' clients out there).
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#39
|
||||
|
||||
It should be pretty easy to get it compiled for 64-bit on Windows if you don't include playback or recording...so a service-only type of build. You'd then use a local network encoder for handling all of the capture stuff (and you'd have to change SageTV.exe's use of mutexes to allow running multiple copies of SageTV server on one machine). Then use SageTVClient locally like has always been done for playback...or across the network. The part that benefits from 64-bit is the Java portion...which is the easiest to deal with in 64-bit world.
![]() It also probably wouldn't be all that hard to get capture working properly in 64-bit, as long as the drivers are there for the devices. There's definitely a lot less code for capture vs. playback; and much of the complex code there is shared across both platforms (i.e. the TS parsing/remuxing) so it's already been vetted for 64-bit compatibility.
__________________
Jeffrey Kardatzke Founder of SageTV |
#40
|
|||
|
|||
Quote:
Quote:
Ben |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Plugin: SageTV Web Interface V2 for Jetty | jreichen | SageTV Customizations | 256 | 02-09-2014 08:05 AM |
Strange problem with the SageTV Jetty webserver, always returns 404 | hagur | SageTV Customizations | 3 | 11-01-2011 01:20 PM |
Problems with the Jetty webserver plugin and SageTV web interface | hagur | SageTV v7 Customizations | 0 | 06-06-2011 05:28 PM |
Upgrading Jetty from SageTV 6 to SageTV 7 | jreichen | SageTV v7 Customizations | 36 | 03-21-2011 10:07 PM |