[mythtv-users] Brand new install - Mythbackend doesn't start
Ashu Desai
ashu.desai at gmail.com
Thu Aug 3 04:29:58 UTC 2017
On Wed, Aug 2, 2017 at 11:00 PM, Bill Meek <keemllib at gmail.com> wrote:
> On 08/02/2017 10:55 PM, Mark Perkins wrote:
>
>> As I understand it the logic for starting as a slave is a simple
>> comparison of the local backend address and the master backend address
>> fields. If they are different in any way (even if 127.0.0.1 in one and
>> localhost in the other) it will start as a slave.
>>
>> If it is 'not working' with 172.16.10.54 in both master and local BE
>> fields then need to troubleshoot what other bad config exists rather than
>> keep changing back to localhost / 127.0.0.1 and masking the problem /
>> creating further problems.
>>
>> What do you get in the log file (clean pastebin from startup to shutdown)
>> when you have 172.16.10.54 in both local and master BE fields?
>> Is mysql listening on more than localhost (sudo netstat -peanut | grep
>> 3306)?
>>
>
> Mark's exactly right, the IPs MUST match otherwise it's a slave.
>
> Please add the log from mythtv-setup in a pastebin too. Need to see that
> it's accessing the correct confdir etc.
>
>
The IPs match - that's why I am having this issue of mythbackend crashing.
For now, Local and Master backend server both have the same IP -
172.16.10.54
I am not sure how to get the logs of "mythtv-setup" so i just did a tail -f
| journalctl -xe while doing a myth-setup
https://pastebin.com/ax9v2nVY
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170802/93797f91/attachment.html>
More information about the mythtv-users
mailing list