https://bz.apache.org/bugzilla/show_bug.cgi?id=69759
Bug ID: 69759
Summary: (17)File exists: AH00023: Couldn't create the proxy
mutex
Product: Apache httpd-2
Version: 2.4.65
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
[Sat Jul 26 00:01:23.934681 2025] [mpm_prefork:notice] [pid 13793:tid 13793]
AH00173: SIGHUP received. Attempting to restart
[Sat Jul 26 00:01:24.007069 2025] [core:emerg] [pid 13793:tid 13793] (17)File
exists: AH00023: Couldn't create the proxy mutex
[Sat Jul 26 00:01:24.007122 2025] [proxy:crit] [pid 13793:tid 13793] (17)File
exists: AH02478: failed to create proxy mutex
[Sat Jul 26 00:01:24.007138 2025] [:emerg] [pid 13793:tid 13793] AH00020:
Configuration Failed, exiting
My take: Restarting several Apache instances in close succession with SIGHUP or
SIGUSR1 seems to cause name clashes for POSIX semaphores. I am using apr-1.7.5
and the code in locks/unix/proc_mutex.c uses unix time (sec+usec) if a name is
not supplied, which is the case with the proxy mutex. Maybe the behavior of
mutex_needs_file can be changed for POSIX semaphores? I can alternatively
submit the problem to the APR team.
The system has Linux Kernel 5.10.240 with glibc 2.41.
Regards,
Michael Brunnbauer
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
