search

nashve / mythbox

Automatically exported from code.google.com/p/mythbox
GNU General Public License v2.0
0 stars 1 forks source link

MySQL Connection Refused - sock file error? #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Since MySQL 5.1.41 the socket file has changed location from
/tmp/mysql.sock to /var/run/mysqld/mysqld.sock

What steps will reproduce the problem?
1. Install MySQL >= 5.1.41
2. Test Settings

What is the expected output? What do you see instead?

Although all settings are correct, I get the following error:
NOTICE: DEBUG | mythtv.ui | ui.py | MainThread | Line 79 | showPopup:
XBMC.Notification(Settings Error,Connect to MySQL failed: Failed connecting
to localhost:3306 ((111; 'Connection refused')),10000)

What version of the product are you using? On what operating system?
using 1558 from the downloads, also tried latest source. All on (Arch) Linux

I found two references to the old sock file in:

resources/lib/mysql-connector-python/mysql/connector/connection.py
resources/lib/mysql-connector-python/client.py

updated them to the new path and also deleted the ...connection.pyo but
still not fixed.

Original issue reported on code.google.com by markfoxw...@gmail.com on 3 Jan 2010 at 1:43

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I too am experiencing this issue.

What steps will reproduce the problem?
I only see this problem on the "Recording Details" page. Commerical Skip works 
fine,
the "Watch Recordings" page works fine and the home screen works fine.

What version of the product are you using? On what operating system?
I'm using version 1558 of mythbox, mysql-5.0.84 (double checked, it's 5.0.84) 
and
mythtv-0.22 (svn 22860). Also Gentoo Linux.

Original comment by wes...@gmail.com on 13 Jan 2010 at 11:55

GoogleCodeExporter commented 9 years ago 
I would recommend you both enable the default mysql tcp socket (port 3306) 
instead of
using the unix domain socket. It is just more work to support both connection
methods. Furthermore, the tcp socket method works for both local and remote 
frontends
whereas the domain socket only supports local frontends. If you feel this is a
critical feature, please submit a patch and accompanying unit tests.

Original comment by semir.pa...@gmail.com on 17 Jan 2010 at 6:13