Bug 60542 - failure on php to connect to mysql after updating php.
Summary: failure on php to connect to mysql after updating php.
Status: CLOSED DUPLICATE of bug 60515
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Phil Copeland
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2002-03-01 15:45 UTC by Drew Bertola
Modified: 2007-04-18 16:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-03-04 06:25:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
one line patch to change default mysql.sock location in configure script (384 bytes, patch)
2002-03-04 06:24 UTC, Alastair Tse
no flags Details | Diff

Description Drew Bertola 2002-03-01 15:45:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205

Description of problem:
Error shown in web page is something like "php cannot connect to mysql through

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1. make sure /etc/php.ini has no value for mysql.default_socket
2. latest php, mysql, apache (php-4.0.6-12.i386.rpm)
3. run a mysql_connect

Actual Results:  error message like: "php cannot connect to mysql through

Expected Results:  Connection success.  The applied rpms for the php security
fix caused this.

Additional info:

This doesn't cause a crash, but it does take down the web server fuctionality of
php+mysql enabled sites when apache gets a HUP (after logrotate).  I suppose I
would have found the problem earlier if I restarted apache manually after the
upgrade, but I didn't want to do that.  My production site was down for 6 hours.

Comment 1 Need Real Name 2002-03-01 17:59:03 UTC
Untill they get this fixed you can create a symlink from
/var/lib/mysql/mysql.sock to /tmp/mysql.sock. that got me back up and running.

Is there a config file to fix this or is it compiled into a binary?

Comment 2 Alastair Tse 2002-03-04 06:24:16 UTC
Created attachment 47282 [details]
one line patch to change default mysql.sock location in configure script

Comment 3 Alastair Tse 2002-03-04 06:25:24 UTC
of course - that means you have to apply that patch before rebuilding that RPM
:) But the softlink from /tmp/mysql.sock works just as well.

Comment 4 Phil Copeland 2002-03-04 19:17:42 UTC

*** This bug has been marked as a duplicate of 60515 ***

Note You need to log in before you can comment on or make changes to this bug.