Mobile Web Search Broken

[KarylFStein]

I'm not sure when this broke, but know it used to work. In the mobile web interface when I select Search Airings, Search Recordings, Listings or HD Listings I get the following error:

PWC6033: Unable to compile class for JSP PWC6199: Generated servlet error: The import java.util.Arrays cannot be resolved PWC6197: An error occured at line: 14 in the jsp file: /WEB-INF/tags/sage/functions/collections/ArrayToList. PWC6199: Generated servlet error: Arrays cannot be resolved.

The regular web interface (non-mobile view) works fine with searches and listings.

[KarylFStein]

I get a similar error trying to schedule a recording on the mobile interface too .

[stuckless]

Are you running Java 1.8... this sounds like the same problems that we have with the "/apps" on Java 1.8 and this version of Jetty.

[KarylFStein]

Originally Posted by stuckless

Are you running Java 1.8... this sounds like the same problems that we have with the "/apps" on Java 1.8 and this version of Jetty.

Yes, I just upgraded to Java 1.8 because of the Phoenix/BMT updates . Is it possible to load an earlier version of a plugin? I suppose I can just use the "desktop" web interface as it works in that.

[stuckless]

Originally Posted by KarylFStein

Yes, I just upgraded to Java 1.8 because of the Phoenix/BMT updates . Is it possible to load an earlier version of a plugin? I suppose I can just use the "desktop" web interface as it works in that.

No we can't "roll back" to an earlier version... but, I am working on an updated WebServer plugin... hopefully I can have "something" in the next couple weeks.

[KarylFStein]

Originally Posted by stuckless

No we can't "roll back" to an earlier version... but, I am working on an updated WebServer plugin... hopefully I can have "something" in the next couple weeks.

No worries; we'll live. Thanks for all you do.

[Spartan]

*bump* this is still a thing. I just upgraded to SageTV 9 recently...

https://www.screencast.com/t/zLQBJEaUBCnQ

[stuckless]

Originally Posted by Spartan

*bump* this is still a thing. I just upgraded to SageTV 9 recently...

https://www.screencast.com/t/zLQBJEaUBCnQ

Sadly, I don't see these issues getting fixed, so much as we move to new web technology. I have looked at upgrading Jetty, and it's not easy and ends up breaking other things... and my intention is really to create a new "web" platform for SageTV and then re-implementing features as we build it out.

[NetworkGuy]

Originally Posted by stuckless

... and my intention is really to create a new "web" platform for SageTV and then re-implementing features as we build it out.

I like the Web interface, but it is showing its age. It sounds like a great idea to build a new one.

[VCRUser]

I had been using the old (non-Jetty) webserver, but last night it started returning "not found" for the URL, with a message saying it's generated by Jetty. My server is on Java 1.7. Advice, please? I really depend on the webserver for certain functions.

[wayner]

The landing page that we used to use doesn't work but try going straight to the sage web URL - as in http://192.168.1.100:8080/sage/Home - and it is case sensitive

[VCRUser]

That's what I use when at home (but with my lan IP address substituted). I get "not found." That just happened around 3:00am, when it had been find just an hour before. Around that time (I was watching something via PlaceShifter), I got a sudden "service lost" message. Even after I got the service restarted on the server, the web access remained broken. Doing the equivalent thing now (not at home) but with the locator-string (which just got fixed yesterday) or the external IP likewise yields:

HTTP ERROR: 404
Problem accessing /sage/Home. Reason:

NOT_FOUND

Powered by Jetty://

[VCRUser]

I checked the log and see this:

[Tue Jun 06 04:30:45 EDT 2017] Server socket: java.net.BindException: Address already in use: JVM_Bind

Does that suggest a fix to anyone who knows how to interpret it?

[KarylFStein]

Originally Posted by VCRUser

I checked the log and see this:

[Tue Jun 06 04:30:45 EDT 2017] Server socket: java.net.BindException: Address already in use: JVM_Bind

Does that suggest a fix to anyone who knows how to interpret it?

Something is holding on to the same port that something else is trying to use. You said that you were using something pre Jetty so guessing that something else installed Jetty and they are fighting over port 8080?

[VCRUser]

I discovered that the original web server is now working on port 8081 (alway used 8080 before). I tried configuring the Jetty server for port 8082, but that didn't fix it. I think what may have happened is that the jetty server stomped on the original server on 8080 but the original server works on 8081 and for some reason the jetty server doesn't want to work on either 8080 or 8082. Maybe there is yet another port that Jetty will like, but I but at least I have a web server again.

[waynedunham]

Originally Posted by stuckless

Sadly, I don't see these issues getting fixed, so much as we move to new web technology. I have looked at upgrading Jetty, and it's not easy and ends up breaking other things... and my intention is really to create a new "web" platform for SageTV and then re-implementing features as we build it out.

If you need testers put me on the list. Especially during the summer I rely HEAVILY on the various remote SageTV interfaces while I'm up at my camp in Maine for several weeks at a time with no physical connection to my 2 servers. I use it to keep track of scheduled recordings (I use IR so that can be a LOT), address any system messages, etc.

I can access with my tablet, cellphone, or even my Mom's computer while I'm there via a WiFi Hotspot from my phone (she still has dialup.... UGH!)

[stuckless]

Originally Posted by waynedunham

If you need testers put me on the list. Especially during the summer I rely HEAVILY on the various remote SageTV interfaces while I'm up at my camp in Maine for several weeks at a time with no physical connection to my 2 servers. I use it to keep track of scheduled recordings (I use IR so that can be a LOT), address any system messages, etc.

I can access with my tablet, cellphone, or even my Mom's computer while I'm there via a WiFi Hotspot from my phone (she still has dialup.... UGH!)

I do think that most of the mobie UI does still work. I still use it myself, along with the main web server and BMT. My point was really, that what is "broken" will likey stay broken, since the cost to fix it is great. But you should still some mileage out what is there today.

[tvmaster2]

Originally Posted by stuckless

I do think that most of the mobie UI does still work. I still use it myself, along with the main web server and BMT. My point was really, that what is "broken" will likey stay broken, since the cost to fix it is great. But you should still some mileage out what is there today.

With the Phoenix Remote android app, everything works save for Mobile Web search, and Mobile Web listings. Too bad, since those can be useful when away from home. Otherwise, the android app mostly functions

[wayner]

The regular web UI works fine on a phone and since most phones have large screens these days you don't need specially designed web pages as much.

[tvmaster2]

Originally Posted by wayner

The regular web UI works fine on a phone and since most phones have large screens these days you don't need specially designed web pages as much.

the regular web U.I.? Sorry, not sure I understand. Are there guide listings? Do you have a screen grab of the page?