[mythtv-users] BE3 - Issues with installation and database

[Barry Martin]

Hi Stephen!


If you have not changed the bind-address setting in the//etc/mysql//*
config files, you will get it only binding localhost (127.0.0.1).  But
that will not stop it from working.


    Assuming these (maybe I'm looking at the wrong files!):


    barry at Backend-3:/etc/systemd/system$ find / -iname config.xml
    2>/dev/null

    /etc/mythtv/config.xml

    /home/barry/.mythtv/config.xml

    /home/mythtv/.mythtv/config.xml

    /usr/share/doc/mythtv-backend/contrib/config_files/config.xml

    /usr/share/mythtv/config.xml



    So:

    /etc/mythtv/config.xml 192.168.0.3 username = mythtv password (correct)

    /home/barry/.mythtv/config.xml (same as above)

    /home/mythtv/.mythtv/config.xml (same as above)

    /usr/share/doc/mythtv-backend/contrib/config_files/config.xml

    hostname: my-unique-identifer-goes-here

    127.0.0.1 mythtv mythtv

    (I've always assumed this was a template rather than a config file)

    /usr/share/mythtv/config.xml same as above (127.0.0.1, etc,)

There are going to be error
messages in the log files.  Unfortunately, which log file depends on
how it is configured.  So you need to look at:

/var/log/mysql.log	BJM: no such file per ls
/var/log/mysql.err	BJM: no such file		No errors! Yea! <joke>

and all the files in:

//var/log/mysql//

One or more of them will have all the normal startup messages, and the
error(s) that are causing it to shut down again.  If it is configured
right, the most likely place for the error(s) to be logged is:

/var/log/mysql/error.log

    Error.Log was requested by Bill and posted at
    https://pastebin.com/bVwNPwB8



Since you do not know all that much about MariaDB yet, it is best if
you just post the entire log for the last time you attempted to start
MariaDB.  The easiest way to do that is to try starting it:

sudo systemctl start mariadb

and note down the time you did that command.  Then find any messages
in the logs that happened at that time and for the next few seconds
(minutes?) afterwards.  If there is not too much, just post it in an
email here, otherwise post it on pastebin.com and post a URL to there.

My first guess is that it will have a message about "can't init" a
"tc.log" file.  So when you are looking at the log files, if you find
one named tc.log, try deleting that and starting MariaDB again.


    OK, I’ll admit to getting tired and fuzzy-brained. If something got
    posted oddly I apologize and will try to answer when more rested.


    I did use /find /to look for tc.log – starting at root. It didn’t
    locate.


    Good night for now! Do appreciate the assistance!

    Barry


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190516/215b7e01/attachment.html>