[Pacemaker] lrmd fork: cannot allocate memory

Wed Feb 12 14:56:09 UTC 2014

Thanks Lars,

This is sar on node 1

11:10:01       958244 131164608     99,27   2282996 115595888  87761480     32,95

11:20:01       903164 131219688     99,32   2289980 115604020  87799716     32,97

11:30:01      1101560 131021292     99,17   2298388 115513776  87693196     32,93

11:40:01      1075876 131046976     99,19   2304764 115516508  87698880     32,93

11:50:01      3547640 128575212     97,31   2311380 115539592  87406308     32,82

12:00:01       382812 131740040     99,71   2320756 115289668  95762708     35,95                   <------

Media:        1053500 131069352     99,20   2218531 115382679  87977415     33,03

12:05:32          LINUX RESTART

12:10:01    kbmemfree kbmemused  %memused kbbuffers  kbcached  kbcommit   %commit

12:20:01    130170068   1952784      1,48     38216    297912    362208      0,14

12:30:01    119692256  12430596      9,41    161532   5032616  78708160     29,55

12:40:01    118970064  13152788      9,95    182136   5390288  78842992     29,60

12:50:01    118899184  13223668     10,01    187440   5425376  78874608     29,61

13:00:01    118810216  13312636     10,08    191460   5477888  78896804     29,62

Thanks

Walter

-----Original Message-----
From: Lars Marowsky-Bree [mailto:lmb at suse.com]
Sent: mercoledì 12 febbraio 2014 13:19
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] lrmd fork: cannot allocate memory

On 2014-02-12T11:57:16, walter.pisani at erptech.it<mailto:walter.pisani at erptech.it> wrote:

This is still 1.1.7 with the LRM from cluster-glue.

All the log messages point to, well, an out-of-memory error on that node.

> Can this error "Cannot allocate memory" to indicate that there cannot be any memory allocated for a new Resource Agent instance ?

That's exactly what it means.

> I have 128Gb of RAM

Yes, but apparently, no free memory. I'd start monitoring memory usage on those servers to make sure you get notified ahead of time next time, and can also identify the culprit.

> OS Sles 11 SP2 kernel 3.0.80-0.7-default

For a production SAP system, the best way to get assistance is via NTS, by the way. I don't *always* respond to mailing list posts immediately

;-)

I'd also suggest to consider updating, as always a good idea.

Best,

    Lars

--

Architect Storage/HA

SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________

Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>

http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org

Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

Bugs: http://bugs.clusterlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140212/0e92f3ef/attachment.htm>