since we update from syslog-ng 2.0.9 to 2.1.3 we have problems with oom-killer. Jan 27 09:05:17 maya syslog-ng[17897]: syslog-ng starting up; version='2.1.3' Jan 27 09:05:17 maya x2e Jan 27 09:05:17 maya [<ffffffff8025fbdb>] __alloc_pages+0x26b/0x2fe Jan 27 09:05:17 maya [<ffffffff804e328d>] __wait_on_bit_lock+0x5b/0x66 Jan 27 09:05:17 maya [<ffffffff8026164e>] __do_page_cache_readahead+0x79/0x185 Jan 27 09:05:17 maya [<ffffffff8025c504>] filemap_fault+0x14f/0x30c Jan 27 09:05:17 maya [<ffffffff80266c1f>] __do_fault+0x68/0x3aa Jan 27 09:05:17 maya [<ffffffff802686bc>] handle_mm_fault+0x32f/0x67b Jan 27 09:05:17 maya [<ffffffff802226f7>] do_page_fault+0x353/0x6fc Jan 27 09:05:17 maya [<ffffffff804e4639>] error_exit+0x0/0x51 Jan 27 09:05:17 maya Jan 27 09:05:17 maya Mem-info: Jan 27 09:05:17 maya Node 0 DMA per-cpu: Jan 27 09:05:17 maya CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jan 27 09:05:17 maya CPU 1: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jan 27 09:05:17 maya CPU 2: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jan 27 09:05:17 maya CPU 3: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0 Jan 27 09:05:17 maya Node 0 DMA32 per-cpu: Jan 27 09:05:17 maya CPU 0: Hot: hi: 186, btch: 31 usd: 30 Cold: hi: 62, btch: 15 usd: 48 Jan 27 09:05:17 maya CPU 1: Hot: hi: 186, btch: 31 usd: 134 Cold: hi: 62, btch: 15 usd: 32 Jan 27 09:05:17 maya CPU 2: Hot: hi: 186, btch: 31 usd: 42 Cold: hi: 62, btch: 15 usd: 60 Jan 27 09:05:17 maya CPU 3: Hot: hi: 186, btch: 31 usd: 45 Cold: hi: 62, btch: 15 usd: 20 Jan 27 09:05:17 maya Node 0 Normal per-cpu: Jan 27 09:05:17 maya CPU 0: Hot: hi: 186, btch: 31 usd: 58 Cold: hi: 62, btch: 15 usd: 60 Jan 27 09:05:17 maya CPU 1: Hot: hi: 186, btch: 31 usd: 47 Cold: hi: 62, btch: 15 usd: 60 Jan 27 09:05:17 maya CPU 2: Hot: hi: 186, btch: 31 usd: 49 Cold: hi: 62, btch: 15 usd: 22 Jan 27 09:05:17 maya CPU 3: Hot: hi: 186, btch: 31 usd: 123 Cold: hi: 62, btch: 15 usd: 23 Jan 27 09:05:17 maya Active:165018 inactive:823505 dirty:0 writeback:0 unstable:0 Jan 27 09:05:17 maya free:5407 slab:4987 mapped:57 pagetables:5131 bounce:0 Jan 27 09:05:17 maya Node 0 DMA free:10544kB min:16kB low:20kB high:24kB active:0kB inactive:0kB present:10056kB pages_scanned:0 all_ unreclaimable? yes Jan 27 09:05:17 maya lowmem_reserve[]: 0 3255 4013 4013 Jan 27 09:05:17 maya Node 0 DMA32 free:9584kB min:6564kB low:8204kB high:9844kB active:322112kB inactive:2957716kB present:3333792kB pages_scanned:6628506 all_unreclaimable? yes Jan 27 09:05:17 maya lowmem_reserve[]: 0 0 757 757 Jan 27 09:05:17 maya Node 0 Normal free:1500kB min:1528kB low:1908kB high:2292kB active:341700kB inactive:332720kB present:775680kB p ages_scanned:1113964 all_unreclaimable? yes Jan 27 09:05:17 maya lowmem_reserve[]: 0 0 0 0 Jan 27 09:05:17 maya Node 0 DMA: 6*4kB 5*8kB 3*16kB 6*32kB 6*64kB 3*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 2*4096kB = 10544kB Jan 27 09:05:17 maya Node 0 DMA32: 358*4kB 3*8kB 0*16kB 0*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 1*4096kB = 9584kB Jan 27 09:05:17 maya Node 0 Normal: 57*4kB 1*8kB 1*16kB 1*32kB 1*64kB 1*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1500kB Jan 27 09:05:17 maya Swap cache: add 307242, delete 307241, find 3804/7830, race 0+4 Jan 27 09:05:17 maya Free swap = 0kB Jan 27 09:05:17 maya Total swap = 1076344kB Jan 27 09:05:17 maya Free swap: 0kB Jan 27 09:05:17 maya 1245184 pages of RAM Jan 27 09:05:17 maya 231857 reserved pages Jan 27 09:05:17 maya 21819 pages shared Jan 27 09:05:17 maya 1 pages swap cached Jan 27 09:05:17 maya Out of memory: kill process 25352 (apache2) score 31635 or a child Jan 27 09:05:17 maya Killed process 25352 (apache2) Jan 27 09:05:17 maya postmaster invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0 Syslog-ng is restarted everyday by crontab : 0 0,12 * * * /etc/init.d/syslog-ng restart If we restart manually we don't have problems. Reproducible: Sometimes Steps to Reproduce: 1.I'm not able to reproduce this problems. 2. 3. I resize the swap up to 6Gb (1Gb before), i compil and install a new kernel 2.6.24-gentoo-r to 2.6.27-gentoo-r8. It does the same problems so i re-install app-admin/syslog-ng-2.0.9 and block it in package.mask.
attach your config please.
Created attachment 180670 [details] Syslog-ng config I have a similar problem with an another x86_64 gentoo. No process are alive after a restart in crontab. It works fine with all x86 and the same configuration.
Same thing on both amd64 and x86.
Created attachment 180708 [details] syslog-ng.conf on amd64
From the changelog of syslog-ng 2.1.4 released 17-Mar-2009: Bugfixes: * Fixed a possible DoS condition triggered by a destination port unreaachable ICMP packet received from a UDP destination. syslog-ng started eating all available memory and CPU until it crashed if this happened. I've seen this once also. Hopefully a version bump will fix it.
yes, should be fixed in 2.1.4. Reopen if it's still a problem.
