Problem with Mysql 4.0.18 + Apache
Hello:
I posted this before but I have made some changes since then (not that
they helped much). I have a Debian (woody) server running a good sized
database (7.2GB of db files), Mysql 4.0.18. I am running Apache 1.3.29
+ perl and using mysql as the backend. In my.cnf, I set
max_connections=300.
Here's the problem. I had the site up for weeks, with everything running
perfectly. Ordinarily there would be about 11 mysql processes running
(according to ps). However, when I switched my domain name over to this
server, immediately the number of mysql processes increases to over 150,
and the site crashes. Formerly I'd get errors like
DBI connect('yada yada, ...) failed: Too many connections at DB.pm line 25
However once I set max_connections to 300 (default is 90), mysql will
still accept connections, but it is still way too slow to be usable, so
the website becomes unreachable.
I know that the site is getting virtually no traffic, so the problem is
not that it is being overloaded. I have tried this scenario at least a
dozen times, and the same thing always happens. Is this a known issue
with Apache + mysql 4.0.18?
Ryan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with Mysql 4.0.18 + Apache
Hello:
I posted this before but I have made some changes since then (not that
they helped much). I have a Debian (woody) server running a good sized
database (7.2GB of db files), Mysql 4.0.18. I am running Apache 1.3.29
+ perl and using mysql as the backend. In my.cnf, I set
max_connections=300.
Here's the problem. I had the site up for weeks, with everything
running perfectly. Ordinarily there would be about 11 mysql processes
running (according to ps). However, when I switched my domain name over
to this server, immediately the number of mysql processes increases to
over 150, and the site crashes. Formerly I'd get errors like
DBI connect('yada yada, ...) failed: Too many connections at DB.pm line
25
However once I set max_connections to 300 (default is 90), mysql will
still accept connections, but it is still way too slow to be usable, so
the website becomes unreachable.
I know that the site is getting virtually no traffic, so the problem is
not that it is being overloaded. I have tried this scenario at least a
dozen times, and the same thing always happens. Is this a known issue
with Apache + mysql 4.0.18?
Ryan
Are you using mod_perl by any chance? You might check to make sure that
you are calling 'disconnect' at the end of each call. With mod_perl
connections may stay open. I see a similar problem with php. Also,
mod_perl will cause the children to be larger.
--
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with Mysql 4.0.18 + Apache
Hello:
This is my first time posting so bear with me. I have a Debian (woody)
server running a good sized database (7.2GB), Mysql 4.0.18. I am
running Apache 1.3.29 + perl and using mysql as the backend. Here's the
problem. I had the site up for weeks, with everything running
perfectly. Ordinarily there would be about 11 mysql processes running
(according to ps). However, when I switched my domain name over to this
server, immediately the number of mysql processes increases to over 100,
and the site crashes, giving errors like
DBI connect('yada yada, ...) failed: Too many connections at DB.pm line 25
Also I can't connect to the mysql commandline, I get the error
ERROR 1040: Too many connections.
I know that the site is getting virtually no traffic, so the problem is
not that it is being overloaded. I have tried this scenario at least a
dozen times, and the same thing always happens. Is this a known issue
with Apache + mysql 4.0.18?
Ryan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
