Well spotted. I think you are right. Now that I've taken your advice and removed both grabbing options from the DVB EPG section, leaving everything up to WebEPG, which grabs the EPG at 01:10, there should be very little likelihood of a conflict.I was looking at your log file again, and found the place where "TV Server" decided to stop. it is at:
2021-02-16 20:55:05,727 (line 7571). The error is an SQL error, and the text description is:
Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Is it possible that your SQL EPG update program interfered with TV Server's access to the database?
-- from CyberSimian in the UK
Thanks for all of your help.