Reply to thread

Message

<blockquote data-quote="RonD" data-source="post: 1109932" data-attributes="member: 117536">Unfortunately the log files only/mostly show PowerScheduler activity from 2014-11-13 06:09:03 to 2014-11-13 07:50:53 (3.5 MB of log data), no info about SchedulesDirect. To find what causes SD problems we will need to get focused log activity showing what happens when you run SD-plugin. Try the following,setup SD-plugin to “Force full guide update”goto SetupTV &gt; Manual, press &quot;stop&quot;delete TVService.log and TVService-Error.log, so tvserver will start new log files when you startpress &quot;Start&quot;, tvserver will start running, trigger SD-pluginlet this run until SD is done and upload the 2 log files, on my system when SD runs for daily background EPG update it generates log files like the following, yours may be a bit different since you did manual &quot;trigger&quot;. Not sure how long this will take, depends on number of channels, days, etc. Maybe 5-10 minutes?? For initial setup/debug you can limit SD to 2-3 days.[2014-11-13 06:35:04,002] [Log&nbsp; ] [SchedulesDirect EPG Client] [INFO ] - Starting EPG refresh job on thread #24end of my SD activity, looks like this[2014-11-13 06:41:06,864] [Log&nbsp; ] [SchedulesDirect EPG Client] [INFO ] - Last program entry in database was 11/25/2014 6:00:00 AM, now 11/26/2014 6:00:00 AM[2014-11-13 06:41:07,270] [Log&nbsp; ] [SchedulesDirect EPG Client] [INFO ] - Scheduling next poll for 11/13/2014 2:37:04 PM[2014-11-13 06:41:07,380] [Log&nbsp; ] [SchedulesDirect EPG Client] [INFO ] - Electronic Program Guide now updated through 11/26/2014 6:00:00 AMIf you use notepad to open TVService.log, you will need to open/close the log file several times, look at end of file, to see when SD-plugin is done. Other editors like notepad++ will see changes to the log file and ask if you want to &quot;reload&quot;.</blockquote>

[QUOTE="RonD, post: 1109932, member: 117536"] Unfortunately the log files only/mostly show PowerScheduler activity from 2014-11-13 06:09:03 to 2014-11-13 07:50:53 (3.5 MB of log data), no info about SchedulesDirect. To find what causes SD problems we will need to get focused log activity showing what happens when you run SD-plugin. Try the following, setup SD-plugin to “Force full guide update” goto SetupTV > Manual, press "stop" delete TVService.log and TVService-Error.log, so tvserver will start new log files when you start press "Start", tvserver will start running, trigger SD-plugin let this run until SD is done and upload the 2 log files, on my system when SD runs for daily background EPG update it generates log files like the following, yours may be a bit different since you did manual "trigger". Not sure how long this will take, depends on number of channels, days, etc. Maybe 5-10 minutes?? For initial setup/debug you can limit SD to 2-3 days. [2014-11-13 06:35:04,002] [Log ] [SchedulesDirect EPG Client] [INFO ] - Starting EPG refresh job on thread #24 end of my SD activity, looks like this [2014-11-13 06:41:06,864] [Log ] [SchedulesDirect EPG Client] [INFO ] - Last program entry in database was 11/25/2014 6:00:00 AM, now 11/26/2014 6:00:00 AM [2014-11-13 06:41:07,270] [Log ] [SchedulesDirect EPG Client] [INFO ] - Scheduling next poll for 11/13/2014 2:37:04 PM [2014-11-13 06:41:07,380] [Log ] [SchedulesDirect EPG Client] [INFO ] - Electronic Program Guide now updated through 11/26/2014 6:00:00 AM If you use notepad to open TVService.log, you will need to open/close the log file several times, look at end of file, to see when SD-plugin is done. Other editors like notepad++ will see changes to the log file and ask if you want to "reload". [/QUOTE]

Verification