Ticket #73 (new bug)
Seal some memory leakages
| Reported by: | tobixen | Owned by: | hannu, steinwinde |
|---|---|---|---|
| Priority: | major | Milestone: | unassigned |
| Component: | ServerSetup | Keywords: | memory leak load |
| Cc: |
Description
We need to figure out why apache sometimes run away with all the memory.
I'll set this as ServerSetup as for now, but it's probably a bug in some PHP script
Change History
comment:2 Changed 4 years ago by steinwinde
- Keywords memory leak load added
- Owner changed from hannu to steinwinde
- Status changed from new to assigned
comment:3 Changed 4 years ago by steinwinde
- Owner changed from steinwinde to hannu
- Status changed from assigned to new
comment:5 Changed 4 years ago by tobixen
right, I think I've seen such configuration at least for fcgi ... dunno about php.
That would anyway be a work-around, not a proper fix. In the long run, we should stop the memory leakages from happening in the first place.
As a part of #70, I fixed daily restarts of apache.
comment:6 Changed 4 years ago by feuerdaemon
- follow_up set to none
- show_on_bw set to 0
- freq_reported set to 1
- Milestone set to BigPicture
comment:7 Changed 4 years ago by philipp
- Milestone changed from BigPicture to unassigned
Milestone BigPicture? deleted
Note: See
TracTickets for help on using
tickets.



Maybe we could try configuring apache so that it kills serving apache process after X amount of requests. Maybe it would then free the memory?