Changes between Version 70 and Version 71 of FAQ


Ignore:
Timestamp:
Sep 21, 2013, 6:58:00 PM (4 years ago)
Author:
max
Comment:

Info for remote systems

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v70 v71  
    507507For MythTV 0.27 and later, this probably means that the '''augment_timezone''' component isn't adding timezones to your data, which is essential in 0.27+. You can confirm this by looking at ~/.shepherd/output.xmltv and seeing if show times look like "20130426100000" (bad) instead of "20130426100000 +1000" (good). The reason you're not getting timezones is probably that you don't have an up-to-date Shepherd installation: in particular, you may be missing the perl module '''Sort::Versions'''. Run '''tv_grab_au --update''' to confirm, and (if you're on Debian/Ubuntu) '''apt-get install libsort-versions-perl''' to fix. 
    508508 
    509 If that's not it, there is probably another reason why '''augment_timezone''' can't figure out which version of MythTV you have. Look in ~/.shepherd/log/shepherd.log (or whichever log file corresponds to Shepherd's most recent full run) under "augment_timezone". 
     509If that's not it, there is probably another reason why '''augment_timezone''' can't figure out which version of MythTV you have. One reason might be that you run Shepherd on a remote system. In that case, in ~/.shepherd/log/shepherd.log (or whichever log file corresponds to Shepherd's most recent full run), you'll see something like this: 
     510{{{ 
     511: ERROR: Could not find info to establish database connection to MythTV. 
     512: ERROR: Missing essential DB connection info. 
     513:          No valid response from MythTV. 
     514:          Assuming MythTV's timezone is "None". 
     515:          *** If this is wrong, guide data may be in wrong timezone! *** 
     516: 
     517:  - Target timezone is "None". No need to do anything. 
     518}}} 
     519And to fix, you will need to manually instruct '''augment_timezone''' which zone to stamp its times with. You can do this with the command to set default options, e.g.: 
     520{{{ 
     521tv_grab_au --component-set augment_timezone:timeoffset=Auto 
     522}}} 
     523The above tells '''augment_timezone''' to try to figure out your timezone based on its local system. If this isn't the same as your MythTV box, it will probably get things wrong. You can specify a timezone by replacing "Auto" in the above command with something like "+1000"; however, bear in mind this may become inaccurate during Daylight Savings Time changes. 
    510524 
    511525'''Data out by 1-3 hours'''