Apache 2 produces an OOM after 4 hours using

Bug #230878 reported by Léobaillard
6
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Invalid
Low
Chuck Short

Bug Description

Binary package hint: apache2

After upgrading my web server from Ubuntu Gutsy to Hardy, I couldn't get Apache 2 working correctly. I thought at first, that I was experiencing this bug : #224945 . But this one deals with memory leaks when mod_ssl is enabled. So, because I'm not using it on apache, I've decided to unload it. But it hasn't changed a thing. I've also updated my apache's version to get the latest, with the bug fixed. Nothing has changed so far...

My problem is, after approximately four hours of execution, apache is overloading and taking all the memory and the swap so that my system produces an Out of memory error which wants to kill apache2 but doesn't succeed, which leads to a system crash. The weird thing is that the OOM error sometimes tries to kill other processes...

Here's a dump from /var/log/syslog when an OOM happens :

May 3 19:12:15 yoda kernel: [ 8267.512850] Out of memory: kill process 7986 (apache2) score 19064 or a child
May 3 19:12:15 yoda kernel: [ 8267.513008] Killed process 7986 (apache2)
May 3 19:12:15 yoda kernel: [ 8271.323940] apache2 invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
May 3 19:12:15 yoda kernel: [ 8271.323974] Pid: 8012, comm: apache2 Not tainted 2.6.24-16-server #1
May 3 19:12:15 yoda kernel: [ 8271.324051] [oom_kill_process+0x10a/0x120] oom_kill_process+0x10a/0x120
May 3 19:12:15 yoda kernel: [ 8271.324136] [out_of_memory+0x167/0x1a0] out_of_memory+0x167/0x1a0
May 3 19:12:15 yoda kernel: [ 8271.324186] [agpgart:__alloc_pages+0x34c/0x380] __alloc_pages+0x34c/0x380
May 3 19:12:15 yoda kernel: [ 8271.324248] [__do_page_cache_readahead+0x11d/0x240] __do_page_cache_readahead+0x11d/0x240
May 3 19:12:15 yoda kernel: [ 8271.324314] [do_page_cache_readahead+0x4c/0x70] do_page_cache_readahead+0x4c/0x70
May 3 19:12:15 yoda kernel: [ 8271.324344] [filemap_fault+0x2f2/0x420] filemap_fault+0x2f2/0x420
May 3 19:12:15 yoda kernel: [ 8271.324408] [__do_fault+0x83/0x4c0] __do_fault+0x83/0x4c0
May 3 19:12:15 yoda kernel: [ 8271.324437] [libata:kunmap_atomic+0x2d/0x2e90] kunmap_atomic+0x2d/0x80
May 3 19:12:15 yoda kernel: [ 8271.324480] [do_wp_page+0x460/0x650] do_wp_page+0x460/0x650
May 3 19:12:15 yoda kernel: [ 8271.324510] [deadline_move_request+0x59/0x70] deadline_move_request+0x59/0x70
May 3 19:12:15 yoda kernel: [ 8271.324527] [elv_dispatch_add_tail+0x1c/0x60] elv_dispatch_add_tail+0x1c/0x60
May 3 19:12:15 yoda kernel: [ 8271.324590] [handle_mm_fault+0x21b/0xb80] handle_mm_fault+0x21b/0xb80
May 3 19:12:15 yoda kernel: [ 8271.324697] [sched_clock+0x13/0x30] sched_clock+0x13/0x30
May 3 19:12:15 yoda kernel: [ 8271.324771] [do_page_fault+0x143/0x900] do_page_fault+0x143/0x900
May 3 19:12:15 yoda kernel: [ 8271.324797] [__do_softirq+0x82/0x110] __do_softirq+0x82/0x110
May 3 19:12:15 yoda kernel: [ 8271.324864] [do_page_fault+0x0/0x900] do_page_fault+0x0/0x900
May 3 19:12:15 yoda kernel: [ 8271.324881] [error_code+0x72/0x78] error_code+0x72/0x78
May 3 19:12:15 yoda kernel: [ 8271.324920] [unix_create1+0x50/0x120] unix_create1+0x50/0x120
May 3 19:12:15 yoda kernel: [ 8271.324971] =======================
May 3 19:12:15 yoda kernel: [ 8271.324979] Mem-info:
May 3 19:12:15 yoda kernel: [ 8271.324986] DMA per-cpu:
May 3 19:12:15 yoda kernel: [ 8271.324996] CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
May 3 19:12:15 yoda kernel: [ 8271.325008] Normal per-cpu:
May 3 19:12:15 yoda kernel: [ 8271.325018] CPU 0: Hot: hi: 186, btch: 31 usd: 143 Cold: hi: 62, btch: 15 usd: 52
May 3 19:12:15 yoda kernel: [ 8271.325035] Active:86718 inactive:10 dirty:0 writeback:0 unstable:0
May 3 19:12:15 yoda kernel: [ 8271.325042] free:981 slab:3338 mapped:1 pagetables:1909 bounce:0
May 3 19:12:15 yoda kernel: [ 8271.325058] DMA free:1556kB min:104kB low:128kB high:156kB active:10512kB inactive:0kB present:16256kB pages_scanned:52482 all_unreclaimable? yes
May 3 19:12:15 yoda kernel: [ 8271.325071] lowmem_reserve[]: 0 364 364 364
May 3 19:12:15 yoda kernel: [ 8271.325090] Normal free:2368kB min:2384kB low:2980kB high:3576kB active:336360kB inactive:40kB present:372812kB pages_scanned:540939 all_unreclaimable? yes
May 3 19:12:15 yoda kernel: [ 8271.325104] lowmem_reserve[]: 0 0 0 0
May 3 19:12:15 yoda kernel: [ 8271.325116] DMA: 1*4kB 0*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 1556kB
May 3 19:12:15 yoda kernel: [ 8271.325148] Normal: 31*4kB 0*8kB 0*16kB 0*32kB 1*64kB 1*128kB 2*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2364kB
May 3 19:12:15 yoda kernel: [ 8271.325184] Swap cache: add 0, delete 0, find 0/0, race 0+0
May 3 19:12:15 yoda kernel: [ 8271.325192] Free swap = 0kB
May 3 19:12:15 yoda kernel: [ 8271.325200] Total swap = 0kB
May 3 19:12:15 yoda kernel: [ 8271.325206] Free swap: 0kB
May 3 19:12:15 yoda kernel: [ 8271.352327] 98032 pages of RAM
May 3 19:12:15 yoda kernel: [ 8271.352343] 0 pages of HIGHMEM
May 3 19:12:15 yoda kernel: [ 8271.352349] 1953 reserved pages
May 3 19:12:15 yoda kernel: [ 8271.352355] 349943 pages shared
May 3 19:12:15 yoda kernel: [ 8271.352361] 0 pages swap cached
May 3 19:12:15 yoda kernel: [ 8271.352367] 0 pages dirty
May 3 19:12:15 yoda kernel: [ 8271.352373] 0 pages writeback
May 3 19:12:15 yoda kernel: [ 8271.352378] 1 pages mapped
May 3 19:12:15 yoda kernel: [ 8271.352384] 3338 pages slab
May 3 19:12:15 yoda kernel: [ 8271.352390] 1909 pages pagetables

