search for: oomkilladj

...Info: pop3-login: Login: user=<DDDDDDDD>, method=PLAIN, rip=66.165.6.233 dovecot: Apr 17 07:49:12 Info: pop3-login: Login: user=<EEEEEEEE>, method=PLAIN, rip=71.222.224.38 From /var/log/messages: Apr 17 07:48:42 mail2 kernel: pop3-login invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 Apr 17 07:48:42 mail2 kernel: [<c0450ace>] out_of_memory+0x3b/0x179 Apr 17 07:48:42 mail2 kernel: [<c0451f01>] __alloc_pages+0x1fe/0x27e Apr 17 07:48:42 mail2 kernel: [<c05c6696>] tcp_sendmsg+0x4e7/0x994 Apr 17 07:48:42 mail2 kernel: [<c05dd85d>] inet_sendmsg+0x35/0x3f...

...el5.centos installed php-pear-MDB2-Driver-mysql.noarch 1.4.1-3.el5.centos installed squirrelmail.noarch 1.4.8-5.el5.centos.3 installed Dmesg: Apr 2 17:18:28 s_local at webmail kernel:init invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0 Apr 2 17:18:28 s_local at webmail kernel: Apr 2 17:18:28 s_local at webmail kernel:Call Trace: Apr 2 17:18:28 s_local at webmail kernel:[<ffffffff802bc998>] out_of_memory+0x8b/0x203 Apr 2 17:18:28 s_local at webmail kernel:[<ffffffff8020f657>] __alloc_pages+0x245/0x2ce Apr 2 17...

...e unresponsive. I went to the console and couldn't get it to respond, so I had to POWER OFF! Ugh! (Note: this script, get-backup, ran fine on a CentOS 4.5 system) Looking through /var/log/messages, I see: Jan 23 12:52:14 DoyleBrunson kernel: ps invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 Jan 23 12:52:14 DoyleBrunson kernel: [<c0455946>] out_of_memory+0x72/0x1a4 Jan 23 12:52:14 DoyleBrunson kernel: [<c0456d71>] __alloc_pages+0x201/0x282 Jan 23 12:52:14 DoyleBrunson kernel: [<c049c8af>] proc_info_read+0x0/0x96 Jan 23 12:52:14 DoyleBrunson kernel: [<c0456e17...

just had a server hang on me...seems pretty clearly that some process stole all the RAM (clamd?) Jul 30 16:26:04 srv1 kernel: auditd invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=-17 Jul 30 16:26:08 srv1 kernel: [<c0457d36>] out_of_memory+0x72/0x1a4 Jul 30 16:26:08 srv1 kernel: [<c0459161>] __alloc_pages+0x201/0x282 Jul 30 16:26:08 srv1 kernel: [<c045a3bf>] __do_page_cache_readahead +0xc4/0x1c6 Jul 30 16:26:08 srv1 kernel: [<c0438ecf>] wake_futex...

...em: empty 46 pagecache pages Swap cache: add 8934611, delete 8934611, find 7869746/7929974, race 11+11 Free swap = 0kB Total swap = 4096564kB Free swap: 0kB 196064 pages of RAM 13511 reserved pages 5948 pages shared 0 pages swap cached kthread invoked oom-killer: gfp_mask=0xd0, order=1, oomkilladj=0 Call Trace: [<ffffffff800c3a6a>] out_of_memory+0x8e/0x2f5 [<ffffffff8000f2eb>] __alloc_pages+0x245/0x2ce [<ffffffff8002303f>] alloc_page_interleave+0x3d/0x74 [<ffffffff8003c061>] __get_free_pages+0xe/0x71 [<ffffffff8001eb82>] copy_process+0xc6/0x15b8 [<ffff...

HI: I run glusterfs with four nodes, 2x2 Distributed-Replicate. I mounted it via fuse and did some test, it was ok. However when I mounted it via nfs, a problem was found: When I copied 200G files to the glusterfs, the glusterfs process in the server node(mounted by client) was killed because of OOM, and all terminals of the client were hung. Trying to test for many times, I got the