Apache Reload Crash with slotmem-shm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| apache2 (Debian) |
New
|
Unknown
|
||
| apache2 (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 18.04 LTS
Release: 18.04
*** 2.4.29-1ubuntu4.1 500
500 http://
100 /var/lib/
When i reload apache
[Tue Jul 24 16:17:26.783249 2018] [slotmem_shm:error] [pid 23188:tid 139792764550080] (28)No space left on device: AH02611: create: apr_shm_
[Tue Jul 24 16:17:26.783287 2018] [proxy_
[Tue Jul 24 16:17:26.783293 2018] [:emerg] [pid 23188:tid 139792764550080] AH00020: Configuration Failed, exiting
Apache Revision 1834887
mod_slotmem_shm: use a generation number for SHM filename on all platforms.
Successive generations can't share the same SHMs because restarts may modify
them under the terminating children, while SHMs are not extensible when all
slots are in use.
description: | updated |
tags: | added: bionic |
Andreas Hasenack (ahasenack) wrote : | #1 |
Andreas Hasenack (ahasenack) wrote : | #2 |
Would you be able to share the config for a reproducer of this bug? I suppose you have a lot of proxy balancers, and/or vhosts?
R (gregory.r) wrote : | #3 |
Sorry, it's production so it's not be possible.
Yes, 31 proxy balancer and 200 vhosts
We have to do a restart for each modification, and modify the logrotate (replace the reload by restart) to avoid the crash each morning.
Andreas Hasenack (ahasenack) wrote : | #4 |
It could be https:/
Changed in apache2 (Debian): | |
status: | Unknown → New |
R (gregory.r) wrote : | #5 |
I compiled the version with
apache2_
https:/
And I put mod_proxy_
But it doesn't work,i have error messages when i reload:
Directory /var/run/apache2 is empty
Start :
[Thu Aug 07 09:40:53.271008 2018] [ slotmem_shm:error] [pid 25187: tid 140664450165696] AH02599: exiting shared memory for /var/run/
...
but Directory /var/run/apache2/ is no empty
Reload:
[Thu Aug 07 09:46:22.930184 2018] [ proxy_balancer:
...
[Thu Aug 07 09:46:23.067853 2018] [:emerg] [pid 25187: tid 140664450165696] AH00020: Configuration Failed, exiting
Thank
Possibly same bug reported in Debian: https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 896090