V4.1.10 MVP - stv selection not surviving power cycle

[hchucky]

I just upgraded to v4.1.10 from v4.1.9 and now when I select a new stv in the MPV everything works fine until I power down the MVP and power it back up. When it comes back online the stv is reset to its default.

This was not an issue before the upgrade. I upgraded to 4.1.10 by simply installing over the top of 4.1.9.

The stv that I am using is nielm's Dynamic Customisable Main Menu.

Is anyone else seeing this issue?

HChucky

[michelkenny]

Try restarting the SageTV Service. I experienced this problem in a few different versions and it magically dissapeared when I was trying to find out what the problem was.

[rickw]

Originally Posted by hchucky

I just upgraded to v4.1.10 from v4.1.9 and now when I select a new stv in the MPV everything works fine until I power down the MVP and power it back up. When it comes back online the stv is reset to its default.

This was not an issue before the upgrade. I upgraded to 4.1.10 by simply installing over the top of 4.1.9.

The stv that I am using is nielm's Dynamic Customisable Main Menu.

Is anyone else seeing this issue?

HChucky

This the only issue I've had with 4.1.10. (Thankfully!) Lost power last night because of a storm and the MVP came back to the default.

I'll try restarting the service tonight.

Rick...

[hchucky]

I am not running in service mode but I will try restarting SageTV.exe tonight and see if that makes a difference.

HC

[Opus4]

This is one of those things that SageTV hasn't been able to find a reproducible case so they can find & fix the problem. If this is happening & you can reproduce it, please set the debug_logging=TRUE property (exactly as shown, CAPS too). Email the log files and your properties files to betatest at sagetv.com -- also include sage.properties and any properties files in the 'clients' subdirectory.

If you are testing the beta, then rather than just finding a way around this issue, please help by submitting the files mentioned above so that it can be fixed & not happen other users in the future. Thanks for your help.

- Andy

[larryf]

Too late for me to get the log files, but it happened to me also. Did it several times over several upgrades, not just the latest...

I fiddled a lot, but what seemed to fix it was a reboot (which stopped/started the service obviously).

A side note, I do like the progress Sage has made with the MVP. Later versions are stable and the 'stuttering' has gone away. I used to keep the server at 10/half to mask the problem, but now have it at 100/full with no dropouts or glitches.

If it happens again I will get the logs.

Larry

[hchucky]

I did not get a chance to look at this issue last evening. It should still be present so I will enable debug and create some logs and send them in this evening.

HC

[michelkenny]

Originally Posted by Opus4

This is one of those things that SageTV hasn't been able to find a reproducible case so they can find & fix the problem. If this is happening & you can reproduce it, please set the debug_logging=TRUE property (exactly as shown, CAPS too). Email the log files and your properties files to betatest at sagetv.com -- also include sage.properties and any properties files in the 'clients' subdirectory.

If you are testing the beta, then rather than just finding a way around this issue, please help by submitting the files mentioned above so that it can be fixed & not happen other users in the future. Thanks for your help.

- Andy

It happened to me twice. For both times I went to enable debugging to see if I could gather some info, restarted the service, but couldn't reproduce the problem anymore

[malbec]

Ditto here, but I just gave up and used the "hack" describe in another post on this same issue.

Back up the default STV (if you care) and rename the customized STV you want to the default STV name ... SageTV3.xml.

[hchucky]

Well I shut down the Sage server and added the debug line in the config file and restarted. The good and bad news is the problem is now resolved. I changed the stv on the MVP and power cycled it several times and the stv sticks every time.

Next time I upgrade I'll add the debug line before the upgrade and see if I can capture something meaningful that way.

HC

[marneb17]

Aloha,
I also tried to "capture" the bug, but as soon as I enabled logging, the STV would stick!

Marneb