Auto-schedule-restore : not restoring

[bob_a_builder]

My T2 has entered the dodgy stage lately, randomly crashing and restarting in the setup mode - did put a new drive in etc, seemed better for a week or 2 - now just done it again
It would be easier to live with if the Auto-schedule-restore package would do what it supposed to - but its not for me

Checking via Web-If after the restart - I get the pink warning message box telling me Auto-schedule-restore has run and if I check the activity.log after the restart I can see a number of entries like this - time stamped to post re-start time - and which match my rough memory of scheduled stuff

" 23/09/2020 14:46:31 - Scheduled Rhod Gilbert's Work Experience @ 1600462800"

But checking the Schedule section still shows nothing listed, I rebooted again to be sure but still nothing listed

Does anyone have any ideas/suggestion please ?

p.s. I have been able to do the manual Restore from the Backup/Restore tab of the Schedule page
i.e. auto-2020-Sep-23-02:08 ( Wed Sep 23 02:08:02 2020 BST)

 

[MymsMan]

Did you reboot after the schedule was restored?

 

[Black Hole]

My T2 has entered the dodgy stage lately, randomly crashing and restarting in the setup mode - did put a new drive in etc, seemed better for a week or 2 - now just done it again

Never mind all the other nonsense - see Steps for Resolving HDR-FOX Crash/Reboot Issues (click).

It would be easier to live with if the Auto-schedule-restore package would do what it supposed to - but its not for me

There do seem to be some problems with this, and we have our hands tied at the moment due to the indisposition of af123. A manual restore might be the best bet at the moment.

 

[bob_a_builder]

@ MymsMan : - Thanks - Yes I did do that - didn't mention in initial post but in an edit a few mins later

To be more specific , most of my earlier problems were with it stuck in boot loop issue, the factory default option equiv of system flush at time of drive format , and new drive seem to have resolved that between them ( not a 'new' drive just a random 2.5" sata one I had to hand, non pipeline)
Now its just the random (not too often) going back to initial start up i.e. retune etc

Will carry on with the manual restores for now then - Thanks

 

[/df]

My T2 has entered the dodgy stage lately, randomly crashing and restarting in the setup mode
...
It would be easier to live with if the Auto-schedule-restore package would do what it supposed to - but it's not for me

Checking via Web-If after the restart - I get the pink warning message box telling me Auto-schedule-restore has run and if I check the activity.log after the restart I can see a number of entries like this - time stamped to post re-start time - and which match my rough memory of scheduled stuff

" 23/09/2020 14:46:31 - Scheduled Rhod Gilbert's Work Experience @ 1600462800"
...
p.s. I have been able to do the manual Restore from the Backup/Restore tab of the Schedule page
...

This is pretty weird since the same code is used in both cases, so if (as appears) auto-schedule-restore is running, and rsvsync (which completes the restore on rebooting, and might have been clobbered by a reset) must be working, there's no obvious reason why the auto-schedule-restore restore would fail. Probably we should check /mod/tmp/rsvsync.log.

One question with auto-schedule-restore is why its backup is stored in flash, even though the package files are on the hard disk. This means that after an uncommanded reset (you turn on: instead of a programme, you get the installation wizard or a message saying "no channels"), when the writable flash may have been erased, the backup may not be found. But that doesn't appear to be the issue here since the backup appears to have been readable.

 

[Black Hole]

If anyone has time to contribute to the investigation, (presuming you have the auto-schedule-restore package installed) an auto-restore can be (should be) triggered by rebooting after emptying out your recording schedule (make a manual backup using WebIF >> Scheduled Events >> Backup/Restore first).

The auto-restore event should then trigger another reboot automatically. If it doesn't reboot, try rebooting manually.

A known issue is if your schedule is intentionally empty. If your schedule is empty and a daily backup has been made of an empty schedule, auto-restore will restore an empty schedule and therefore initiate another auto-restore at next boot.

 

[bob_a_builder]

The rsvsync log for the time in question shows this - which look pretty similar to the later entries when I did the manual backup

120	Wed Sep 23 14:46:57 2020: Final schedule entries: 15
119	Wed Sep 23 14:46:57 2020: Slots: +0,+1,+2,+3,+4,+5,+6,+7,+8,+9,+10,+11,+12,+13,+14
118	Wed Sep 23 14:46:57 2020: Restoring any favourites.
117	Wed Sep 23 14:46:54 2020: Moving pending entry 14 to spare slot 14
116	Wed Sep 23 14:46:54 2020: Moving pending entry 13 to spare slot 13
115	Wed Sep 23 14:46:54 2020: Moving pending entry 12 to spare slot 12
114	Wed Sep 23 14:46:54 2020: Moving pending entry 11 to spare slot 11
113	Wed Sep 23 14:46:54 2020: Moving pending entry 10 to spare slot 10
112	Wed Sep 23 14:46:54 2020: Moving pending entry 9 to spare slot 9
111	Wed Sep 23 14:46:54 2020: Moving pending entry 8 to spare slot 8
110	Wed Sep 23 14:46:54 2020: Moving pending entry 7 to spare slot 7
109	Wed Sep 23 14:46:54 2020: Moving pending entry 6 to spare slot 6
108	Wed Sep 23 14:46:54 2020: Moving pending entry 5 to spare slot 5
107	Wed Sep 23 14:46:54 2020: Moving pending entry 4 to spare slot 4
106	Wed Sep 23 14:46:54 2020: Moving pending entry 3 to spare slot 3
105	Wed Sep 23 14:46:54 2020: Moving pending entry 2 to spare slot 2
104	Wed Sep 23 14:46:54 2020: Moving pending entry 1 to spare slot 1
103	Wed Sep 23 14:46:54 2020: Moving pending entry 0 to spare slot 0
102	Wed Sep 23 14:46:54 2020: Opening /var/lib/humaxtv/rsvp.db
101	Wed Sep 23 14:46:54 2020: rsvsync starting, version 1.1.13.

 

[bob_a_builder]

Have since run a 'fix-flash packages' from the diagnostic , and then done the , save back up of schedule, delete all scheduled events and reboot process
Done it twice, and scheduled events were auto restored OK both times - rsvsync log looks same as above

 

[Black Hole]

Sounds like it works as intended then, so long as everything is installed properly and hasn't been killed by a double crash.