[mythtv-users] silence.py with 0.28

[Mark]

> -----Original Message-----
> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
> Of Roger Siddons
> Sent: Thursday, 29 October 2015 6:23 AM
> To: Discussion about MythTV
> Subject: Re: [mythtv-users] silence.py with 0.28
> 
> On Wed, 28 Oct 2015 02:54:46 -0000, Mark <perkins1724 at hotmail.com>
> wrote:
> 
> >
> > With the patch I get:
> > 2015-10-28 13:13:33.488855 D [20389] Python Database Connection Trying
> > database credentials from: /home/mythtv/config.xml
> > 2015-10-28 13:13:33.544067 I [20389]  mythcommflag:
> > 2015-10-28 13:13:33.565025 I [20389]  mythcommflag: Seeking chanid
> > 1022, starttime 2015-10-27 23:28:00+10:30
> > 2015-10-28 13:13:33.601900 E [20389]  mythcommflag: Failed due to:
> > "DBData() could not read from database"
> >
> >
> > It appears to be reading the config.xml file correctly as if I change
> > the user/password/database to an incorrect value then the script
> > silently fails. Plus I added additional logging at one point and it
> > appeared to be getting the database url correctly (and I couldn't work
> > out how to log the user / password it was using so I eventually gave
> > up). Any other suggestions on what I can try to do to troubleshoot?
> >
> 
> That error usually means the recording can't be found.
> 
> Your post appears to be coming from a BE log, but it doesn't appear to be
> using a %JOBID% (I'd expect to see: "Starting job ...").
> 
> So check you're using version 5 (Oct 2014) of silence.py. That has an
> (undocumented) option "--dump" that will dump the stack.
> 
> The data isn't particularly helpful but I suspect, at the bottom, it will
> show:
> 
> File "/usr/local/lib/python2.7/dist-packages/MythTV/database.py", line
> 203, in _pull
> 
> confirming you have no database entry for that chan/time. It will also
> show the ProgId, which is the Chan/UTC that Myth uses.
> 
> Do you have a file 1022_20151027125800.ts ? The TV guide for your area
> doesn't appear to show anything starting around then.
> 
> _______________________________________________
Thanks Roger, you were spot on. I was calling it from the command line using
--chanid and --starttime and was feeding the wrong starttime in (either UTC
when it was expecting local or vica-versa). I switched over to using --jobid
and it worked.

Thanks for the pointer.