Bug 9304

GemStone/S

6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, earlier versions

All

Page server processes continue to exist after stopstone

Page server processes can continue to exist after a stopstone, or
after a remote machine on which a gem was running has crashed or been
rebooted.

If this happens, a message similar to the following may appear in the
monitor log when you attempt to restart GemStone:

Error = exclusive open:  file is open by another process
UNIX Codes = errno=13, EACCES, Authorization failure"
Error in opening repository for exclusive access.
Error in stone startup.

Workaround

Close any other Gem sessions (including Topaz sessions) that are
accessing the repository you are trying to restart, or wait for a
copydbf to complete.  Us ps -ef (the options on your system may
differ) to identify any pgsvrmain processes that are still running,
and then use kill processid to terminate them.  Try to start
GemStone again.

FOR GEMSTONE VERSIONS 5.0 AND ABOVE
You can use the keepalive network option, as explained in Chapter 3
of the GemStone System Administration Guide.


Last updated: