On Fri, Jun 20, 2003 at 05:50:14PM -0700, Jimmy Wales wrote:

I rebooted both *.197 and *.199, mostly because I'm clueless these days.

I don't know the password for root mysql account, for example. Well, I used to know it.

This is twice today that the same thing happened. Any clues as to what the problem is?

From what I understood from some mails between Brion and Lee, there

is a maximum number of concurrent connections defined for mysql. This number is set to a higher value than the number of concurrent apache processes. This is to prevent that the mysql server is killed by a fork-bombing client application.

There must be something like

set-variable = max_connections=somebignumber

in mysql.conf.

Regards,

JeLuF

Jimmy Wales wrote:

I rebooted both *.197 and *.199, mostly because I'm clueless these days.

I don't know the password for root mysql account, for example. Well, I used to know it.

This is twice today that the same thing happened. Any clues as to what the problem is?

Forget the max_connection limit. It was to early in the morning, the error that was reported (and the solving: mysqladmin flush-hosts) has nothing to do with the max connection limit. The given solution looks best, it's possible reasons are in the mysql-handbook. Pity if you can't get on the password.

The problem on the es-wiki is still not fixed. Anyone with a proper password can run ''repair table searchindex'' on the proper DB? It was not the best way to fix it, but the way anyone can handle, who's able to connect to the es-db.