Aaron Bannert wrote:
The problem with doing that is you don't know if there already is an
apache instance running on the box when you blow away the memory segment.
But then Apache should have some way of guaranteeing that the memory
segment it intends to use, is dedicated to it.
Regards,
Graham
On Fri, Oct 03, 2003 at 06:47:16PM +0200, Graham Leggett wrote:
Is there no way that some cleanup process (whether it involves deleting
a file, or talking to the kernel, doesn't matter) can be done before an
attempt is made to create the shared memory segment?
The problem with doing that is
Kris Verbeeck wrote:
That won't solve the problem, the shared memory segment is still registered
somewhere in the kernel. I've had lots of problems with this too and only
deleting the file does not solve it. You have to remove the segments from
the kernel table too (see mail from Paul).
Is
On Fri, Oct 03, 2003 at 06:47:16PM +0200, Graham Leggett wrote:
Kris Verbeeck wrote:
That won't solve the problem, the shared memory segment is still registered
somewhere in the kernel. I've had lots of problems with this too and only
deleting the file does not solve it. You have to remove
Graham Leggett wrote:
Graham Leggett wrote:
My Apache server just went down, and now refuses to come up, logging the
following message:
[Wed Oct 01 11:16:12 2003] [error] Cannot allocate shared memory:
(17)File exists
There is no record of which module is emitting this message, nor does
the
Hi all,
My Apache server just went down, and now refuses to come up, logging the
following message:
[Wed Oct 01 11:16:12 2003] [error] Cannot allocate shared memory:
(17)File exists
There is no record of which module is emitting this message, nor does
the message say which file this is referring
The shared mem got left around after Apache crashed.
Assuming you are on Linux try:
ipcs # check for zero access count...
ipcrm shm XX # will remove the offending shmem id
ipcs will give you something like:
...
0x0102c028 776437784 rederpj 60056344 6
...
ipcrm
Graham Leggett wrote:
My Apache server just went down, and now refuses to come up, logging the
following message:
[Wed Oct 01 11:16:12 2003] [error] Cannot allocate shared memory:
(17)File exists
There is no record of which module is emitting this message, nor does
the message say which file this
