[request-tracker-maintainers] Bug#649864: request-tracker4: modperl apache2 config leads to memory full
Olivier Berger
olivier.berger at it-sudparis.eu
Thu Nov 24 11:57:30 UTC 2011
Source: request-tracker4
Version: 4.0.4-1
Severity: normal
Hi.
On a 2Gb VM, I'm running a rebuilt package of RT 4 on a squeeze + backports system.
I configured the apache config to use mod_perl.
The memory used by the apache process is reported like this in top :
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
18864 www-data 20 0 827m 345m 4428 S 0.0 17.2 0:08.15 apache2
18836 www-data 20 0 828m 345m 4388 S 0.0 17.2 0:08.64 apache2
18828 root 20 0 517m 322m 6124 S 0.0 16.1 0:03.40 apache2
18834 www-data 20 0 516m 316m 692 S 0.0 15.8 0:00.00 apache2
27804 mysql 20 0 173m 39m 7568 S 0.0 2.0 0:27.58 mysqld
I fear there's a problem with the memory management of RT, or RT with mod_perl.
I used to run RT 3.8 from squeeze before, and had experienced problems with memory full and actions not being executed because of memory exhaustion reported in the logs.
I tried to upgrade in order to see if things would be improving with the next version.
Is this a known problem ?
Thanks in advance.
Best regards,
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (300, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
More information about the pkg-request-tracker-maintainers
mailing list