From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020227 Description of problem: mysql is set to refer to mysql.sock in /var/lib/mysql(mysql's home directory). In the past it was set to /tmp, and /tmp is the mysql default. I believe this change was made to clean up the /tmp directory and maybe add security. After upgrading to php-*-4.0.6-12 it again tries to refer to mysql.sock in /tmp even though the latest redhat mysql's my.cnf refers to it in /var/lib/mysql. This will break any website that depends on php-mysql and is using the standard configuration. Two workarounds are to either make a symlink from /var/lib/mysql.sock to /tmp/mysql.lock, not a great way. Another is to change /etc/my.cnf and change the socket= line. Version-Release number of selected component (if applicable): 4.0.6-12 How reproducible: Always Steps to Reproduce: 1. Upgrade to php-*-4.0.6-12 2. Go to a url that depends on php to read data out of mysql 3. See the error message about no able to find /tmp/mysql.sock Actual Results: See the error message about no able to find /tmp/mysql.sock Expected Results: See no error message and the page to load normally. Additional info:
*** This bug has been marked as a duplicate of 60515 ***