RS auto scheduling long past events

[MymsMan]

A test 'Schedule Matching entries' rule (that I intended to Disable) fired and triggered a bunch of Schedule entries for events long past (plus a few current ones)

BBC NEWS
[Thu, 14 Dec 2017 03:30:00 +0000 / 00:30]
Click
Childs Play: The tech show looks at Generation U for Universal, and asks how children are learning about technology and staying safer online. Also in HD. [S]
= Scheduled successfully (event). ( / title Click action scheduleevents) =
BBC NEWS
[Sat, 16 Dec 2017 01:30:00 +0000 / 00:30]
Click
Click investigates the weird world of quantum computing, Spencer meets arts legend Marina Abramovic and Dan reviews the leading 360 cameras. Also in HD. [S]
= Scheduled successfully (event). ( / title Click action scheduleevents) =
BBC NEWS
[Sat, 16 Dec 2017 03:30:00 +0000 / 00:15]
Click
A comprehensive guide to all the latest gadgets, websites, games and computer industry news. Also in HD. [S]
= Scheduled successfully (event). ( / title Click action scheduleevents) =
...

Why? It should never schedule past events and why were they still in the database

 

[peterworks]

Does running diagnostic epgrange give a clue ?

 

[MymsMan]

Does running diagnostic epgrange give a clue ?

Not really since it is the RS version of the EPG rather than the Humax copy that is the issue.

 diag epgrange
Running: epgrange
Tue Feb 20 20:50:00 GMT 2018
Thu Mar 22 23:55:00 GMT 2018

The diag page failed to fully populate the log file list, presumably because the log was being rotated at the time

2    in procedure 'file' called at file "/mod/webif/html/diag/diag.jim", line 144
1    /mod/webif/html/diag/diag.jim:144: Error: could not read "/mod/tmp/auto.log": No such file or directory

Refreshing the page worked so I must have caught a timing window.

 

[af123]

I'm not sure what's going on here, I'll check the databases.

 

[af123]

There was a table that needed repairing and that was stopping the expiry process... running now, should be sorted soon.