Hi,
Finally you seem to say that you 've setting max_connections with a
limit.
Can you tell how many 100 or 200 ?
Also you say :
> Here's the configuration:
> MySQL Ver 12.21 Distrib 4.0.14, for pc-linux (i686)
> PHP 4.3.2
> Red Hat 9.0
Have you enable QUERY CACHE feature with MySQL 4.0.14 ?
Regards
Thierno6C
-----Original Message-----
From: Parker Morse [mailto:morse@stripped]
Sent: vendredi 5 septembre 2003 15:01
To: mysql@stripped
Subject: SOLVED Re: MySQL 4.0.14 stops responding to PHP 4.3.2
On Thursday, Sep 4, 2003, at 12:47 US/Eastern, Parker Morse wrote:
> No, it turns out this is not the key. With mysql_connect() I'm
> actually failing MORE often than with mysql_pconnect - so far it
> hasn't stayed up 15 minutes without error. (Fortunately, I have a cron
> job checking on it and restarting.)
However, this did put me on to the problem. I was tripping resource
limits. When I was first setting up the server and getting the
individual sites/users working in the mysql.user table, I saw the
max_connections column set to 0 and thought that was a problem; I
didn't realize that 0 meant "no limit". So I set a limit. I was running
up on the connection limits, which meant mysqld was refusing further
connections until my server restart reset the counts to 0.
With mysql_connect I had more connections, and thus reached the limit
faster.
Now I have reset the max_connections numbers to 0, and I haven't had a
failure in twenty hours, so I think I can call this problem solved.
Thanks for your help. In the course of sorting it out, I also learned a
good deal about debugging mysql errors gracefully in PHP.
pjm
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=1
