[mythtv-users] Remote frontend access denied

John Pilkington johnpilk222 at gmail.com
Thu Nov 21 08:58:22 UTC 2019


On 21/11/2019 04:01, Don Brett wrote:
> I had a working 18.04 Ubuntu-Mate box that worked fine; after a 
> self-induced catastrophic error, I ended up rebuilding it (fe/be box 
> with one remote frontend).  The rebuild also works pretty well, but I 
> haven't gotten the remote front-end working yet.  I haven't made any 
> changes to the remote, but I'm getting database connection errors.  
> Tried lots of things, but no luck.  Any suggestions on what to look for?
> 
> Don
> 
> *From the logs:*
> 
> *Excerpts from remote box: (/var/log/mythtv/mythfrontend.log)*
> Nov 20 12:49:34 jax mythfrontend.real: mythfrontend[2459]: E CoreContext 
> mythdbcon.cpp:239 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: 
> Unable to connect#012Database error was:#012Access denied for user 
> 'mythtv'@'jax' (using password: YES)
> 
> Nov 20 12:49:34 jax mythfrontend.real: mythfrontend[2459]: E CoreContext 
> mythdb.cpp:646 (GetSettingOnHost) Database not open while trying to load 
> setting: backendserverport
> 
> *Excerpts from fe/be box:**(/var/log/mysql/error.log)*
> 2019-11-20T17:49:34.057263Z 544 [Note] Access denied for user 
> 'mythtv'@'jax' (using password: YES)
> 2019-11-20T18:00:01.606694Z 545 [Note] Got an error reading 
> communication packets
> 2019-11-21T00:01:41.387690Z 721 [Note] Got an error reading 
> communication packets
> 2019-11-21T00:15:52.630339Z 156 [Note] Aborted connection 156 to db: 
> 'mythconverg' user: 'mythtv' host: 'localhost' (Got timeout reading 
> communication packets)
> 
> 
> *Things I've checked:**
> **
> **/home/don/don.my.cnf*
> secure_file_priv=/var/lib/mysql
> 
> */home/don/.mythtv/config.xml (same as it was before rebuild)*
> <LocalHostName>my-unique-identifier-goes-here</LocalHostName>
>    <Database>
>      <PingHost>1</PingHost>
>      <Host>localhost</Host>
>      <UserName>mythtv</UserName>
>      <Password>mythtv</Password>
>      <DatabaseName>mythconverg</DatabaseName>
>      <Port>3306</Port>
>    </Database>
> 
> */home/mythtv/.mythtv/config.xml (symlinked to /etc/mythtv/config.xml)*
> <Configuration>
>    <Database>
>      <PingHost>1</PingHost>
>      <Host>localhost</Host>
>      <UserName>mythtv</UserName>
>      <Password>mythtv</Password>
>      <DatabaseName>mythconverg</DatabaseName>
>      <Port>3306</Port>
>    </Database>
> 
> */etc/mysql/mysql.conf.d/mysqld.cnf*
> # removed 11/17/2019
> #bind-address           = 127.0.0.1
> 
> # trying this 11/18/2019...didn't help
> #bind-address           = 0.0.0.0
> 
> */etc/mysql/mysql.conf.d/mythtv.cnf*
> [mysqld]
> #bind-address=::
> max_connections=100
> #sql_mode=NO_ENGINE_SUBSTITUTION
> 

I have recently had DB access problems running master from the ppa under 
kubuntu 18.04, but not as an appliance.  I run mythbackend in one 
konsole tab, and mythfrontend.real in another,  after using 
mythtv-setup.real   This makes it similar to the way I run myth under 
Fedora or el7.

Uncommenting the bind-address = 0.0.0.0 and restarting the DB (sudo 
systemctl restart mysql.service, IIRC) brought it back to life, although 
I'm not sure how completely.  It needed to be done again after 
installing the next build.

HTH, but YMMV.

John P


More information about the mythtv-users mailing list