<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/05/2013 20:48, Jongi wrote:<br>
</div>
<blockquote cite="mid:518E9299.2010606@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 07/05/2013 12:04, Mike Perkins
wrote:<br>
</div>
<blockquote cite="mid:5188D19B.7030504@randomtraveller.org.uk"
type="cite">On 07/05/13 01:35, Jongi wrote: <br>
<blockquote type="cite">On 07/05/2013 01:49, Raymond Wagner
wrote: <br>
<blockquote type="cite">On 5/6/2013 7:44 PM, Jongi wrote: <br>
<blockquote type="cite">However 0.26 with fixes pops up a
dialog box asking about backend <br>
settings when i run the frontend. <br>
</blockquote>
<br>
It should be popping up asking for the credentials to log
into your database <br>
server. It then queries the database server as to how to
connect to your <br>
backend. <br>
<br>
Have you configured your database server to listen on a
network-accessible <br>
address, rather than just the loopback interface? <br>
Have you set up permissions to allow the remote machine to
access the MythTV <br>
database on your database server? <br>
_______________________________________________ <br>
mythtv-users mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
<br>
</blockquote>
before i continue, i should note that the master be/fe works
perfectly. <br>
<br>
the problems i am findingstarts with a package named
mythtv-database on debian <br>
(sid/testing). again it is working on the master be/fe. <br>
<br>
So a dialog box opens (regarding mythtv-database) askingfor: <br>
administrator account <br>
password for mysql administrator account <br>
<br>
if i issue mythtv:mythtv for both questions, then
dpkg-reconfigure --force <br>
mythtv-database returns: <br>
Failed to execute SQL: GRANT ALL PRIVILEGES ON mythconverg.*
TO mythtv@localhost <br>
IDENTIFIED BY 'MZb2HG0O'\nAccess denied for user
'mythtv'@'192.168.1.%' to <br>
database 'mythconverg' at -e line 8, <> line 1. <br>
<br>
on the be/fe machine, i have already tried running - mysql -u
root -p <br>
mythconverg and then <br>
<br>
mysql> grant all on mythconverg.* to mythtv@"192.168.1.%"
identified by "mythtv"; <br>
Query OK, 0 rows affected (0.00 sec) <br>
<br>
mysql> flush privileges; <br>
Query OK, 0 rows affected (0.00 sec) <br>
<br>
mysql> grant all on mythconverg.* to jongi@"192.168.1.%"
identified by "password"; <br>
Query OK, 0 rows affected (0.00 sec) <br>
<br>
mysql> flush privileges; <br>
Query OK, 0 rows affected (0.00 sec) <br>
<br>
i can't help but feel there is one step i have missed. <br>
<br>
</blockquote>
Those strings in the 'identified' clauses are the actual
*passwords* that you are assigning to the mythtv user. You have
two different strings here. It would probably be safer to use
the same string for both; it doesn't matter which. <br>
<br>
IIRC Debian assigns some kind of random string as the mythtv
password /on mysql/. You'll have to go and hunt for all
occurrences of config.xml in your machine to see if the
reconfigure did it's job properly - and check your apache config
files as well. <br>
<br>
I notice that the rejected GRANT ALL PRIVILEGES command above
has a hostname of 'localhost' and a password of 'MZb2Hg0O'. Note
that this won't disappear simply because you manually ran the
other two commands successfully. The entry stays in the mysql
database. Rerun that command as you did those below and set it
to the same password as you chose for those. <br>
<br>
</blockquote>
<font size="-1"><font face="DejaVu Sans">Realised I don't need the
backend pac<font size="-1">kages on a <font size="-1">FE <font
size="-1">only system<br>
<br>
<font size="-1">Th<font size="-1">e errors were likely
because <font size="-1">there was no <font
size="-1">mythconverg database setup to be a s<font
size="-1">lave backend (as the systems are
meant to be FE only).</font></font></font></font></font></font></font></font></font></font><br>
</blockquote>
<font size="-1"><font face="DejaVu Sans">And to complete the loop in
case someone else has a simila<font size="-1">r question.<br>
<br>
<font size="-1">The above started because my master BE/FE syst<font
size="-1">em <font size="-1">is connected to a router
which from time to time has an issue which requi<font
size="-1">res me to reset the router.<br>
<br>
<font size="-1">what this meant in <font size="-1">0.24
i think it was, was that even thought the FE was
on the same box as the <font size="-1">BE, i
would get the error message that the FE was not
connected to the BE. So I would set in
mythtv-setup <font size="-1">on the master BE
that <font size="-1">localhost is the address
for the database.</font></font></font></font></font><br>
<br>
<font size="-1">This was then causing an issue in the
FEs stating that hey could not connect to the BE.<br>
<br>
<font size="-1">Should I be able to set on the <font
size="-1">M</font>aster Be in mythtv-setu<font
size="-1">p</font> <font size="-1">such that in
the General section I have for:<br>
<font size="-1">Local Backend - local<font
size="-1"><font size="-1">h</font>ost<br>
<font size="-1">Master Backend -
192.168.1.102<br>
<br>
<font size="-1"><font size="-1">When</font>
I have tried this it<font size="-1">
seems, <font size="-1">my standalone
FEs complain<font size="-1"> about
not <font size="-1">seeing</font>
the BE.<br>
<br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font>
</body>
</html>