[mythtv-users] Myth not autoexpiring since upgrade to 0.22RC1

Chris Pinkham cpinkham at bc2va.org
Tue Oct 27 01:40:09 UTC 2009


* On Mon Oct 26, 2009 at 11:47:05PM +0000, Duncan Brown wrote:
> +------------------------+
> | Expirable in recorded: |
> +------------------------+
> |                    211 |
> +------------------------+
> 1 row in set (0.00 sec)

So this indicates you should have something printed when you run
mythbackend --printexpire.  Can you try the following:

echo "SELECT recorded.chanid, starttime, endtime, title, subtitle, description, hostname, channum, name, callsign, seriesid, programid, recorded.recpriority, progstart, progend, filesize, recgroup, storagegroup, basename FROM recorded LEFT JOIN channel ON recorded.chanid = channel.chanid WHERE autoexpire > 0 AND deletepending = 0 ORDER BY autoexpire DESC, starttime ASC;" | mysql -umythtv -p mythconverg

This is the command that the expirer code runs when you run
--printexpire.  You should be able to see this SQL command if
you ran mythbackend like this:  "mythbackend -v file,database --printexpire"

See if that SQL generates an error or lists the info on the programs
that may be expired.

--
Chris


More information about the mythtv-users mailing list