You should add debug-code to your script and add
* * * * * root mysql -e 'show processlist' >/tmp/mysql_processlist_debug_`date +%s`.txt
to your /etc/crontab in order to log the processlist once every minute in a txt-file in /tmp
Jan
[EMAIL PROTECTED] wrote:
Thanks for the two responses.
William Mussatto said:
Are you running mod_perl?
Yes I am, with Perl 5.8.3.
Victor Pendleton said:
What does mysql "show processlist" look like?
Here is what it looks like currently, but the system is not in its "unresponsive" phase right now. I can't force it to go all wonky on me, it will probably be tomorrow before the process count explodes again.
+----+---------+-----------+---------+---------+------+-------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+---------+-----------+---------+---------+------+-------+------------------+
| 8 | citidel | localhost | citidel | Sleep | 0 | | NULL |
| 71 | citidel | localhost | citidel | Sleep | 2192 | | NULL |
| 72 | citidel | localhost | citidel | Sleep | 2141 | | NULL |
| 78 | citidel | localhost | citidel | Sleep | 1503 | | NULL |
| 79 | citidel | localhost | citidel | Sleep | 1503 | | NULL |
| 87 | citidel | localhost | citidel | Sleep | 741 | | NULL |
| 88 | citidel | localhost | citidel | Sleep | 730 | | NULL |
| 89 | citidel | localhost | citidel | Sleep | 607 | | NULL |
| 95 | citidel | localhost | citidel | Query | 0 | NULL | show
processlist |
+----+---------+-----------+---------+---------+------+-------+-----------------
Ryan Richardson said:
-----Original Message----- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: 8/2/04 9:16 AM Subject: Problem with Mysql 4.0.18 + Debian
Hello:
I posted this before but I have not gotten a response. 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 have max_connections=300.
Here's the problem. I had the site up several days, with everything running perfectly. Ordinarily there would be about 11 mysql processes running. However, after a few days of running smoothly, the number of mysql processes increases to over 170, 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've read on this list that people running MySQL w/ FreeBSD can have similar sounding problems. I am wondering if there is a connection.
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.
Ryan
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
