Cannot start stone, IPC identifier already exists
When you have multiple stones running on the same machine, particular if you are using multiple definitions for GEMSTONE_GLOBAL_DIR to define multiple separate lock file areas and gemstone-logical-spaces on the same machine, there is a risk that the same shared memory key will be computed by the OS. This results in an incorrect error that the IPC identifier already exists.
This occurs since the ftok() command is documented to have the risk of returning the same key for different files, since it only uses a set number of bits of the inode (plus device, plus project id).
Workaround
Upgrading is recommended. As an immediate workaround, creating files to order to use inodes would allow a different lock file inode to be allocated to avoid the conflict.
Last updated: 7/22/15