[mythtv-users] Unable to connect to the master backend at 192.168.1.100:6543 (16.04 & 0.28)

Stephen Worthington stephen_agent at jsw.gen.nz
Fri Apr 15 17:24:11 UTC 2016


On Fri, 15 Apr 2016 10:03:51 -0700, you wrote:

>This question didn't get any traction on the Mythbuntu forum so I thought
>I'd ask here...
>
>I installed 16.04 beta 2 and MythTV Mythbuntu 0.28 (both updated to the
>latest versions as of yesterday) and for the most part it's solid - can
>record and watch shows, etc. But mythweb and mythtv-status are not working
>100%. I'll describe my mythtv-status problem, since I suspect that if I can
>fix that, my mythweb connection issue will be fixed as well.
>
>When I run mythtv-status, I get this:
>
>> $ mythtv-status
>> MythTV status for localhost
>> ===========================
>> Status...........: 2016-04-10 18:07:31
>> Total Disk Space.: Total space is 5.4 TB, with 4.6 TB used (85.2%)
>> Next Recording In: 35 Minutes
>> Scheduled Recordings:
>> 2016-04-10 18:43:00 - Fear the Walking Dead (AMC HD (Pacific))
>> 2016-04-10 20:00:00 - Madam Secretary (KIONDT (KION-DT))
>> Schedule Conflicts:
>> Unable to access MythTV Perl API. Try with --verbose to find out why.
>
>
>When I try --verbose, I see what appears to be the same issue I have with
>mythweb:
>
>> Failed to load Perl API
>> Couldn't communicate with 192.168.1.100 on port 6543:
>> IO::Socket::INET::MythTV: connect: Connection refused
>
>
>Any ideas why/how mythtv-status seems to be able to connect to the database
>for scheduled recordings but not for conflicts? Not sure where to look
>next...

I am just guessing, but mythtv-status may not be compatible with 0.28
yet.  So when it calls the old 0.27 API call for the scheduler
conflicts, that call may have changed in 0.28 and fails.


More information about the mythtv-users mailing list