2012-02-21, 01:06 PM
I also had incomplete EPG twice back in January but since then I occasionally had missing Pending Recordings which could be related. Yesterday morning I found I only had 33 pending recordings after the overnight EPG update which I knew was wrong so did a manual update and then had 96 pending recordings. Before I posted the logs and database I wanted the log of a good EPG update to compare with the log of the faulty update and this morning there were 87 pending recordings. However when I looked at the NRecord.log it only found 1 recording was set! I do a nightly reboot at 02:20 and looked at the latest NRecord.log and there was a second EPG update at 02:24 which found 87 recordings.
Comparing the logs of the EPG update which found 1 recording and the one which found 87 the main difference is the number of Saved Listings for each channel. For the good EPG update most channels had well over 50 listings but for the faulty update listing below 10 were found. At the 02:20 reboot I make a backup of the database and that only has 1000 EPG entries but after the second EPG update there are 7837 entries. Another difference between the two updates is that the ndigitalhost log has the tuning info for the second EPG update but nothing for the original 02:00 update.
I am using 2.3.6 R1 patches. Enclosed is the database after the faulty EPG update and the logs covering both EPG updates.
Comparing the logs of the EPG update which found 1 recording and the one which found 87 the main difference is the number of Saved Listings for each channel. For the good EPG update most channels had well over 50 listings but for the faulty update listing below 10 were found. At the 02:20 reboot I make a backup of the database and that only has 1000 EPG entries but after the second EPG update there are 7837 entries. Another difference between the two updates is that the ndigitalhost log has the tuning info for the second EPG update but nothing for the original 02:00 update.
I am using 2.3.6 R1 patches. Enclosed is the database after the faulty EPG update and the logs covering both EPG updates.