Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

mythbackend --printexpire

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


esarfl at gmail

Jul 31, 2012, 10:11 AM

Post #1 of 6 (389 views)
Permalink
mythbackend --printexpire

In 0.24, I could run the command "mythbackend --printexpire" and see a
list of the recordings next eligible for autoexpire. This was helpful
for tuning my priorities--and no surprises when recordings were
expired. With 0.25, the expire list never prints. I just get the
normal startup lines...

tom [at] t:~$ mythbackend --help 2>&1 | grep expire
--printexpire Print upcoming list of recordings to be expired.

tom [at] t:~$ mythbackend --printexpire
2012-07-31 11:00:14.461484 C mythbackend version: fixes/0.25
[v0.25.2-3-gf0e2ad8] www.mythtv.org
2012-07-31 11:00:14.461679 C Qt version: compile: 4.7.4, runtime: 4.8.1
2012-07-31 11:00:14.461684 N Enabled verbose msgs: general
2012-07-31 11:00:14.461711 N Setting Log Level to LOG_INFO
2012-07-31 11:00:14.461823 I Added logging to the console
2012-07-31 11:00:14.461831 I Added database logging to table logging
2012-07-31 11:00:14.461949 N Setting up SIGHUP handler
2012-07-31 11:00:14.465757 N Using runtime prefix = /usr
2012-07-31 11:00:14.465794 N Using configuration directory = /home/tom/.mythtv
2012-07-31 11:00:14.467671 I Assumed character encoding: en_US.UTF-8
2012-07-31 11:00:14.471718 N Empty LocalHostName.
2012-07-31 11:00:14.471734 I Using localhost value of t3
2012-07-31 11:00:14.508050 N Setting QT default locale to EN_US
2012-07-31 11:00:14.508118 I Current locale EN_US
2012-07-31 11:00:14.508706 N Reading locale defaults from
/usr/share/mythtv//locales/en_us.xml

I added a drive to my Default storage group around the time I upgraded
to 0.25. Maybe this is the cause.

Without this command line tool working, the only way I know of to view
the autoexpire list is via the frontend. I'd like the list via ssh, or
better yet, mythweb. What happened to --printexpire? Can someone point
me to the autoexpire SELECT query so I can run it manually?

Tom
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Jul 31, 2012, 11:01 AM

Post #2 of 6 (367 views)
Permalink
Re: mythbackend --printexpire [In reply to]

On 07/31/2012 01:11 PM, Tom Hayward wrote:
> In 0.24, I could run the command "mythbackend --printexpire" and see a
> list of the recordings next eligible for autoexpire. This was helpful
> for tuning my priorities--and no surprises when recordings were
> expired. With 0.25, the expire list never prints. I just get the
> normal startup lines...
>
> tom [at] t:~$ mythbackend --help 2>&1 | grep expire
> --printexpire Print upcoming list of recordings to be expired.
>
> tom [at] t:~$ mythbackend --printexpire
> 2012-07-31 11:00:14.461484 C mythbackend version: fixes/0.25
> [v0.25.2-3-gf0e2ad8] www.mythtv.org
> 2012-07-31 11:00:14.461679 C Qt version: compile: 4.7.4, runtime: 4.8.1
> 2012-07-31 11:00:14.461684 N Enabled verbose msgs: general
> 2012-07-31 11:00:14.461711 N Setting Log Level to LOG_INFO
> 2012-07-31 11:00:14.461823 I Added logging to the console
> 2012-07-31 11:00:14.461831 I Added database logging to table logging
> 2012-07-31 11:00:14.461949 N Setting up SIGHUP handler
> 2012-07-31 11:00:14.465757 N Using runtime prefix = /usr
> 2012-07-31 11:00:14.465794 N Using configuration directory = /home/tom/.mythtv
> 2012-07-31 11:00:14.467671 I Assumed character encoding: en_US.UTF-8
> 2012-07-31 11:00:14.471718 N Empty LocalHostName.
> 2012-07-31 11:00:14.471734 I Using localhost value of t3
> 2012-07-31 11:00:14.508050 N Setting QT default locale to EN_US
> 2012-07-31 11:00:14.508118 I Current locale EN_US
> 2012-07-31 11:00:14.508706 N Reading locale defaults from
> /usr/share/mythtv//locales/en_us.xml
>
> I added a drive to my Default storage group around the time I upgraded
> to 0.25. Maybe this is the cause.
>
> Without this command line tool working, the only way I know of to view
> the autoexpire list is via the frontend. I'd like the list via ssh, or
> better yet, mythweb. What happened to --printexpire? Can someone point
> me to the autoexpire SELECT query so I can run it manually?

