Reply to thread

Message

<blockquote data-quote="rsbrux" data-source="post: 189580" data-attributes="member: 49539">Hi Bavarian,Thanks for looking at this.&nbsp; If WebEPG was finished at 5:32, why was the system still running at 8:30?Based on these entries at the end of MediaPortal.log:Hibernation should have taken place at 5:47.&nbsp; Why didn't it?It looks more to me as though the DB is responsible.It was still active at 5:51 and was also the source of the only error shown in Error.log (admittedly a consequence of a WebEPG error).Still, grabber errors are bound to occur from time to time, and shouldn't interfere with other key system functions.P.S.&nbsp; The symptom appeared again this morning (with SVN 16125):&nbsp; system still on at 8:30, although none of the logs show any activity since 6:00.&nbsp; Once again there was a grabber error, but I am no longer convinced that it has anything to do with the DB error.Perhaps I&nbsp; misunderstood what you were trying to say about the EPG.&nbsp; I see that the DB error reported in &quot;error.log&quot; coincides with the end of data import in &quot;epg.log&quot;.&nbsp; What can we conclude from this?Once again, the last activity shown is:BTW, the TV Guide appears to have all but the last two entries shown in &quot;epg.log&quot;.</blockquote>

[QUOTE="rsbrux, post: 189580, member: 49539"] Hi Bavarian, Thanks for looking at this. If WebEPG was finished at 5:32, why was the system still running at 8:30? Based on these entries at the end of MediaPortal.log: Hibernation should have taken place at 5:47. Why didn't it? It looks more to me as though the DB is responsible. It was still active at 5:51 and was also the source of the only error shown in Error.log (admittedly a consequence of a WebEPG error). Still, grabber errors are bound to occur from time to time, and shouldn't interfere with other key system functions. P.S. The symptom appeared again this morning (with SVN 16125): system still on at 8:30, although none of the logs show any activity since 6:00. Once again there was a grabber error, but I am no longer convinced that it has anything to do with the DB error. Perhaps I misunderstood what you were trying to say about the EPG. I see that the DB error reported in "error.log" coincides with the end of data import in "epg.log". What can we conclude from this? Once again, the last activity shown is: BTW, the TV Guide appears to have all but the last two entries shown in "epg.log". [/QUOTE]

Verification