Re: Semaphore bug
but is not apache who's living them opened ? Apache is installed on a low load server ( on a mandrake distro), and I'm shutting down cleanly apache each hour, so even after shutdown apache doesn't release anything, i think ... -pablo On Saturday 23 August 2003 17:42, Aaron Bannert wrote: You've simply exhausted your systemwide (or soft user limits) for that resource. Find out what type of lock you're using and increase the limit. -aaron On Friday, August 22, 2003, at 05:04 AM, Pablo Yaggi wrote: Hi, I notice the semaphore bug last night, is anybody working on it ? I saw is the last one on bugs report. The problem is apache left too many semaphores open, so it reuses to start with this kind of message (in my case) [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock is plenty space left on disk and if you check ipcs -s you'll notice a lot of apache's semaphores. cu Pablo
Semaphore bug
Hi, I notice the semaphore bug last night, is anybody working on it ? I saw is the last one on bugs report. The problem is apache left too many semaphores open, so it reuses to start with this kind of message (in my case) [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock is plenty space left on disk and if you check ipcs -s you'll notice a lot of apache's semaphores. cu Pablo
Re: Semaphore bug
You've simply exhausted your systemwide (or soft user limits) for that resource. Find out what type of lock you're using and increase the limit. -aaron On Friday, August 22, 2003, at 05:04 AM, Pablo Yaggi wrote: Hi, I notice the semaphore bug last night, is anybody working on it ? I saw is the last one on bugs report. The problem is apache left too many semaphores open, so it reuses to start with this kind of message (in my case) [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock is plenty space left on disk and if you check ipcs -s you'll notice a lot of apache's semaphores. cu Pablo
