hi list, this is not understandable. Warning: mysql_connect(): Too many connections in /home/mystop/public_html/includes/database.mysql.inc on line 31 Too many connections what does this mean? thank you.
This message means that MySQL has received more requests for connections than it is willing to deal with.
This could happen if your MySQL server is particularly busy, but most likely is a result of not allowing persistent connections for PHP (mysql.allow_persistent =On in php.ini)
Cheers, Djun
On 27-Dec-2005, at 6:25 AM, Mohammed al-shar' wrote:
hi list, this is not understandable. Warning: mysql_connect(): Too many connections in /home/mystop/ public_html/includes/database.mysql.inc on line 31 Too many connections what does this mean? thank you. -- [ Drupal support list | http://lists.drupal.org/ ]
At 9:53 AM -0500 27/12/05, puregin wrote:
likely is a result of not allowing persistent connections for PHP (mysql.allow_persistent =On in php.ini)
In my experience allowing persistent connections causes this problem. When enabled you have each apache process holding open a connection to each database that process has accessed. This exponential growth in idle connections quickly leads to resource exhaustion.
...Richard.
Interesting... I could see that happening in certain situations. I guess this would depend on the traffic profile you're seeing and your apache configuration.
Sounds like a little experimentation is in order. If you currently allow persistent connections, turn them off; otherwise, turn them on and see if the problem goes away :)
Ah, I love the scientific method ;)
Djun
On 27-Dec-2005, at 3:26 PM, Richard Archer wrote:
At 9:53 AM -0500 27/12/05, puregin wrote:
likely is a result of not allowing persistent connections for PHP (mysql.allow_persistent =On in php.ini)
In my experience allowing persistent connections causes this problem. When enabled you have each apache process holding open a connection to each database that process has accessed. This exponential growth in idle connections quickly leads to resource exhaustion.
At 5:29 PM -0500 27/12/05, puregin wrote:
Interesting... I could see that happening in certain situations. I guess this would depend on the traffic profile you're seeing and your apache configuration.
If your server is dedicated to hosting Drupal and there is only one or two databases in use then persistent connections may be useful.
I have 100 databases on my server and if I enable persistent connections mysql starts throwing "too many connections" errors after about 8 hours of operation.
I profiled performance before disabling pconnect and the peformance hit was about 0.001 seconds per connect. And that's on a 6 year old server... on modern hardware you would hardly notice it.
...R.
This is good to know. We should include this in the documentation somewhere....
Richard, could you write a paragraph for one of the existing handbook pages, or create a new one if necessary?
Djun
On 27-Dec-2005, at 6:42 PM, Richard Archer wrote:
At 5:29 PM -0500 27/12/05, puregin wrote:
Interesting... I could see that happening in certain situations. I guess this would depend on the traffic profile you're seeing and your apache configuration.
If your server is dedicated to hosting Drupal and there is only one or two databases in use then persistent connections may be useful.
I have 100 databases on my server and if I enable persistent connections mysql starts throwing "too many connections" errors after about 8 hours of operation.
I profiled performance before disabling pconnect and the peformance hit was about 0.001 seconds per connect. And that's on a 6 year old server... on modern hardware you would hardly notice it.
At 7:11 PM -0500 27/12/05, puregin wrote:
This is good to know. We should include this in the documentation somewhere....
Richard, could you write a paragraph for oneof the existing handbook pages, or create a new one if necessary?
Suggestions welcome.
...R.
hello richard and all, yes, actually, it appeared to me that the problem was on my shared server. my site is running on a shared server, and so the whole sql database was down. I can't afford dedicated hosting plan. hope it never happens again. thanks for the help. regards mohammed al-shar' www.mystop.net ----- Original Message ----- From: "Richard Archer" drupal.org@juggernaut.com.au To: support@drupal.org Sent: Wednesday, December 28, 2005 1:42 AM Subject: Re: [support] too many connections
At 5:29 PM -0500 27/12/05, puregin wrote:
Interesting... I could see that happening in certain situations. I guess this would depend on the traffic profile you're seeing and your apache configuration.
If your server is dedicated to hosting Drupal and there is only one or two databases in use then persistent connections may be useful.
I have 100 databases on my server and if I enable persistent connections mysql starts throwing "too many connections" errors after about 8 hours of operation.
I profiled performance before disabling pconnect and the peformance hit was about 0.001 seconds per connect. And that's on a 6 year old server... on modern hardware you would hardly notice it.
...R.
[ Drupal support list | http://lists.drupal.org/ ]
-
Mohammed al-shar' -
puregin -
Richard Archer