[Glass] Host OS crash and GemStone

James Foster james.foster at gemtalksystems.com
Tue Oct 29 09:38:46 PDT 2013

Hi Bruno,

What you did is exactly right. The ‘lock’ files are created when a process starts and deleted when the process exits normally. If the process dies (not normally), then the lock file remains and the next startup attempt will fail because it thinks that something else is running. The solution (as you found) is to delete the lock files. 

A slightly safer approach is gslist with the ‘-c’ option to ‘cleanup’ stale locks. (This is only safer in the sense that you might accidentally delete a lock file for a running process.)

Because of the situation you describe, I’ve sometimes included a system start-up script that simply deletes everything in the locks directory on the general principle that if the system is starting then none of my processes are running yet.


On Oct 28, 2013, at 10:46 PM, BrunoBB <smalltalk at adinet.com.uy> wrote:

> Hi All,
> Today i was working with GemStone. Running VMware Player (with Centos Linux)
> over Windows 8.
> Suddenly Windows 8 crashed. All windows remained freeze. So i decided to
> shut it down.
> After this and inside Centos Linux again startGemStone failed to start. 
> I read the log and i remove all /opt/GemStone/Locks file. After this i
> startGemStone worked fine and no problem so far. (It is my development
> environment).
> Which is the general process when somethig like this happend ?
> I do not want a detailed explanation, only few indications or a link to some
> document to read.
> Regards,
> Bruno
> --
> View this message in context: http://forum.world.st/Host-OS-crash-and-GemStone-tp4717698.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

More information about the Glass mailing list