That sounds like a typical mod_perl-problem. The script is making new
connections and doesn't close the old ones.
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
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
Fournier
www.presence-pc.com
- Original Message -
From: Jan Kirchhoff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 7:43 PM
Subject: Re: Problem with Mysql 4.0.18 + Debian
That sounds like a typical mod_perl-problem. The script is making new
Jocelyn Fournier wrote:
Hi,
A quick fix would be to set the wait_timeout variable in the my.cnf to a
much smaller value than 28800 (default value).
Try to add wait_timeout=60 in the my.cnf for example, the connections should
be automatically closed after 60 secondes if there are not used anymore.
What does mysql show processlist look like?
-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
Victor Pendleton said:
What does mysql show processlist look like?
-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
Ryan,
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
