No subject
Tue May 30 07:28:35 UTC 2006
Unexpected response to MYTH_PROTO_VERSION 'MYTH_PROTO_VERSION 26':
So I started digging through the mythbackend log and found that it was
starting up as a slave backend not the master. Upon further inspection I
saw that if the BackendServerIP and the MasterServerIP do not match then it
starts as a slave.
Output from settings table:
mysql> select * from settings where value in ('BackendServerIP',
'MasterServerIP');
+--------------------+--------------+--------------+
| value | data | hostname |
+--------------------+--------------+--------------+
| BackendServerIP | 127.0.0.1 | enterprise |
| MasterServerIP | 192.168.1.5 | NULL |
+--------------------+--------------+--------------+
To correct this I changed the MasterServerIP data and hostname fields to
match that of the BackendServerIP.
I started up mythbackend and all seems well now.
One question remains...the system runs the master backend, mythweb, and a
frontend. Should these values be the same? if so what changes them at run
time? if not why was I not able to connect to it?
If the steps I took were the correct resolution then I'll gladly post this
message in the Troubleshooting section of the wiki :)
Thanks much,
--
Joe Maldonado
------=_Part_32969_15754090.1149865837515
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hello all,<br><br>I'm not quite sure whether this is a know issue, or just my boneheadedness but here it goes..<br><br>Recently my system went down due to a power outage. I realize I should have a UPS on this system though it's one of those things I have not gotten around to. Anyhow the system came up fine. Or so it seemed. The frontends were not able to connect to the backend process. This was disturbing since there were no clear error messages in the log.
<br><br>From the mythfrontend log I saw:<br><br>2006-06-08 10:50:43.587 Socket error connecting to host: <a href="http://192.168.1.5">192.168.1.5</a>, port: 6543, error: ConnectionRefused<br>2006-06-08 10:50:43.588 Connection timed out.
<br> You probably should modify the Master Server<br> settings in the setup program and set the<br> proper IP address.<br><br>From mythweb i get an error message:
<br><br>Unexpected response to MYTH_PROTO_VERSION 'MYTH_PROTO_VERSION 26': <br><br>So I started digging through the mythbackend log and found that it was starting up as a slave backend not the master. Upon further inspection I saw that if the BackendServerIP and the MasterServerIP do not match then it starts as a slave.
<br><br>Output from settings table:<br><br>mysql> select * from settings where value in ('BackendServerIP', 'MasterServerIP');<br><br>+--------------------+--------------+--------------+<br>| value | data | hostname |
<br>+--------------------+--------------+--------------+<br>| BackendServerIP | <a href="http://127.0.0.1">127.0.0.1</a> | enterprise |<br>| MasterServerIP | <a href="http://192.168.1.5">192.168.1.5</a> | NULL |
<br>+--------------------+--------------+--------------+<br><br>To correct this I changed the MasterServerIP data and hostname fields to match that of the BackendServerIP.<br><br>I started up mythbackend and all seems well now.
<br><br>One question remains...the system runs the master backend, mythweb, and a frontend. Should these values be the same? if so what changes them at run time? if not why was I not able to connect to it?<br><br>If the steps I took were the correct resolution then I'll gladly post this message in the Troubleshooting section of the wiki :)
<br><br>Thanks much,<br><br>-- <br>Joe Maldonado
------=_Part_32969_15754090.1149865837515--
More information about the mythtv-users
mailing list