Are there any messages in the Apache-Errorlog or in the one of MySQL.
Maybe you are opening connections and don't close them, ... . You could
also run the DBI in Debugging mode. Do you use Apache::DBI?
Tom
Alejandro Galue wrote:
Hello All,
I'm using Fedora Core 3 with this packages version (RPM):
httpd-2.0.52-3.1
mod_perl-1.99_16-3
perl-DBI-1.40'5
perl-DBD-MySQL-2.9004-4
libdbi-0.6.5-10
libdbi-dbd-mysql-0.6.5-10
mysql-4.1.9-1
mysql-server-4.1.9-1
mysqlclient10-3.23.58-4
I downloaded source rpm for Mysql from fedora-development and rebuild on a
updated fedora core 3.
I have an application that run a script to read and modify mysql (this part
works great), and the web interface for this application. This web interface
was created totally with mod_perl.
After a certain amount of time, it cannot be possible to use the database
frontend via web becase it cannot connect to database. This problem appears
when we run the application in a limited RAM machine - 128 - 256MB; before
that we have never experience the problem. It has been working ok in HW with
RAM between 386MB and 512MB RAM.
I can enter to database manually and check status and mysql is up; but I
need to restart apache to have the Web front-end working properly again.
After some hours the failure shows up again.
Anyone have any idea of what is happening here ?
My guest is : the problem should be related to perl-DBI or mod_perl or maybe
the configuracion of modperl or mysql. My questions in this case:
- Does it sound like the place to look for the problem ?
- Any tips on how to turn on the debugging on this components ? How to
figure out which one is responsible for the failure and why ?
Thanks in advance,
Alejandro Galue.