I can't tell you how to reproduce this bug because I don't know it yet, but I'm pretty sure it's an apache problem (or related with apache) because when it's not launched, this problem doesn't happen.

I'm using Ubuntu Hardy Heron (8.04 LTS) Server with Apache 2.2.8-1 (it's the same with 2.2.8-4 by the way), libapache2-mod-php5 (5.2.4-5), MySQL (5.0.51a).

Thank you for helping

PS : Sorry for my English, I'm French...

Revision history for this message
Léobaillard (leobaillard) wrote :

I've also added some restrictions for apache which seems not to change the problem :

<IfModule prefork.c>
        MaxClients 40
        MaxSpareServers 8
        MaxRequestsPerChild 2000
</IfModule>

RLimitNPROC 10
RLimitMEM 67108864
RLimitCPU 30

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Hi Léobaillard-

I at first marked this a duplicate of Bug #224945, but I see now that you're not dealing with SSL. In which case I'm interested in reproducing this bug (and I un-marked it duplicate).

Would it be possible for you to determine an Apache bench (ab) command that you can run to reproduce this problem reliably, and quicker than within 4 hours?

Thanks,
:-Dustin

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Marking incomplete until we have full instructions for reproducing this bug (ideally using ab).

Please change back to "new" once you've provided these.

Thanks!
:-Dustin

