Hi
Another thing that may help,
When I restart the postgres db, then I have a little bit of "grace" time
(the memory free field is also lifted a bit).
I can run the crons and then after an hour or two the status returns to
regular... "out of memory" errors.
Thanks!
On Wed, Sep 26, 2012 at 11:36
Hi
I contact amazon with this issue.
What can I check for the fragmented memory issue?
Thanks (:
On Wed, Sep 26, 2012 at 11:11 PM, Scott Marlowe wrote:
> OK then I'm lost. It's got to either be a bug in how amazon ec2
> instances work or severely fragmented memory because you've got a TON
> of
OK then I'm lost. It's got to either be a bug in how amazon ec2
instances work or severely fragmented memory because you've got a TON
of kernel cache available.
On Wed, Sep 26, 2012 at 3:00 PM, Shiran Kleiderman wrote:
> Hi
> Yes, same machine.
>
> Thanks for your help.
>
>
> On Wed, Sep 26, 201
Hi
Yes, same machine.
Thanks for your help.
On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe wrote:
> On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman
> wrote:
> > Hi
> > Thanks again.
> > Right now, this is free -m and ps aux and non of the crons can run -
> can't
> > allocate memory.
>
> OK
On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman wrote:
> Hi
> Thanks again.
> Right now, this is free -m and ps aux and non of the crons can run - can't
> allocate memory.
OK, so is the machine you're running free -m on the same as the one
running postgresql and the same one you're running cr
