I've just run into this, and it is present in 2.0.36.. the name-based sysvmem isn't appropiate as it will cause apache to refuse to start when you upgrade a module (forcing a reboot)
a simple way to 'fix' is this it for the server to write out in the error message what sharedmem segment it is trying to create so you can ipcrm it. otherwise your forced to remove them all which is not a good thing