FWIW, since you actually seem to want something more computer-parsable
than human readable:
http://www.gossamer-threads.com/lists/mythtv/users/468992#468992 (though
the first option would be "just want to see it in the browser")

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


fredwattmythtv at gmail

Jul 31, 2012, 11:09 AM

Post #3 of 6 (365 views)
Permalink
Re: mythbackend --printexpire [In reply to]

Try disabling EIT on every TV/Sat card.


raymond at wagnerrp

Jul 31, 2012, 11:26 AM

Post #4 of 6 (365 views)
Permalink
Re: mythbackend --printexpire [In reply to]

On 7/31/2012 13:11, Tom Hayward wrote:
> In 0.24, I could run the command "mythbackend --printexpire" and see a
> list of the recordings next eligible for autoexpire. This was helpful
> for tuning my priorities--and no surprises when recordings were
> expired. With 0.25, the expire list never prints. I just get the
> normal startup lines...

Thanks for spotting that. I accidentally inverted the logic to run that
option about a year back, so it would just terminate immediately rather
than printing out those lines. Corrected in 0.25 and 0.26.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


esarfl at gmail

Jul 31, 2012, 12:42 PM

Post #5 of 6 (367 views)
Permalink
Re: mythbackend --printexpire [In reply to]

On Tue, Jul 31, 2012 at 12:26 PM, Raymond Wagner <raymond [at] wagnerrp> wrote:
> On 7/31/2012 13:11, Tom Hayward wrote:
>>
>> In 0.24, I could run the command "mythbackend --printexpire" and see a
>> list of the recordings next eligible for autoexpire. This was helpful
>> for tuning my priorities--and no surprises when recordings were
>> expired. With 0.25, the expire list never prints. I just get the
>> normal startup lines...
>
>
> Thanks for spotting that. I accidentally inverted the logic to run that
> option about a year back, so it would just terminate immediately rather than
> printing out those lines. Corrected in 0.25 and 0.26.

Thanks for the fix Raymond. Unfortunately I'm not sure I'll have time
to install while the Olympics are in progress. Uptime is critical for
WAF...

A more customized solution will solve my use case better anyway. I've
started playing with the python bindings for the first time and I've
run into some issues.

MythXML().getExpiring() seems to map to Dvr/GetExpiring, when the
correct url is Dvr/GetExpiringList.

>>> import MythTV
>>> for i in MythTV.MythXML().getExpiring():
... i
... break
...
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/pymodules/python2.7/MythTV/methodheap.py", line 1202,
in getExpiring
for prog in self._request('Dvr/GetExpiring')\
File "/usr/lib/pymodules/python2.7/MythTV/connections.py", line 574,
in readJSON
return json.loads(self.read())
File "/usr/lib/pymodules/python2.7/MythTV/connections.py", line 563, in read
def read(self): return self.open().read()
File "/usr/lib/pymodules/python2.7/MythTV/connections.py", line 562, in open
def open(self): return urllib2.urlopen(self)
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 406, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 519, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 444, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found


And MythBE().getExpiring() is not sorted, or sorted by record date,
not expire priority:

>>> for i in MythTV.MythBE().getExpiring():
... i
... break
...
<Program 'Good Eats','2010-10-14 17:30:00' at 0x1b113d0>

That is my earliest recording, and it is unwatched so very low on the
autoexpire list.


This url works: http://t3:6544/Dvr/GetExpiringList. Now I'm
considering using an XML library instead of Myth python bindings to
parse that response. But maybe I'm just doing something wrong.


Tom
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


esarfl at gmail

Jul 31, 2012, 1:27 PM

Post #6 of 6 (360 views)
Permalink
Re: mythbackend --printexpire [In reply to]

On Tue, Jul 31, 2012 at 1:42 PM, Tom Hayward <esarfl [at] gmail> wrote:
> MythXML().getExpiring() seems to map to Dvr/GetExpiring, when the
> correct url is Dvr/GetExpiringList.
>
>>>> import MythTV
>>>> for i in MythTV.MythXML().getExpiring():
> ... i
> ... break
> ...
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/usr/lib/pymodules/python2.7/MythTV/methodheap.py", line 1202,
> in getExpiring
> for prog in self._request('Dvr/GetExpiring')\

Well it seems I'm not completely helpless... attached is a patch to
fix this issue.

Tom
Attachments: 0001-Fix-request-url-in-python-bindings-MythXML-.getExpir.patch (0.95 KB)

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.