[mythtv-users] erratic connection to master backend after upgrading

[Bill Meek]

On 07/11/2015 11:04 AM, Douglas Sargent wrote:
> Hi Bill,
>
>      thanks for your reply. Here is the content of ~/.mythtv
> doug at media-tv:~/.mythtv$ ls -la
> total 268
> drwxrwxr-x 18 doug doug   4096 Jul  8 15:51 .
...
> -rw-rw-r--  1 doug doug    600 Jul  8 15:51 config.xml
...
> here is content of config.xml
> doug at media-tv:~/.mythtv$ more config.xml
> <Configuration>
>    <Database>
>      <PingHost>1</PingHost>
>      <Host>192.168.0.19</Host>
>      <UserName>mythtv</UserName>
>      <Password>mythtv</Password>
>      <DatabaseName>mythconverg</DatabaseName>
>      <Port>3306</Port>
>    </Database>
>    <WakeOnLAN>
>      <Enabled>1</Enabled>
>      <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
>      <SQLConnectRetry>5</SQLConnectRetry>
>      <Command>echo 'WOLsqlServerCommand not set'</Command>
>    </WakeOnLAN>
>    <UPnP>
>      <UDN>
>        <MediaRenderer>6d7d01e4-a78b-4d0e-b2ba-751094b1aa1c</MediaRenderer>
>      </UDN>
>    </UPnP>
>    <LocalHostName></LocalHostName>
> </Configuration>
> doug at media-tv:~/.mythtv$
>
>   - Regarding your question, yes the crash is on the master backend, when I
> lift the frontened. it crashes after the flag screen, the the frontend
> starts with the menu.
>
> -  Regarding the erratic behaviour. Last night got back late. Mythweb on
> tablet was giving me the conection error, and remote frontend was not
> conecting. Today wake up, mythweb is working ok, and remote frontend is
> working perfect. It's like a service is stuck and taking time to start
>
> Thanks
>
> Doug
>
>>
>> Message: 2
>> Date: Fri, 10 Jul 2015 17:05:48 -0500
>> From: Bill Meek <keemllib at gmail.com>
>> To: mythtv-users at mythtv.org
>> Subject: Re: [mythtv-users] erratic connection to master backend after
>>          upgrading
>> Message-ID: <55A041BC.7080809 at gmail.com>
>> Content-Type: text/plain; charset=windows-1252; format=flowed
>>
>> On 07/10/2015 07:26 AM, Douglas Sargent wrote:
>>> Hi all,
>>>
>>>       not sure how to debug this one. My remote frontend and mythweb work
>>> perfect. Then I update Mythtv packages, and now remote frontend does not
>>> coonect to the backend, and mythweb goves me this error:
>>> Unable to connect to the master backend at 192.168.0.19:6543.
>>> Is it running?
>>>
>>> On my Myster backend, I can run the frontend and see recordings normaly.
>>> On the *Master* backend when the frontend starts it shows me the flags
>> and
>>> languages, when I slelect it crashes, the starts up direct on the menu
>> ...
>>> Version : apt-cache policy mythtv
>>> mythtv:
>>>     Installed: 2:0.28.0~master.20150709.7ff031a-0ubuntu0mythbuntu4
>>>     Candidate: 2:0.28.0~master.20150710.c331c3f-0ubuntu0mythbuntu4
>>
>> Hi,
>>
>> If the SHA1s above are from your earlier installation and the most recent
>> (failing) one, then I'd say it isn't due to a commit.  Here's what was
>> changed: http://pastebin.com/8HzDqKVP .
>>
>> I see mytharchivehelper, BluRay, ZoneMinder and Gallery.
>>
>> Hopefully, there a typo in your 2nd paragraph, I think you mean that on the
>> *Remote*, the frontend doesn't work (not the Master.)
>>
>> I'd start by looking at ~/.mythtv/config.xml. Does it exist, is it
>> writable,
>> has a symbolic link to a system-wide config.xml been broken...

OK, config.xml looks right, and the randomness you mention also suggests
that isn't it.

Since the backend isn't responding, maybe the 1st step is proving you
can connect to 192.168.0.19, e.g. with ping, ssh or even WebFrontend
at 192.168.0.19:6544 if the backend is actually running.

Otherwise, I'd start looking at the backend logs. Pastebin them if you like, maybe someone
will spot something in them. [https://www.mythtv.org/wiki/Posting_Logs]

You confirm that the "the crash is on the master backend", but crash is a bit too
vague. To me it means a segfault and there should be a core file. This is where
to go for help with them, but assume that's not the case for now:

     https://www.mythtv.org/wiki/Debugging#Getting_a_Backtrace

FYI, I'm running 0.28-pre on commit 98d0914, which is 3 commits later than
your Candidate above. No connection problems here.

-- 
Bill