• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

auto-schedule-restore not restoring schedule after retuning

S

StevenR

New Member
Hi,

As the subject suggests, I've done retunes on my box twice in the last few months (due to Freeview channel changes) and on both occasions the custom firmware hasn't restored my schedule. Is this still supposed to work automatically?

The schedule is backing up overnight on a daily basis so I've just restored manually from the backup both times, but it's a bit of a faff as my box isn't permanently connected to my router.

Thanks
Steven
 
If you have Disable-OTA package that adds an on/off timer when the box is rebooted after the retune. The schedule is not empty, so schedule restore does not restore it.
 
Sorry yeah I forgot to say I powered off the box completely (twice) and waited for the hard drive to stop before turning back on.

The last backup wasn't empty.
 
StevenR said:
I've done retunes on my box twice in the last few months (due to Freeview channel changes) and on both occasions the custom firmware hasn't restored my schedule. Is this still supposed to work automatically?
Click to expand...
Yes. Run the fix-flash-packages diagnostic.
Owen Smith said:
If you have Disable-OTA package that adds an on/off timer when the box is rebooted after the retune. The schedule is not empty, so schedule restore does not restore it.
Click to expand...
Of course, any sane person would have designed it to ignore any such entries so created... which is why that is exactly how it works, and not how you say.
 
Owen Smith said:
Do you have the Disable-OTA package installed and configured to add an on/off timer event?
Click to expand...
No, it's not installed.

prpr said:
Yes. Run the fix-flash-packages diagnostic.

Of course, any sane person would have designed it to ignore any such entries so created... which is why that is exactly how it works, and not how you say.
Click to expand...
Thanks for the reply. When I first loaded the web interface yesterday it said my box had crashed (couldn't remember when but according to crash.log it was last Thursday evening) and that I should run fix-flash-packages, which I did.

Once the box has stopped recording I'll try another retune, after which it sounds like it should work OK?
 
StevenR said:
When I first loaded the web interface yesterday it said my box had crashed (couldn't remember when but according to crash.log it was last Thursday evening) and that I should run fix-flash-packages, which I did.
Click to expand...
To prevent having this hassle run the plugin_autodisable/off diagnostic.
Once the box has stopped recording I'll try another retune, after which it sounds like it should work OK?
Click to expand...
Maybe.
 
prpr said:
Of course, any sane person would have designed it to ignore any such entries so created... which is why that is exactly how it works, and not how you say.
Click to expand...
It didn't used to ignore such entries when I tried auto-schedule-restore a number of years ago. I had to choose, and decided to stick with disable-ota. Sounds like the clash was fixed while I wasn't paying attention.
 
prpr said:
To prevent having this hassle run the plugin_autodisable/off diagnostic.
Click to expand...
I did that on someone's advice in the last year or so and it's been much better. My boxes report packages crashing and being disabled on an almost monthly basis, I was getting fed up logging in to the web UI just to re-enable them. In the early days I reported these crashes on hummy.tv but none of them ever seemed to get fixed so I gave up.
 
StevenR said:
It worked perfectly that time!
Click to expand...
Good stuff. Thanks for confirming the problem is fixed.
Owen Smith said:
In the early days I reported these crashes on hummy.tv but none of them ever seemed to get fixed
Click to expand...
Probably nothing could be done as the crash was caused by bugs in the Humax code.
Owen Smith said:
It didn't used to ignore such entries when I tried auto-schedule-restore a number of years ago. I had to choose, and decided to stick with disable-ota. Sounds like the clash was fixed while I wasn't paying attention.
Click to expand...
That was changed on 4 Sep 2014 - that's over 11 years ago. It's probably worth checking before pontificating on such out of date information.
 
prpr said:
Probably nothing could be done as the crash was caused by bugs in the Humax code.
Click to expand...
I didn't realise crashes in the Humax code could be seen as crashes in packages. I assumed they all run as separate unix processes so it would always be clear which one had crashed and be correctly atributed.
prpr said:
That was changed on 4 Sep 2014 - that's over 11 years ago. It's probably worth checking before pontificating on such out of date information.
Click to expand...
I consider myself chastised and will sit on the naughty step. I hadn't realised it was that long ago!
 
Owen Smith said:
I didn't realise crashes in the Humax code could be seen as crashes in packages.
Click to expand...
They aren't.
I assumed they all run as separate unix processes so it would always be clear which one had crashed and be correctly atributed.
Click to expand...
They do and are.
But the thing that crashes the machine, and triggers the crash protection stuff which necessitates fix-flash-packages, is when the humaxtv binary abends. This is because init is configured to reboot the machine if this happens.
I'm unaware of any bugs in packages which crash causing this effect.
 
Owen Smith said:
I didn't realise crashes in the Humax code could be seen as crashes in packages. I assumed they all run as separate unix processes so it would always be clear which one had crashed and be correctly atributed.
Click to expand...
The disablement is to prevent a continuous crash-reboot cycle, and triggered if there are two crashes in quick succession for any reason... in case alpha testing caused it. Otherwise it could be difficult to recover from.

Of course, there are occasions when functionality in the flash packages becomes compromised, and fix-flash-packages is a means to restore that functionality, so anyone setting auto-disable off needs to be aware of that.
 
You must log in or register to reply here.
Back
Top