[mythtv-users] Python3 interface: Could not find setting 'BackendServerAddr' on host '192.168.1.10' [work-around]

[Ross Boylan]

The workaround is to add an entry to the settings table in the form the
program wants.

I'm not sure if the lack of the appropriate entry originally indicates
1. I misconfigured my setup
2. the code has a bug
3. the code is correct for the v31 schema but not for v30.
4. something else

>From settings table:
| value             | data                | hostname |
+-------------------+---------------------+----------+
| AllowConnFromAll  | 0                   | barley   |
| BackendServerAddr | myth.betterworld.us | barley   |
| BackendServerAddr | 192.168.1.10        | barley   |
| ListenOnAllIps    | 1                   | barley   |
| MasterServerIP    | 192.168.1.10        | NULL     |
| MasterServerName  | barley              | NULL     |
+-------------------+---------------------+----------+

The entry for BackendServerAddr | 192.168.1.10 is one I added recently;
with that I am  able to get past the error I reported.
I initially used myth.betterworld.us as the hostname, but that didn't match
my existing entry for BackendServerPort.
myth.betterworld.us, barley, and 192.168.1.10 are all the same machine, the
one on which I'm running.

With that change, my deletion of the retrieved program seems to work.  I'm
still waiting to verify the recording file gets cleaned up.

My config file says host is
<Configuration>
  <LocalHostName>my-unique-identifier-goes-here</LocalHostName>
  <Database>
    <PingHost>1</PingHost>
    <Host>db.betterworld.us</Host>
    <UserName>mythtv</UserName>
....
db.betterworld.us is another alias for same machine.
It's a little odd that I don't see an explicit entry for the host of the
myth BE server itself,
though in this case it's the same as the DB.  There is a UPNP section later
in the config file;
maybe that's how it's locating  the BE server?

On Mon, Feb 24, 2020 at 10:44 AM Roland Ernst <rcrernst at gmail.com> wrote:

> On Mon, Feb 24, 2020 at 5:22 AM Ross Boylan
> <rossboylan at stanfordalumni.org> wrote:
>
> > While I'd like to understand what's going on, the services API may
> > be an easier route to get things going, though it too seems pretty
> opaque.
> > Thanks for the example.
>
>
> The Services API is the preferred way to talk to
> mythtv. Though, there are still some useful commands
> in the old part of the python bindings, which interface
> directly to the SQL database and the protocol sockets.
>
> Bill warned you already, that python3 on MythTV v30 is
> not supported.
>
> The traceback of your python3 example shows:
> > MythDBError: Could not find setting 'BackendServerAddr'
> > on host '192.168.1.10'
> and, usually, tracebacks tell the truth:
>
> Please post the output of
>
> SELECT *
>   FROM settings
>   WHERE (value = 'MasterServerName')
>      OR (value = 'MasterServerIP')
>      OR (value = 'BackendServerAddr')
>      OR (value = 'BackendServerIP')
>      OR (value = 'BackendServerIP6')
>      OR (value = 'ListenOnAllIps')
>      OR (value = 'AllowConnFromAll');
>
> and the output of your 'Host' value in 'config.xml'.
>
> According ticket #13024, the IP of the setting 'MasterServerIP' must match
> the IP of 'BackendServerAddr' or one of ['BackendServerIP',
> 'BackendServerIP6'].
>
> Roland
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200224/2fdc7ecc/attachment.htm>