Problems with MySQL after updating PHP with custombuild 2.0

[medieja]

I tried that but unfortunately it didn't make a difference. Also, the value didn't change to /tmp/mysql.sock. Should I change php.ini directly or something else?

 

[SeLLeRoNe]

Is DA able to connect to MySQL? (On User Level if you got to MySQL Management are you able to see DB or you got an error?)

Can you paste the output for:
grep mysql.sock /etc/my.cnf* -R

On my box the sock is in /var/lib/mysql/mysql.sock

This is a CentOS box, i would rather suggest you to change MySQL configuration instead of the PHP one.

Best regards

 

[medieja]

Yes, I can. It shows all of my databases without any errors. The output of the command is:

socket=/tmp/mysql.sock
socket=/tmp/mysql.sock

Kind regards!

 

[SeLLeRoNe]

Ok, what about the output for:
grep mysql.sock /usr/local/directadmin/conf/*

Best regards

 

[medieja]

The output is:

/usr/local/directadmin/conf/mysql.conf:socket=/tmp/mysql.sock

 

[SeLLeRoNe]

mmmmh, what about this:
grep "sock" /usr/local/lib/php*

Best regards

 

[medieja]

grep: /usr/local/lib/php*: No such file or directory

Kind regards

 

[SeLLeRoNe]

What PHP version are you usin?

 

[medieja]

PHP 7.0 and PHP 5.6 both FPM.

Kind regards

 

[Arieh]

I had some issues with this as well, on Debian 7.

mysqldump didn't work (complaining about the .sock file), after a restart, websites didn't work anymore either. Changed localhost -> 127.0.0.1 in web app, and the website did work again.

I messed around with restarting, fixing .err errors.. nothing helped to fix the localhost + mysqldump.

Then I just updated mysql in CB 2.0 from mysql-5.6.33 to mysql-5.6.34 and it all went back to normal: localhost working, and mysqldump as well.

So I guess this should be really CB / server / install things related.

 

[SeLLeRoNe]

Does both have the same issue? Can you try to update/re-build both as Arieh suggested?

Best regards

 

[duke28]

./build rewrite_confs