Memory capacity is currently set to 512MB on our Hardy RT VM. CPU is
capped to a whole core for itself (so, something like 2.8GHz). Usage
is practically none. I'm not so sure memory is the issue, but I'll
bump the VM's memory up and start pounding the Hardy RT VM and see if
that fixes it.
On
Same error is occurring with 1GB of memory on the VM. Everything else
in Apache works just fine, but RT is dead until I restart Apache2.
On Wed, May 20, 2009 at 9:13 AM, Kage kagekon...@gmail.com wrote:
Memory capacity is currently set to 512MB on our Hardy RT VM. CPU is
capped to a whole
Kage wrote:
Same error is occurring with 1GB of memory on the VM. Everything else
in Apache works just fine, but RT is dead until I restart Apache2.
As I said before:
But I would start by looking for more clues when the system is in the not
working state. Look at memory usage, CPU usage,
Well, to reiterate what I said, I did try other Apache2 pages while it
was broken. They load just fine with no errors, including Perl
scripts. CPU load is 0%, Load is 0.01 or around there across the
board. Memory is about the same as after the VM boots up (about 100MB
in use). The logs say
I know you said you don't suspect a memory issue on your end, but I have
to report, once I upped our 3.8.2 VMs from 256M to 1G per, I have yet to
see the error repeated. Something that may be a quite different between
our systems is user load. I'm the only one poking around on ours.
Kage wrote:
Well, to reiterate what I said, I did try other Apache2 pages while it
was broken. They load just fine with no errors, including Perl
scripts. CPU load is 0%, Load is 0.01 or around there across the
board. Memory is about the same as after the VM boots up (about 100MB
in use).
I hate to bump my own thread, but I kind of need to find a fix for
this extremely soon. My bosses are breathing down my neck. Thanks!
On Mon, May 18, 2009 at 10:14 AM, Kage kagekon...@gmail.com wrote:
Also sent this mail to rt-devel...
First and foremost, I use 3.6.5 since that's what exists
Kage wrote:
Essentially what happens is I can use RT for an extended period of
time (from 1 hour to 10 hours), and eventually, it'll stop working,
resulting in a 500 Internal Server Error.
Sounds like resource exhaustion of some kind, perhaps a memory or some other
type of leak in mason, perl,
Kage,
I'm seeing similar issues with 3.8.2. Take a look at my post
apache/mason software caused connection abort.
Running with Tom's thought, maybe we can compare setups. My two systems
are identical builds of a gentoo stage 4 on VMWare ESX3i. My default vm
resources are pretty low. Each
Also sent this mail to rt-devel...
First and foremost, I use 3.6.5 since that's what exists in Ubuntu
Hardy's repository.
Essentially what happens is I can use RT for an extended period of
time (from 1 hour to 10 hours), and eventually, it'll stop working,
resulting in a 500 Internal Server
10 matches
Mail list logo
