https://issues.apache.org/bugzilla/show_bug.cgi?id=57526
Bug ID: 57526
Summary: Apache 2.2.29_openssl-1.0.1k_x86_64 Error creating
semaphore - No space left on device (28
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: All
Assignee: [email protected]
Reporter: [email protected]
Hello,
Environment Details:
Apache: apache-2.2.29_openssl-1.0.1k_x86_64
Linux: Linux 2.6.18-400.1.1.el5 #1 SMP Sun Dec 14 06:01:17 EST 2014 x86_64
x86_64 x86_64 GNU/Linux
Proxy servers: 34 instances (httpd)
Virtual Proxy: 68 instances
Problem:
We have recently updated apache from apache-2.2.27_openssl-1.0.1g_x86_64 to
apache-2.2.29_openssl-1.0.1k_x86_64 in PROD server (details above). We have
stated receiving the semaphore issues.
[26/Jan/2015:18:53:28] [Info] [CA WebAgent IPC] [3033] [CSmSem::getSem]
Attempted to attach to non-existent semaphore with key 0xc8b9bf3c
[26/Jan/2015:18:53:28] [Error] [CA WebAgent IPC] [3033] [CSmSem::getSem] Error
creating semaphore using key 0xc8b9bf3c - No space left on device (28)
The same was done to QA servers also, but no errors found(varies because of
load)
Current Configuration:
#kernel.sem=<SEMMSL> <SEMMNS> <SEMOPM> <SEMMNI>
kernel.sem=512 524288 100 1024
# Controls the maximum shared segment size, in bytes
kernel.shmmax = 68719476736
# Controls the maximum number of shared memory segments, in pages
kernel.shmall = 4294967296
Question:
1. Does apache-2.2.29 have more memory requirement than apache-2.2.27?
2. Could you please help us in checking the thread-safety for below modules
used in our environement:
libmod_sm22.so
mod_actions.so
mod_alias.so
mod_asis.so
mod_authz_host.so
mod_autoindex.so
mod_deflate.so
mod_dir.so
mod_filter.so
mod_headers.so
mod_include.so
mod_negotiation.so
mod_proxy_balancer.so
mod_rewrite.so
mod_setenvif.so
mod_status.so
mod_logio.so
3. Do you consider updating the kernel semaphore on sysctl.conf based on the
values shown above?
Thanks in advance.
Best Regards,
Atul Sharma
--
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]
