Michael Winston [EMAIL PROTECTED] wrote:
Okay, so the first thing to try is obviously enlarge the
max_connections.
Have you tried this?
Yes. It's set to 400 (a number we will never reach unless there's some
sort of logjam). max_connect_errors is set to 200.
Is it a webserver backend
Michael Winston [EMAIL PROTECTED] wrote:
Okay, so the first thing to try is obviously enlarge the max_connections.
Have you tried this?
Is it a webserver backend database?
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net
On Sep 2, 2004, at 6:04 AM, Egor Egorov wrote:
Michael Winston [EMAIL PROTECTED] wrote:
Okay, so the first thing to try is obviously enlarge the
max_connections.
Have you tried this?
Yes. It's set to 400 (a number we will never reach unless there's some
sort of logjam). max_connect_errors is
Hi-
We've been running into a pretty serious problem for the past several
versions of mysql 4.0 running on OS X (both client and server). Every
once in a while we wake up to find the too many connections error
coming up. There really aren't too many connections (we have our max
set to 99) -
Is it a too many connections or Host blocked because of many connection
erros? If it is the later you have reached max_connect_errors and need to
issue flush-hosts.
-Original Message-
From: Michael Winston
To: [EMAIL PROTECTED]
Sent: 9/1/04 11:02 AM
Subject: bad too many connections error
Michael Winston wrote:
Hi-
We've been running into a pretty serious problem for the past several
versions of mysql 4.0 running on OS X (both client and server). Every
once in a while we wake up to find the too many connections error
coming up. There really aren't too many connections (we
I think that there is an error in your code.
I have had this problem with a small application I wrote:
The problem arises when you don't send the quit command to mysql
before dropping tcp.
You must send a quit command in every case (if you opened a socket).
I can not be more precise because i
On Sep 1, 2004, at 9:10 AM, V. M. Brasseur wrote:
Michael Winston wrote:
Hi-
We've been running into a pretty serious problem for the past several
versions of mysql 4.0 running on OS X (both client and server).
Every once in a while we wake up to find the too many connections
error coming up.
Michael Winston wrote:
On Sep 1, 2004, at 9:10 AM, V. M. Brasseur wrote:
Michael Winston wrote:
Hi-
We've been running into a pretty serious problem for the past several
versions of mysql 4.0 running on OS X (both client and server).
Every once in a while we wake up to find the too many
Not if the host that is blocked is `localhost`.
-Original Message-
From: Michael Winston
To: Victor Pendleton
Cc: '[EMAIL PROTECTED] '
Sent: 9/1/04 11:24 AM
Subject: Re: bad too many connections error (os x)
This would make sense since they all the connections are coming from
the same
or Host blocked because of many connection
erros? If it is the later you have reached max_connect_errors and need
to
issue flush-hosts.
-Original Message-
From: Michael Winston
To: [EMAIL PROTECTED]
Sent: 9/1/04 11:02 AM
Subject: bad too many connections error (os x)
Hi-
We've been running
This also may caused by the TTL of the http socket and the launched
zombie forks by the http/php server ( the FIN_WAIT_2 problem!!). Thats
what it happend to me . I dunno who waited for who, and became zombie,
was it MySQL waiting for timeout or was socket wating to timeout.
You can test this
12 matches
Mail list logo
