EPG Server Issues With Latest Linux Code

[Taddeusz]

Not sure where to put this since I'm not sure if this is code or EPG server related. My Windows SageTV server is still working but builds on both 32-bit & 64-bit are getting "error connecting" when I try to load load new listings for a tuner. Key is in place. Not sure what's happening.

[stuckless]

Originally Posted by Taddeusz

Not sure where to put this since I'm not sure if this is code or EPG server related. My Windows SageTV server is still working but builds on both 32-bit & 64-bit are getting "error connecting" when I try to load load new listings for a tuner. Key is in place. Not sure what's happening.

Since I think Jeff will ask is there anything in the sagetv_0.txt log file that might show an error?

[Taddeusz]

Originally Posted by stuckless

Since I think Jeff will ask is there anything in the sagetv_0.txt log file that might show an error?

Nothing that I can see.

[Taddeusz]

Is there a particular error that shows up when your key isn't being accepted by the server? Although the same key has been and is working fine on my Windows server. And had been working in Linux up to a couple days ago after I rebuilt my test server vm and synced my personal sagetv fork with the master.

[Narflex]

So I did not actually test the updated code I did on Linux where I had it pull the license key from the 'activkey' file directly rather than passing it as a parameter on the command line to it (after reading it from the activkey file). So there's a chance I made a mistake there...but the code was really simple, so it should be correct. Maybe you have extraneous whitespace in the file? (I don't think I had it strip that off...it'd be good to change that).

And there should be some kind of error in your log file when it's trying to connect...if it's giving you on error in the UI, then it'll log something as well.

[Narflex]

If you just look at the last change made to java/sage/WarlockRipper.java you can see the code change I'm referring to.

[Taddeusz]

Originally Posted by Narflex

If you just look at the last change made to java/sage/WarlockRipper.java you can see the code change I'm referring to.

Yes, I saw the change. After some testing I added .trim() to the end and that seems to have fixed it.

[Taddeusz]

Just submitted a pull request.