https://issues.apache.org/bugzilla/show_bug.cgi?id=57526
Yann Ylavic <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Yann Ylavic <[email protected]> --- (In reply to Atul Sharma from comment #0) > > [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) This is a SiteMinder's module error. > 1. Does apache-2.2.29 have more memory requirement than apache-2.2.27? No it does not. > 2. Could you please help us in checking the thread-safety for below modules > used in our environement: > libmod_sm22.so We can't talk about this module which is not maintained by the ASF nor supported in this bugzilla. > 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 This ones are thread-safe (when used with a threaded MPM). > 3. Do you consider updating the kernel semaphore on sysctl.conf based on the > values shown above? The values look good for your httpd's use, but it also depends on other software using SysV IPC on the system. The issue is probably more about semaphores which are not cleaned when httpd stops (or is it killed? crashes? libmod_sm22 cleanup?), and hence previous ones stay on the system until no more is available. I'm rejecting this report since it's not an httpd issue, please contact SiteMinder's support. -- 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]
