<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 29/04/2016 23:13, Damian wrote:<br>
<blockquote
cite="mid:71b682ff-178e-26c4-0f49-39c76c90ab3b@surr.co.uk"
type="cite">On 29/04/2016 23:09, Thomas Mashos wrote:
<br>
<blockquote type="cite">
<br>
<br>
On Fri, Apr 29, 2016 at 2:55 PM Damian Surr
<<a class="moz-txt-link-abbreviated" href="mailto:damian@surr.co.uk">damian@surr.co.uk</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:damian@surr.co.uk"><mailto:damian@surr.co.uk></a>> wrote:
<br>
<br>
On 29/04/2016 22:31, Damian wrote:
<br>
> I LOVE MythTV when it's all set up and working
properly.
<br>
>
<br>
> Is there anything more frustrating when it's not??
<br>
>
<br>
> OK, here's the latest problem. (all using Xubuntu
16.04, MythTV 0.28,
<br>
> via Mythbuntu, all updates to latest versions etc).
<br>
>
<br>
> Things were going well. Server all set up. Backend
working well. Local
<br>
> frontend (on the server) seeming to work fine.
<br>
>
<br>
> One remote frontend set up and seeming fine.
<br>
>
<br>
> Second (main) remote frontend setup, but just wouldn't
connect to the
<br>
> backend! I couldn't work it out. Everything seemed
fine, but it
<br>
> couldn't connect.
<br>
>
<br>
> In desperation (never a good place to make decisions),
I thought about
<br>
> how Mythbuntu seems to install a slave backend (which I
had removed on
<br>
> the frontends) by default. So, I installed and set up
slave backends
<br>
> on both of the remote frontend machines.
<br>
>
<br>
> This seemed to work well. Now both remote frontends
could connect and
<br>
> I thought that I was heading in the right direction.
However, now the
<br>
> frontends were suddenly SO SLOW and couldn't connect to
'Videos' or
<br>
> watch TV.
<br>
>
<br>
> After failing to fix this, I thought that the slave
backends may have
<br>
> been the problem, so I uninstalled them from both of
the remote
<br>
> frontends.
<br>
>
<br>
> This didn't change anything. I could still connect (so
I was further
<br>
> on than before I affed the slave backends), but
everything was still
<br>
> unusable.
<br>
>
<br>
> I tried changing the <LocalHostName> on one of
the frontends to see if
<br>
> being effectively a 'new user' would clean things up.
It didn't. I was
<br>
> just a new user with a system that was still broken.
<br>
>
<br>
> I ran one of the remote frontends from the command line
to see what
<br>
> error messages I was getting while things were
freezing, and I got
<br>
> lots of copies of messages like this ...
<br>
>
<br>
> 2016-04-29 21:49:14.102196 I
MythCoreContext::ConnectCommandSocket():
<br>
> Connecting to backend server: 192.168.0.2:6543
<br>
<a class="moz-txt-link-rfc2396E" href="http://192.168.0.2:6543"><http://192.168.0.2:6543></a> (try 1 of 1)
<br>
> 2016-04-29 21:49:21.121452 E MythSocket(3b91410:68):
ReadStringList:
<br>
> Error, timed out after 7000 ms.
<br>
> 2016-04-29 21:49:21.121843 C Protocol version check
failure.
<br>
> The response to MYTH_PROTO_VERSION was
empty.
<br>
> This happens when the backend is too busy
to respond,
<br>
> or has deadlocked due to bugs or hardware
failure.
<br>
> 2016-04-29 21:49:21.122406 W Backend : gingerserver
currently
<br>
> Unreachable. Skipping this one.
<br>
> 2016-04-29 21:49:21.122558 I
MythCoreContext::ConnectCommandSocket():
<br>
> Connecting to backend server: 192.168.0.2:6543
<br>
<a class="moz-txt-link-rfc2396E" href="http://192.168.0.2:6543"><http://192.168.0.2:6543></a>
<br>
>
<br>
> I've just gone back to the server (backend system) and
run the
<br>
> frontend on there. Now that's having the same trouble.
Almost
<br>
> completely unresponsive. I haven't even touch this
machine while I've
<br>
> been trying other stuff!
<br>
>
<br>
> $ sudo service mythtv-backend status
<br>
>
<br>
> returns ...
<br>
>
<br>
> ● mythtv-backend.service - MythTV Backend
<br>
> Loaded: loaded
(/lib/systemd/system/mythtv-backend.service;
<br>
> enabled; vendor preset: enabled)
<br>
> Active: active (running) since Fri 2016-04-29
20:34:26 BST; 1h
<br>
> 53min ago
<br>
> Docs: <a class="moz-txt-link-freetext" href="https://www.mythtv.org/wiki/Mythbackend">https://www.mythtv.org/wiki/Mythbackend</a>
<br>
> Main PID: 822 (mythbackend)
<br>
> Tasks: 34 (limit: 512)
<br>
> CGroup: /system.slice/mythtv-backend.service
<br>
> └─822 /usr/bin/mythbackend --quiet --syslog
local7
<br>
>
<br>
> Apr 29 21:45:05 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 21:50:18 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 21:55:31 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:00:43 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:05:55 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:11:08 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:11:11 gingerserver mythbackend[822]:
mythbackend[822]: E
<br>
> TVRecEvent tv_rec.cpp:3964 (TuningSignalCheck)
TVRec[3]:
<br>
> TuningSignalCheck: SignalMonitor timed out
<br>
> Apr 29 22:14:14 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:19:20 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
> Apr 29 22:24:25 gingerserver mythbackend[822]:
mythbackend[822]: I
<br>
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[3]:
TuningFrequency
<br>
>
<br>
> Any ideas?
<br>
>
<br>
> I had some mysql problems earlier, which I posted
about, but they seem
<br>
> to be resolved now. I can connect with both root and
mythtv.
<br>
>
<br>
> My daughter is supposed to be having a cinema party fro
her 16th
<br>
> birthday on Wednesday. If I don't get this sorted, I'm
'bad dad', big
<br>
> time. :-)
<br>
>
<br>
> Please let me know if you can see what's wrong or know
what I should
<br>
> do next.
<br>
>
<br>
> Thanks,
<br>
> Damian
<br>
Brief success, then back to failure.
<br>
<br>
Looking at the backend setup, I saw that I'd set the IPv6
address back
<br>
to "::1". This must have been when I was trying and failing
to get the
<br>
second remote frontend to connect. I don't really know what
that big
<br>
long IPv6 address is (the one that's selectable on the
backend), but
<br>
must have assumed at some point that it should be moved away
from the
<br>
default value just as the IPv4 address needs to be changed.
<br>
<br>
Looking at <a class="moz-txt-link-freetext" href="https://www.mythtv.org/wiki/Setup_General">https://www.mythtv.org/wiki/Setup_General</a>
indicates that I
<br>
should have left this at the default value "::1", and I must
have
<br>
changed that earlier.
<br>
<br>
I just changed it back to the long IPv6 address, and
suddenly everything
<br>
was great, for about 3 minutes. All frontends connected
fine, were
<br>
responsive, and things looked good.
<br>
<br>
Then it all turned to sludge again.
<br>
<br>
Does this point to the source of the problem?
<br>
<br>
Thanks,
<br>
Damian
<br>
<br>
<br>
On your backend, is mysql listening on the right addresses?
<br>
--
<br>
Thomas Mashos
<br>
</blockquote>
<br>
Hi Thomas,
<br>
<br>
I can log in with ...
<br>
mysql -u mythtv -p -h 192.168.0.2
<br>
<br>
Does that answer your question? If it doesn't, I'm afraid I don't
understand the question well enough. Is there a command that I
should run to test it?
<br>
<br>
Thanks,
<br>
Damian
<br>
</blockquote>
<br>
I just remembered something else that happened earlier .. in case
it's relevant.<br>
<br>
While running some updates, the myth backend update seemed to want
me to configure mysql for a user called 'debian-sys-maint'. I've
never had to configue any mysql users other than 'root' and 'mythtv'
before, so this threw me. I tried to just skip it, but if I log into
mysql as root and run "SELECT User FROM mysql.user;" (which is a
command that I don't understand in the slightest, I just found it
online to list users), then 'debian-sys-maint' makes an appearance
...<br>
<br>
mysql> SELECT User FROM mysql.user;<br>
+------------------+<br>
| User |<br>
+------------------+<br>
| mythtv |<br>
| debian-sys-maint |<br>
| mysql.sys |<br>
| root |<br>
+------------------+<br>
4 rows in set (0.00 sec)<br>
<br>
Could this have messed things up?<br>
<br>
Should I try something like:<br>
<pre>sudo dpkg-reconfigure mythtv-database
<span class="anchor" id="line-2"></span>sudo dpkg-reconfigure mythtv-common
or could that break things more?
Or should I be trying to delete that user out of mysql? (I have no idea how to do that .. I could probalby do it if I install phpmyadmin).
Thanks,
Damian
</pre>
</body>
</html>