Opened 7 years ago

Closed 7 years ago

#43088 closed defect (invalid)

mysql5 @5.1.72 uses /tmp for socket

Reported by: ctreleaven (Craig Treleaven) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: ryandesign (Ryan Schmidt), pixilla (Bradley Giesbrecht)
Port: mysql5


Hi guys:

I wanted to add a local mysql5-server but could not make a connection to it. What I've found is that it is ignoring the configure directive ('--with-unix-socket-path=/opt/local/var/run/mysql5/mysqld.sock ') and looking for the socket in tmp:

 CT-MBP11:~ craigtreleaven$ mysql5 --help |grep ^socket
 socket                            /tmp/mysql.sock

I've rebuilt msyql5 (twice) with no change. I'll attach the debug build output from the most recent attempt.

Is it possibly a permissions issue? I've had mysql5 installed on this machine since @5.1.61_0 although it has always been used to access a remote server. Permissions on /opt/local/var/run/mysql5 are 0755. It was only a few days ago that I installed mysql5-server and experienced this issue.

Attachments (1)

mysql5.1.72 debug build (200.7 KB) - added by ctreleaven (Craig Treleaven) 7 years ago.

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by ctreleaven (Craig Treleaven)

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

The mysql5 port has been deprecated for years. Please use a modern mysql port (mysql51, mysql55, mysql56, mariadb or percona) and let us know if the problem persists there.

comment:2 Changed 7 years ago by ctreleaven (Craig Treleaven)

I understand and when the next major version of mythtv is released, I'll revise the port to use a modern version.

BTW, I replaced my 'database server' machine a couple of months ago and did a fresh install of all the software. It doesn't exhibit this problem:

MediumMini:~ mytthtv$ port installed mysql5
The following ports are currently installed:
  mysql5 @5.1.72_0 (active)
MediumMini:~ mytthtv$ mysql5 --help |grep ^socket
socket                            (No default value)

Any suggestions on how to get the older machine to behave like the new one? ;)

Perhaps mysql5 should be modified so that port info highlights that it is to be phased out?

comment:3 Changed 7 years ago by ctreleaven (Craig Treleaven)

pixilla's comment in email sparked me to look for other my.cnf files. There was an old config file in /private/etc/my.cnf. It is dated in 2010, before I started to use MacPorts. In fact, before I bought this machine. Migration Assistant must have copied it over from my former Mac.

After deleting this file, mysql5 is behaving as expected. Sorry for the noise; please close the ticket.


comment:4 Changed 7 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

Ok, great!

Note: See TracTickets for help on using tickets.