[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #36 from m...@blackmans.org --- (In reply to Yann Ylavic from comment #34) > Created attachment 35723 [details] > Reuse SHMs names on restart or stop/start (2.4.x) > > This is the full patch proposed to be backported to 2.4.next. >

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-02-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 Graham Leggett changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-02-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 Yann Ylavic changed: What|Removed |Added Attachment #35702|0 |1 is

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #33 from Yann Ylavic --- Mark, followed up on dev@ since debugging in not really suitable in bugzilla. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #32 from m...@blackmans.org --- so sig_coredump is being triggered by an unknown signal, multiple times a day. It's not a segfault, nothing in /var/log/messages. That results in a bunch of undeleted shared memory segments and

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #31 from m...@blackmans.org --- (In reply to Yann Ylavic from comment #27) > (In reply to mark from comment #7) > > > > " AH00060: seg fault or similar nasty error detected in the parent process" > > but I cannot tell what it's

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #30 from m...@blackmans.org --- (In reply to Yann Ylavic from comment #26) > (In reply to mark from comment #25) > > > > [Wed Jan 31 12:26:41.463136 2018] [slotmem_shm:debug] [pid 1322:tid > > 139715805775616]

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #29 from Yann Ylavic --- > (In reply to Yann Ylavic from comment #24) > > Created attachment 35710 [details] > > Unique balancer id per vhost > > Committed to trunk in r1822800. Reverted, all was there

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 Yann Ylavic changed: What|Removed |Added Attachment #35710|0 |1 is

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 Yann Ylavic changed: What|Removed |Added Keywords||FixedInTrunk ---

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #27 from Yann Ylavic --- (In reply to mark from comment #7) > > " AH00060: seg fault or similar nasty error detected in the parent process" > but I cannot tell what it's referring to. The parent process

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #26 from Yann Ylavic --- (In reply to mark from comment #25) > > [Wed Jan 31 12:26:41.463136 2018] [slotmem_shm:debug] [pid 1322:tid > 139715805775616] mod_slotmem_shm.c(463): AH02301: attach looking for >

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #25 from m...@blackmans.org --- Perhaps, we're seeing the error even in the balancer SHMs as well as the worker SHMs and the balancer SHM already uses conf->id as a distinguisher.

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #24 from Yann Ylavic --- Created attachment 35710 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35710=edit Unique balancer id per vhost It seems indeed that if balancer:// are not unique the slotmem

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #23 from m...@blackmans.org --- 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]

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #22 from m...@blackmans.org --- Anyway, in the absence of other ideas, we're going revert to the more conservative patch, even at the cost of cross-generation persistence, at

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #21 from m...@blackmans.org --- In the patched file, line 396 was updated with "gpool" I believe, should 395 have been updated as well? 393 { 394 if (fbased) { 395 apr_shm_remove(fname, pool);

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #20 from m...@blackmans.org --- Sorry, I am wrong, we are still seeing the "file exists" error in our logs. [Tue Jan 30 09:07:05.575349 2018] [slotmem_shm:debug] [pid 3716:tid 139969799624448] mod_slotmem_shm.c(380): AH02602:

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #19 from m...@blackmans.org --- We were able to rebuild and deploy Yann's patch for the pre-production environments and we're not yet seeing slotmem_shm "File Exists" errors. However, we are seeing a lot of orphaned shared segments

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #18 from m...@blackmans.org --- Thanks for the perspective. We were seeing Apache instances fail and not restart due to the orphaned segments, requiring manual intervention to resolve, hence our urgency. However, I see your point

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #17 from Yann Ylavic --- In any case, if you go with the "Windows" approach for your production, we are still interested in your testing of attachment 35702 for the future ;) -- You are receiving this mail

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #16 from Yann Ylavic --- (In reply to mark from comment #15) > Is this later patch either more robust or more > comprehensive than Jim's? If you're making a strong recommendation, we will > see about pushing

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #15 from m...@blackmans.org --- We were a bit keen for a fix for this morning (29 Jan), so we went with Jim's patch in trunk as it looked very conservative (extending tested behaviours to Unix from Windows). I didn't see your patch

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 Yann Ylavic changed: What|Removed |Added Attachment #35698|0 |1 is

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #13 from m...@blackmans.org --- Yes, I can test fixes. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail:

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #12 from Jim Jagielski --- Upon review, it appears that in slotmem_filenames() there is code that will automagically add generational data to the SHM filename... this is done by default for Win and OS/2. Are you

***UNCHECKED*** [Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #11 from Jim Jagielski --- Yeah, it looks like adding in the generation to conf->id will create a unique name. But I need to see how it effects persistence -- You are receiving this mail because: You are the

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #10 from m...@blackmans.org --- baked here: https://github.com/apache/httpd/blob/2.4.29/modules/proxy/mod_proxy_balancer.c#L787 id = apr_psprintf(pconf, "%s.%s.%d.%s.%s.%u.%s", (s->server_scheme ?

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 cbarb...@okta.com changed: What|Removed |Added CC||cbarb...@okta.com -- You are

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #9 from Jim Jagielski --- ... or possibly re-used?? I'll need to look. It's been awhile since I've reviewed that chunk of code. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #8 from Eric Covener --- (In reply to mark from comment #7) > give that man a teddy bear. pid 13310 was born at 03:40:12 with a SIGHUP at > 03:47:58 and then permanently exiting at 03:48:11. > > [Thu Jan 25

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #7 from m...@blackmans.org --- give that man a teddy bear. pid 13310 was born at 03:40:12 with a SIGHUP at 03:47:58 and then permanently exiting at 03:48:11. [Thu Jan 25 03:40:22.300797 2018] [mpm_event:notice] [pid 13310:tid

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #6 from m...@blackmans.org --- Probably, we do a lot of active restarts both to bring in managed changes to the configuration (but only hourly) and reactive restarts when apache stops responding. I will examine and get back to you.

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #5 from Ruediger Pluem --- (In reply to mark from comment #0) > With a large number of vhosts ( > 1000 ) and proxy balancer configurations ( > > 1000), we are seeing Apache exit at start up time with a

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #4 from m...@blackmans.org --- Thanks for looking, the apr_shm_remove does an apr_file_remove as the final step, so I would be surprised if another one helps -- You are receiving this mail because: You are the assignee for the

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #3 from Yann Ylavic --- Created attachment 35698 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35698=edit Also remove SHM file if any Does this help? -- You are receiving this mail because: You are

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #2 from m...@blackmans.org --- looking at the code for apr_shm_remove at https://github.com/apache/apr/blob/1.6.1/shmem/unix/shm.c#L436 I am reminded that /* Indicate that the segment is to be destroyed as soon * as all

[Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.

2018-01-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62044 --- Comment #1 from m...@blackmans.org --- I believe the error arises here https://github.com/apache/httpd/blob/2.4.29/modules/slotmem/mod_slotmem_shm.c#L408 I assume the 'file exists' error refers to the SHM key rather than the placeholder