--- Comment #23 from ---
That more conservative patch doesn't seem to have helped either.

[Wed Jan 31 08:44:12.677361 2018] [proxy:debug] [pid 58615:tid 140446564935424]
proxy_util.c(1225): AH02337: copying shm[2] (0x7fbc398b07d8) for
[Wed Jan 31 08:44:12.677429 2018] [slotmem_shm:debug] [pid 58615:tid
140446564935424] mod_slotmem_shm.c(331): AH02602: create didn't find
/var/run/http/apache24/tmp/slotmem-shm-p5dfa5b80_balancer3_0.shm in global list
[Wed Jan 31 08:44:12.677469 2018] [slotmem_shm:debug] [pid 58615:tid
140446564935424] mod_slotmem_shm.c(341): AH02300: create
/var/run/http/apache24/tmp/slotmem-shm-p5dfa5b80_balancer3_0.shm: 1176/2
[Wed Jan 31 08:44:12.677585 2018] [slotmem_shm:error] [pid 58615:tid
140446564935424] (17)File exists: AH02611: create:
[Wed Jan 31 08:44:12.677677 2018] [:emerg] [pid 58615:tid 140446564935424]
AH00020: Configuration Failed, exiting

We keep bumping into previously created keys. I wonder if our balancer naming
isn't distinctive enough, literally each vhost gets balancer1, balancer2,
balancer3. So those names appear hundreds or thousands of times per
configuration, but always inside a virtualhost container.

Any ideas?

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to