[mythtv-users] mythtv-status

Stephen Worthington stephen_agent at jsw.gen.nz
Wed May 3 09:41:22 UTC 2017


On Wed, 03 May 2017 15:43:27 +1200, you wrote:


>On Tue, 2017-05-02 at 17:05 -0700, Fred Hamilton wrote:
>> On Sun, Apr 30, 2017 at 6:25 PM, Andrew Ruthven <andrew at etc.gen.nz>
>> wrote:
>> > Odd. Can you please send me the output when running with --verbose?
>> > 
>> 
>> Here you go:
>> 
>> $ mythtv-status --verbose
>> Today:    20170502
>> Tomorrow: 20170503
>> Considering: One Liners
>>   Going to process: One Liners
>> Considering: Status
>>   Going to process: Status
>> Loaded XML from localhost
>> Considering: Encoders
>>   Going to process: Encoders
>> Considering: Encoders
>>   Going to process: Encoders
>> Considering: Encoders
>>   Going to process: Encoders
>> We have the correct protocol version for Encoders
>> Considering: Recording Now
>>   Going to process: Recording Now
>> Considering: Scheduled Recordings
>>   Going to process: Scheduled Recordings
>> Considering: Schedule Conflicts
>>   Going to process: Schedule Conflicts
>> Failed to load Perl API
>> Unable to connect to mythbackend, is it running?
>> Considering: Shows due to Auto Expire
>> Considering: Total Disk Space
>>   Going to process: Total Disk Space
>> Considering: Total Disk Space
>>   Going to process: Total Disk Space
>> We have the correct protocol version for Total Disk Space
>> We have the correct xml version for Total Disk Space
>> Unable to find any value for drive_total_total while at Total Disk
>> Space, marked as optional, skipping block.
>> Considering: Total Disk Space
>>   Going to process: Total Disk Space
>> We have the correct protocol version for Total Disk Space
>> Considering: Disk Space
>>   Going to process: Disk Space
>> We have the correct protocol version for Disk Space
>> Considering: Next Recording In
>>   Going to process: Next Recording In
>> Considering: Guide Data
>>   Going to process: Guide Data
>> Considering: Guide Data
>>   Going to process: Guide Data
>> 
>> MythTV status for localhost
>> ===========================
>> Status...........: 2017-05-02 17:00:18
>> Total Disk Space.: Total space is 8.3 TB, with 3.7 TB used (44.6%)
>> Next Recording In: 59 Minutes
>> 
>> Scheduled Recordings:
>> 2017-05-02 18:00:00 - Graveyard Carz (Velocity)
>> 2017-05-02 19:00:00 - Graveyard Carz (Velocity)
>> 2017-05-02 21:00:00 - Fresh Off the Boat (KSBWDT2 (KSBW-DT2))
>> 2017-05-02 22:00:00 - The Americans (FX HD (Pacific))
>> 2017-05-03 01:02:00 - Archer (FXX HD (Pacific))
>> 2017-05-03 04:00:00 - Frontline (KQEDDT (KQED-DT))
>> 2017-05-03 15:00:00 - PBS NewsHour (KQEDDT (KQED-DT))
>> 
>> Schedule Conflicts:
>> Unable to access MythTV Perl API.  Try with --verbose to find out
>> why.
>>
>Hey Fred,
>
>Thank you. It looks like the Perl bindings can't talk to the backend.
>Is it running on the local host? If not, do you have config.xml file
>present for the user you're running mythtv-status as?
>
>Cheers,
>Andrew

I recently discovered what I think must be a bug in the 0.28 MythTV
Perl bindings, which might be affecting mythtv-status (I have not
looked its code to see).

If you do this:

  $myth = new MythTV();

it fails to connect.

If you do this:

  $myth = new MythTV({'connect' => 0});

it does work.  I do not know Perl at all, so I have no idea what is
going on.  I just happened to be trying to use some code that uses the
MythTV Perl bindings and worked this out by comparing some code that
was working in optimize_mythdb with the code that was not working.


More information about the mythtv-users mailing list