[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 

http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/slotmem/mod_slotmem_shm.c?r1=1822341&r2=1822340&pathrev=1822341&view=patch

for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

[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);
396 rv = apr_shm_create(&shm, size, fname, gpool);
397 }

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

[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: create didn't find
/var/run/http/apache24/tmp/slotmem-shm-p7a67b429_balancer1.shm in gl
obal list
[Tue Jan 30 09:07:05.575357 2018] [slotmem_shm:debug] [pid 3716:tid
139969799624448] mod_slotmem_shm.c(390): AH02300: create
/var/run/http/apache24/tmp/slotmem-shm-p7a67b429_balancer1.shm: 1176/2
[Tue Jan 30 09:07:05.575398 2018] [slotmem_shm:error] [pid 3716:tid
139969799624448] (17)File exists: AH02611: create:
apr_shm_create(/var/run/http/apache24/tmp/slotmem-shm-p7a67b429_balancer1.shm)
failed
[Tue Jan 30 09:07:05.575442 2018] [:emerg] [pid 3716:tid 139969799624448]
AH00020: Configuration Failed, exiting

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

[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 (i.e. zero attached
processes) as though cleanup is not happening appropriately or is getting
bypassed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

[Bug 62061] New: FcgidInitialEnv per Directory or Location

2018-01-30 Thread bugzilla 
https://bz.apache.org/bugzilla/show_bug.cgi?id=62061

Bug ID: 62061
   Summary: FcgidInitialEnv per Directory or Location
   Product: Apache httpd-2
   Version: 2.5-HEAD
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: mod_fcgid
  Assignee: bugs@httpd.apache.org
  Reporter: r...@antcom.de
  Target Milestone: ---

Created attachment 35707
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35707&action=edit
Support FcgiInitialEnv in Directory / Location

FcgidInitialEnv currently can only be specified for a whole VirtualHost.

Consider an fcgi application that can be instantiated in different locations in
the same virtual host, but needs to be parameterized differently for those
different locations (and FcgidInitialEnv is a good mechanism for that).

E.g. a web file manager providing access to different areas on a web server
with different access levels.

I'm providing a patch that supports FcgidInitialEnv in separate Locations /
Directories. Now it can be specified both in VirtualHost as usual and
additionally in individual Directory or Location.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org