V7 to V9 upgrade - error - No encoders can tune the selected station

[mrcandu]

Hi all

Thought i'd have a crack at upgrading from v7 to 9....

Using the Windows installer everything seemed to go through fine, but when I start the service and try to tune a channel from any client, I get the message "No encoders can tune the selected station".

I have tried restarting the service / pc, as well as running Sage locally with the service disabled....
Interestingly I have had channel playback working a twice, once locally and once from Placeshifter, but I can't seem to replicate the fix or find any pattern to it.

My current thoughts are that its either a permissions issue, or something related to a delay in a service starting.

Prior to upgrade I was on java 1.6.10.

Log attached - any help appreciated.

Thanks,

Mat.

[Narflex]

Not sure from the log. Check Setup Video Sources to make sure all your encoders are setup and that the channel lineups are valid and that they are listed as functioning.

[mrcandu]

Originally Posted by Narflex

Not sure from the log. Check Setup Video Sources to make sure all your encoders are setup and that the channel lineups are valid and that they are listed as functioning.

Thanks - Sources and lineups are as they should be.

I left the service running for an hour or so and tried the lineup again - everything worked fine.

I have replicated this a couple of times now - have restarted the service and same error occurs, but continue trying the channels every minute or so until it works - will post a log shortly.

Could Sage or Java being doing something on a fairly infrequent basis that causes things to work again?

[mrcandu]

Replicated the above..... log attached.

So the question is did anything significant happen between 17:22, when the error last occurred and 17:25 (ish) when the channel tuned successfully?

Thanks for assistance - I'll continue to try and figure out if anything is happening outside the application.

Mat.

[mrcandu]

Not entirely sure what to look for, but this seems significant:

The first event of this kind happened at 17:23

Sat 12/24 17:23:53.528 [Seeker@985bef] Seeker adding new Encoder: Hauppauge WinTV MOD7700 DVB-T Capture (Dev2 Path1)

Fired up the service at 17:06

[Monedeath]

Originally Posted by mrcandu

Prior to upgrade I was on java 1.6.10.

Wasn't there an upgrade in the Repo to increase the Minimum Java Version to something like Java 7.5? From this, it looks like MrCandu is on 6.10.

So upgrading to Java 7 at the least might help.

Although I'd then be intrigued as to how this is the only issue so far.

[trallyus]

Did you install the the LAV Filters decoder pack at
https://github.com/Nevcairiel/LAVFilters/releases


Also since I believe sage tv is still 32 bit you have to install the 32 bit decoders instead of the 64 bit versions for sage to find them.

[mrcandu]

Thanks for the help all.

Originally Posted by Monedeath

Wasn't there an upgrade in the Repo to increase the Minimum Java Version to something like Java 7.5? From this, it looks like MrCandu is on 6.10.

So upgrading to Java 7 at the least might help.

Although I'd then be intrigued as to how this is the only issue so far.

Using SageTV v7, i'm running Java 6.10. If I upgrade to Sage v9, Java 7.x is installed for min requirements, so that all seems fine to me.

Originally Posted by trallyus

Did you install the the LAV Filters decoder pack at
https://github.com/Nevcairiel/LAVFilters/releases


Also since I believe sage tv is still 32 bit you have to install the 32 bit decoders instead of the 64 bit versions for sage to find them.

I don't think its a playback / rendering issue, SageTV just doesn't seem to find the tuners until 20 mins or so after the service starting.

I have reverted back to the v7 install for the time being, but will find some time later today to continue looking at this.

One thing I thought I noticed is that the v9 service was consuming much more memory at startup than the v7 install - Will verify later and provide some stats.
My machine is fairly low on resources - its just an Atom 330 with 2gb of RAM.
Windows 10 is not exactly snappy on it, but I have never had any issues with v7.
I wonder if its something in Java v7 or Sage v9, that is consuming that bit more memory that just pushes the server over the edge.

I'll also have a look into when v7 fires the first "Seeker adding new Encoder" event.
This seems to be the thing that happened on the v9 install after 20 mins that got things working again.

[Monedeath]

I know that when I did my initial upgrade to V9 from V7, it took upwards of a half hour for most of the tuners to come online and become available to SageTV.

The Issue only existed on that first startup, tuners were available in a much more reasonable time frame after that. I imagine a lot of that delay was SageTV parsing through the v7 wiz.bin and upgrading it to the v9 format.

So if you've been freaking out after that first startup, and reverted back before trying a second one later on. That is potentially some of what you're seeing.

[Narflex]

For some reason it is taking 17 minutes to verify that all of your recordings are valid and the durations of them are correct. Not sure why though...

[mrcandu]

Originally Posted by Monedeath

I know that when I did my initial upgrade to V9 from V7, it took upwards of a half hour for most of the tuners to come online and become available to SageTV.

The Issue only existed on that first startup, tuners were available in a much more reasonable time frame after that. I imagine a lot of that delay was SageTV parsing through the v7 wiz.bin and upgrading it to the v9 format.

So if you've been freaking out after that first startup, and reverted back before trying a second one later on. That is potentially some of what you're seeing.

Originally Posted by Narflex

For some reason it is taking 17 minutes to verify that all of your recordings are valid and the durations of them are correct. Not sure why though...

Thanks both....
I didn't really get anywhere with finding a proper fix for this - It didn't matter how many times I restarted the service or how long I let it run for.
I managed to pinpoint that it was something in the wiz.bin or properties migration that was causing the problem.
A solution was to let Sage 9 create both files from scratch - everything runs fine now.
Shame I can't keep the db, but a least i'm up and running!

Mat.