Changed in apache2:
assignee: nobody → kirkland
status: New → Incomplete
Revision history for this message
Léobaillard (leobaillard) wrote :

Ok, I'll do this as soon as I go back home and post you the results.

Revision history for this message
Stefan Fritsch (sf-sfritsch) wrote :

It would also be interesting to know what apache modules you have enabled and how the output of top looks just before the OOM situation (i.e. are there many large apache2 processes or only a few very large ones?).

You could also try tweaking "memory_limit" in your php.ini.

Revision history for this message
Léobaillard (leobaillard) wrote :

I ran some ab tests (it's my first time so maybe the settings were too low, you'll tell me) but it didn't produce an OOM. I couldn't get a fresh htop when the server was loading but I've taken a screenshot just before the SSH has frozen.

Here are the ab results

$ ab -c 50 -n 50000 http://<server>/

Benchmarking <server> (be patient)
Completed 5000 requests
Completed 10000 requests
Completed 15000 requests
Completed 20000 requests
Completed 25000 requests
Completed 30000 requests
Completed 35000 requests
Completed 40000 requests
Completed 45000 requests
Finished 50000 requests

Server Software: Apache
Server Hostname: <server>
Server Port: 80

Document Path: /
Document Length: 224 bytes

Concurrency Level: 50
Time taken for tests: 172.678631 seconds
Complete requests: 50000
Failed requests: 0
Write errors: 0
Non-2xx responses: 50005
Total transferred: 21802180 bytes
HTML transferred: 11201120 bytes
Requests per second: 289.56 [#/sec] (mean)
Time per request: 172.679 [ms] (mean)
Time per request: 3.454 [ms] (mean, across all concurrent requests)
Transfer rate: 123.30 [Kbytes/sec] received

Connection Times (ms)
              min mean[+/-sd] median max
Connect: 1 58 414.4 17 21013
Processing: 2 82 1320.6 18 90756
Waiting: 1 55 1264.2 17 90741
Total: 5 140 1397.8 36 90774

Percentage of the requests served within a certain time (ms)
  50% 36
  66% 36
  75% 38
  80% 39
  90% 40
  95% 44
  98% 1887
  99% 3036
 100% 90774 (longest request)

$ ab -c 500 -n 50000 http://<server>/

 Benchmarking <server> (be patient)
Completed 5000 requests
Completed 10000 requests
Completed 15000 requests
Completed 20000 requests
Completed 25000 requests
Completed 30000 requests
Completed 35000 requests
Completed 40000 requests
Completed 45000 requests
Finished 50000 requests

Server Software: Apache
Server Hostname: <server>
Server Port: 80

Document Path: /
Document Length: 224 bytes

Concurrency Level: 500
Time taken for tests: 173.445502 seconds
Complete requests: 50000
Failed requests: 0
Write errors: 0
Non-2xx responses: 50006
Total transferred: 21802616 bytes
HTML transferred: 11201344 bytes
Requests per second: 288.27 [#/sec] (mean)
Time per request: 1734.455 [ms] (mean)
Time per request: 3.469 [ms] (mean, across all concurrent requests)
Transfer rate: 122.75 [Kbytes/sec] received

Connection Times (ms)
              min mean[+/-sd] median max
Connect: 1 82 920.7 18 93023
Processing: 2 142 2040.2 20 146381
Waiting: 1 92 1933.3 20 146363
Total: 3 224 2265.0 39 146408

Percentage of the requests served within a certain time (ms)
  50% 39
  66% 45
  75% 58
  80% 63
  90% 77
  95% 85
  98% 3036
  99% 4119
 100% 146408 (longest request)

Changed in apache2:
status: Incomplete → New
Revision history for this message
Léobaillard (leobaillard) wrote :

I've just seen that the responses werent 2xx, I got a 404, I've fixed this and I'll run more ab tests with higher values.

Revision history for this message
Léobaillard (leobaillard) wrote :
Download full text (5.9 KiB)

I've launched the same ab test but the machine has frozen before I could see the results, nevertheless, when it was frozen, it didn't produce an OOM, the OOM has come later but not within the 4 hours limit.

Here is the initial OOM of apache2 and it seems to have taken down other processes before locking completely the machine :

May 20 01:30:00 yoda kernel: [347664.832222] apache2 invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=-17
May 20 01:30:00 yoda kernel: [347664.832229] Pid: 6899, comm: apache2 Not tainted 2.6.24-16-server #1
May 20 01:30:00 yoda kernel: [347664.832246] [oom_kill_process+0x10a/0x120] oom_kill_process+0x10a/0x120
May 20 01:30:00 yoda kernel: [347664.832274] [out_of_memory+0x167/0x1a0] out_of_memory+0x167/0x1a0
May 20 01:30:01 yoda kernel: [347664.832299] [agpgart:__alloc_pages+0x34c/0x380] __alloc_pages+0x34c/0x380
May 20 01:30:03 yoda kernel: [347664.832334] [__do_page_cache_readahead+0x11d/0x240] __do_page_cache_readahead+0x11d/0x240
May 20 01:30:03 yoda kernel: [347664.832337] [sync_page+0x0/0x40] sync_page+0x0/0x40
May 20 01:30:03 yoda kernel: [347664.832368] [do_page_cache_readahead+0x4c/0x70] do_page_cache_readahead+0x4c/0x70
May 20 01:30:03 yoda kernel: [347664.832380] [filemap_fault+0x2f2/0x420] filemap_fault+0x2f2/0x420
May 20 01:30:05 yoda kernel: [347664.832387] [kmap_atomic_prot+0xfc/0x130] kmap_atomic_prot+0xfc/0x130
May 20 01:30:06 yoda kernel: [347664.832417] [__do_fault+0x83/0x4c0] __do_fault+0x83/0x4c0
May 20 01:30:06 yoda kernel: [347664.832445] [kmap_atomic_prot+0xfc/0x130] kmap_atomic_prot+0xfc/0x130
May 20 01:30:06 yoda kernel: [347664.832474] [handle_mm_fault+0x21b/0xb80] handle_mm_fault+0x21b/0xb80
May 20 01:30:06 yoda kernel: [347664.832543] [set_process_cpu_timer+0xa6/0xc0] set_process_cpu_timer+0xa6/0xc0
May 20 01:30:31 yoda kernel: [347664.832574] [do_page_fault+0x143/0x900] do_page_fault+0x143/0x900
May 20 01:30:32 yoda kernel: [347664.832580] [do_sigaction+0x65/0x170] do_sigaction+0x65/0x170
May 20 01:30:33 yoda kernel: [347664.832598] [recalc_sigpending+0xb/0x40] recalc_sigpending+0xb/0x40
May 20 01:30:33 yoda kernel: [347664.832609] [sys_rt_sigprocmask+0xed/0x110] sys_rt_sigprocmask+0xed/0x110
May 20 01:30:33 yoda kernel: [347664.832620] [do_page_fault+0x0/0x900] do_page_fault+0x0/0x900
May 20 01:30:33 yoda kernel: [347664.832624] [error_code+0x72/0x78] error_code+0x72/0x78
May 20 01:30:33 yoda kernel: [347664.832662] =======================
May 20 01:30:33 yoda kernel: [347664.832663] Mem-info:
May 20 01:30:33 yoda kernel: [347664.832665] DMA per-cpu:
May 20 01:30:33 yoda kernel: [347664.832667] CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
May 20 01:30:33 yoda kernel: [347664.832669] Normal per-cpu:
May 20 01:30:33 yoda kernel: [347664.832670] CPU 0: Hot: hi: 186, btch: 31 usd: 177 Cold: hi: 62, btch: 15 usd: 58
May 20 01:30:33 yoda kernel: [347664.832672] HighMem per-cpu:
May 20 01:30:33 yoda kernel: [347664.832674] CPU 0: Hot: hi: 42, btch: 7 usd: 3 Cold: hi: 14, btch: 3 usd: 2
May 20 01:30:33 yoda kernel: [347664.832677] Active:195460 inactive:49533 dirty:0 writeback:0 unstable:0
May 20 01:30:...

Read more...

Revision history for this message
Chuck Short (zulcss) wrote :

Léobaillard,

Can you test the apache that is in my ppa archive?

http://launchpad.net/~zulcss/+archive

It should be available shortly.

Thanks
chuck

Revision history for this message
Léobaillard (leobaillard) wrote :

Ok, no problem, but what are the differences with my version ? Were do you think the problem is ? I'll try this this afternoon when I come back home.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Chuck has confirmed this, and triaged it to Apache2. He currently has a fix in progress in his PPA.

:-Dustin

Changed in apache2:
status: New → In Progress
assignee: kirkland → zulcss
Revision history for this message
Léobaillard (leobaillard) wrote :

Great ! I install it right now !

Revision history for this message
Léobaillard (leobaillard) wrote :

Unfortunately, it didn't changed anything. The OOM has occured about 20 minutes ago... But the first OOM I saw on the server's screen was triggered by mysqld, usually it's apache and then other processes but this time, it was mysqld... I don't know why but I'm nearly sure that apache is the bad one because, as I already said it in my first message, when apache isn't started, the OOM doesn't occur.

Do you have an idea ?

Revision history for this message
Chuck Short (zulcss) wrote :

Well if mysql is causing you an OOM error then have you tried considering running a memory test on your machine then?

chuck

Revision history for this message
Léobaillard (leobaillard) wrote :

Memory test ? If you mean by this checking th integrity of the physical memory, I don't think this is where the problem is because I tryied to change my machine keeping the hard drives and the data and it didn't changed anything... :( So maybe it's related with apache but not apache itself ? Maybe it's my configuration ? Maybe it's php ? I don't know where to start, I don't have any clue appart from the fact that it's happening only when apache is running... :( I can run a memory test, just to see, but I don't think it'll be relevant. Other ideas / tracks ? Again, thank you so much for the interest you give to my problem, I'm very greatful.

Revision history for this message
Léobaillard (leobaillard) wrote :

Maybe I can trace Apache to see where it's going wrong ? What do you think ?

Revision history for this message
Chuck Short (zulcss) wrote :

Can you please add your apache configuration files, your php.ini files and anything relevant in your apache2 error logs?

Thanks
chuck

Changed in apache2:
status: In Progress → Incomplete
Revision history for this message
Léobaillard (leobaillard) wrote :

Hi,

Here's my apache2.conf. I didn't notice anything in the apache error logs...

Revision history for this message
Léobaillard (leobaillard) wrote :

And here's my php.ini file.

Changed in apache2:
status: Incomplete → New
Revision history for this message
Léobaillard (leobaillard) wrote :

I also have a bunch of these :

127.0.0.1 - - [24/May/2008:09:05:59 +0200] "OPTIONS * HTTP/1.0" 200 - "-" "Apache (internal dummy connection)"

in my access.log.

Revision history for this message
Chuck Short (zulcss) wrote :

What kernel are you using? This seems to be more like a hardware issue than anything else.

Thanks
chuck

Revision history for this message
Léobaillard (leobaillard) wrote :

My kernel is : 2.6.24-16-server. Do you think that a kernel update would do the trick ?

Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

I really dont think its a kernel problem either basically you have a process on your machine that is chewing up all of your memory and you really have to nail it down to see why that is. The reason why you are getting OOM because its not that smart and it killed the first. You might want to consider try a different version of apache (other than mpm-worker) as well. From what you have given us so far I cant really tell which is eating up all of your memory.

Regards
chuck

Changed in apache2:
status: New → Triaged
Chuck Short (zulcss)
Changed in apache2 (Ubuntu):
importance: Undecided → Low
Revision history for this message
Dave Walker (davewalker) wrote :

Marking incomplete as waiting on reporter to provide some further information to help triage.

Changed in apache2 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Dave Walker (davewalker) wrote :

Marking Invalid as a reasonable assumption that it might have been hardware memory issues. If this is not the case, please provide further information as requested.

Thanks again!

Changed in apache2 (Ubuntu):
status: Incomplete → Opinion
status: Opinion → Invalid
Revision history for this message
GrayMatter (cgray) wrote :
Download full text (7.4 KiB)

We are experiencing the same issue. Fresh install of Ubuntu 10.10LTS with default apache2, mysql, php. I can say for certain that it's not a hardware issue. This is a virtual server running on an ESX host. Let me know if there are any other details I can pull to help with this issue. This is a production server and it crashes with this OOM about once a week.

Apache2 Loaded Modules:
core mod_log_config mod_logio prefork http_core mod_so mod_alias mod_auth_basic mod_authn_file mod_authz_default mod_authz_groupfile mod_authz_host mod_authz_user mod_autoindex mod_cgi mod_deflate mod_dir mod_env mod_mime mod_negotiation mod_php5 mod_reqtimeout mod_rewrite mod_setenvif mod_status

PHP Version: 5.3.3-1ubuntu9.5

The default also came with Suhosin Patch 0.9.9.1.

root@public-lamp:/var/log# mysql --version
mysql Ver 14.14 Distrib 5.1.49, for debian-linux-gnu (x86_64) using readline 6.1

2.6.35-30-server #59-Ubuntu SMP 64-bit

Sep 21 12:31:32 public-lamp kernel: [1707807.719708] apache2 invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
Sep 21 12:31:32 public-lamp kernel: [1707807.797392] apache2 cpuset=/ mems_allowed=0
Sep 21 12:31:32 public-lamp kernel: [1707807.824987] Pid: 16345, comm: apache2 Not tainted 2.6.35-30-server #56-Ubuntu
Sep 21 12:31:32 public-lamp kernel: [1707807.824991] Call Trace:
Sep 21 12:31:32 public-lamp kernel: [1707807.877827] [<ffffffff81105331>] dump_header+0x81/0xc0
Sep 21 12:31:32 public-lamp kernel: [1707807.995049] [<ffffffff811053f1>] oom_kill_process+0x81/0x180
Sep 21 12:31:32 public-lamp kernel: [1707807.995053] [<ffffffff81105928>] __out_of_memory+0x58/0xd0
Sep 21 12:31:32 public-lamp kernel: [1707807.995057] [<ffffffff81105a26>] out_of_memory+0x86/0x1c0
Sep 21 12:31:32 public-lamp kernel: [1707807.995061] [<ffffffff8110948e>] __alloc_pages_slowpath+0x58e/0x5a0
Sep 21 12:31:32 public-lamp kernel: [1707807.995065] [<ffffffff8110960c>] __alloc_pages_nodemask+0x16c/0x1d0
Sep 21 12:31:32 public-lamp kernel: [1707807.995075] [<ffffffff8113b9ca>] alloc_pages_current+0x9a/0x100
Sep 21 12:31:32 public-lamp kernel: [1707807.995079] [<ffffffff81102a37>] __page_cache_alloc+0x87/0x90
Sep 21 12:31:32 public-lamp kernel: [1707807.995090] [<ffffffff8110cc09>] __do_page_cache_readahead+0xc9/0x210
Sep 21 12:31:32 public-lamp kernel: [1707807.995095] [<ffffffff8110cd71>] ra_submit+0x21/0x30
Sep 21 12:31:32 public-lamp kernel: [1707807.995098] [<ffffffff8110d125>] ondemand_readahead+0x115/0x240
Sep 21 12:31:32 public-lamp kernel: [1707808.004712] [<ffffffff81049219>] ? __wake_up_common+0x59/0x90
Sep 21 12:31:32 public-lamp kernel: [1707808.005747] [<ffffffff8110d351>] page_cache_sync_readahead+0x31/0x50
Sep 21 12:31:32 public-lamp kernel: [1707808.005751] [<ffffffff81104259>] filemap_fault+0x419/0x450
Sep 21 12:31:32 public-lamp kernel: [1707808.005756] [<ffffffff8111f304>] __do_fault+0x54/0x560
Sep 21 12:31:32 public-lamp kernel: [1707808.005760] [<ffffffff81122b69>] handle_mm_fault+0x1b9/0x440
Sep 21 12:31:32 public-lamp kernel: [1707808.012723] [<ffffffff81170d20>] ? mntput_no_expire+0x30/0x110
Sep 21 12:31:32 public-lamp kernel: [1707808.022743] [<ffffffff815a6a75>] do_page_fault+0x125/0x350
Sep 21 ...

Read more...

Changed in apache2 (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

I notice that both of the reporters are using libapache-mod-php5. It might be that this is a PHP memory leak issue and has nothing to do with apache. OOM killed processes are often not the actual problem.

I don't see anything we can actually act on to reproduce in this bug report. Unless a user is willing to share their PHP configs and possibly code that reproduces the issue, I don't see how we can do anything.

Because of that, I'm going to go ahead and close this issue as Invalid. If anyone has information suggesting that this is still a bug we can respond to and debug in Ubuntu, please feel free to re-open it or to open a new bug from a recent release of Ubuntu.

Changed in apache2 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.