[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 62838] semaphores appear to be leaking


mark@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

--- Comment #7 from mark@xxxxxxxxxxxxx ---
It is Linux, yes. Here's the -V output and I was under the impression
semaphores were the default mutex, but perhaps I've misunderstood. 

Server version: Apache/2.4.34 (Unix)
Server built:   Sep 14 2018 13:35:35
Server's Module Magic Number: 20120211:79
Server loaded:  APR 1.6.3, APR-UTIL 1.6.1
Compiled using: APR 1.6.3, APR-UTIL 1.6.1
Architecture:   64-bit
Server MPM:     event
  threaded:     yes (fixed thread count)
    forked:     yes (variable process count)
Server compiled with....
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D HTTPD_ROOT="/versions64/apache-2.4.34"
 -D SUEXEC_BIN="/versions64/apache-2.4.34/bin/suexec"
 -D DEFAULT_PIDLOG="logs/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"

I can believe the SIGKILL cases might represent orphans, although a central
registry of semaphores, say in the filesystem,  would allow this case to be
handled, but that's a lot of management overhead for what should be a rare

It would be difficult, but not impossible to reproduce the production
behaviours outside of production, which is why I was hoping some higher level
of tracing might give me some clues. I suppose, in the extreme, I could hook up
a permanent strace and hope there's enough surrounding detail to pinpoint who
exactly is creating the semaphores.

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