Thread: Re: [GENERAL] Memory issues
On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman <shirank1@gmail.com> 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 cron jobs on and the same one you're running apache on? Also please don't remove the cc for the list, others might have an insight I'd miss. > cif@domU-12-31-39-08-06-20:~$ free -m > total used free shared buffers cached > Mem: 17079 12051 5028 0 270 9578 > -/+ buffers/cache: 2202 14877 > Swap: 511 0 511 >
Hi
Yes, same machine.
Thanks for your help.
--
On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> Thanks again.OK, so is the machine you're running free -m on the same as the one
> Right now, this is free -m and ps aux and non of the crons can run - can't
> allocate memory.
running postgresql and the same one you're running cron jobs on and
the same one you're running apache on?
Also please don't remove the cc for the list, others might have an
insight I'd miss.
> cif@domU-12-31-39-08-06-20:~$ free -m
> total used free shared buffers cached
> Mem: 17079 12051 5028 0 270 9578
> -/+ buffers/cache: 2202 14877
> Swap: 511 0 511
>
Best,
Shiran Kleiderman+972 - 542380838
Skype - shirank1
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 <shirank1@gmail.com> wrote: > Hi > Yes, same machine. > > Thanks for your help. > > > On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe <scott.marlowe@gmail.com> > wrote: >> >> On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman <shirank1@gmail.com> >> 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 cron jobs on and >> the same one you're running apache on? >> >> Also please don't remove the cc for the list, others might have an >> insight I'd miss. >> >> > cif@domU-12-31-39-08-06-20:~$ free -m >> > total used free shared buffers >> > cached >> > Mem: 17079 12051 5028 0 270 >> > 9578 >> > -/+ buffers/cache: 2202 14877 >> > Swap: 511 0 511 >> > > > > > > -- > Best, > Shiran Kleiderman > +972 - 542380838 > Skype - shirank1 > -- To understand recursion, one must first understand recursion.
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 <scott.marlowe@gmail.com> 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 kernel cache available.--
On Wed, Sep 26, 2012 at 3:00 PM, Shiran Kleiderman <shirank1@gmail.com> wrote:
> Hi
> Yes, same machine.
>
> Thanks for your help.
>
>
> On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe <scott.marlowe@gmail.com>
> wrote:
>>
>> On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman <shirank1@gmail.com>
>> 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 cron jobs on and
>> the same one you're running apache on?
>>
>> Also please don't remove the cc for the list, others might have an
>> insight I'd miss.
>>
>> > cif@domU-12-31-39-08-06-20:~$ free -m
>> > total used free shared buffers
>> > cached
>> > Mem: 17079 12051 5028 0 270
>> > 9578
>> > -/+ buffers/cache: 2202 14877
>> > Swap: 511 0 511
>> >
>
>
>
>
> --
> Best,
> Shiran Kleiderman
> +972 - 542380838
> Skype - shirank1
>
To understand recursion, one must first understand recursion.
Best,
Shiran Kleiderman+972 - 542380838
Skype - shirank1
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 PM, Shiran Kleiderman <shirank1@gmail.com> wrote:
HiI 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 <scott.marlowe@gmail.com> 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 kernel cache available.--
On Wed, Sep 26, 2012 at 3:00 PM, Shiran Kleiderman <shirank1@gmail.com> wrote:
> Hi
> Yes, same machine.
>
> Thanks for your help.
>
>
> On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe <scott.marlowe@gmail.com>
> wrote:
>>
>> On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman <shirank1@gmail.com>
>> 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 cron jobs on and
>> the same one you're running apache on?
>>
>> Also please don't remove the cc for the list, others might have an
>> insight I'd miss.
>>
>> > cif@domU-12-31-39-08-06-20:~$ free -m
>> > total used free shared buffers
>> > cached
>> > Mem: 17079 12051 5028 0 270
>> > 9578
>> > -/+ buffers/cache: 2202 14877
>> > Swap: 511 0 511
>> >
>
>
>
>
> --
> Best,
> Shiran Kleiderman
> +972 - 542380838
> Skype - shirank1
>
To understand recursion, one must first understand recursion.--
Best,
Shiran Kleiderman+972 - 542380838
Skype - shirank1