t did. I set ulimit -u to 50
and restarted mysql. It worked fine until max_used_connectsion and the
number of sleeping/persistent connections got up to 45, then it started
throwing off the "Can't create thread" error. Then I did ulimit -u 150 and
restarted mysql again. This time
gt; set-variable = wait_timeout=10
>
> I tried this, and it was a mixed bag. On the one hand, the "Can't create
> thread..." error did indeed go away, and max_used_connections and the
> number of sleeping/persistent connections dropped down well below
> 250. However
and it was a mixed bag. On the one hand, the "Can't create
> thread..." error did indeed go away, and max_used_connections and the
> number of sleeping/persistent connections dropped down well below
> 250. However, making this change caused a new problem: on about ever
Hi Don,
Thanks for the suggestions. Here's what happened.
> Your pconnects are probably sleeping too long.
in /etc/my.cnf:
[mysqld]
set-variable = wait_timeout=10
I tried this, and it was a mixed bag. On the one hand, the "Can't create
thread..." error
On 31-Mar-2003 Mike William wrote:
> After a routine restart of our MySQL 3.23 server today, we began getting
> the following PHP error message during times of moderately high database
> server load:
>
> Warning: MySQL Connection Failed: Can't create a new thread (errno 11).
> If
> you are no
After a routine restart of our MySQL 3.23 server today, we began getting
the following PHP error message during times of moderately high database
server load:
Warning: MySQL Connection Failed: Can't create a new thread (errno 11). If
you are not out of
available memory, you can consult the man
