> Glad you figured things out ... as an FYI, the `$GS_HOME/bin/stones`
> command runs a `$GEMSTONE/bin/gslist -lc` and the `-c` arg to gslist
> cleans up stale lock files ...
>
> I may decide to add a `gslist -c` to the startStone command[1] to
> avoid this type of issue in the future ...
>
> Dale
>
> [1] https://github.com/GsDevKit/GsDevKit_home/issues/223
>
> On 12/13/18 5:07 AM, BrunoBB via Glass wrote:
>> Hi,
>>
>> After searching a little bit i found:
>> http://forum.world.st/Re-Error-Stoping-stone-Will-not-restart-td4965680.html 
>>
>> /Also ensure any stale files in /opt/gemstone/locks/ other than
>> the gemstone.hostid file are deleted. If no netldi nor stones running,
>> only file gemstone.hostid should exist in /opt/gemstone/locks ./
>>
>> And deleting some file at /opt/gemstone/locks/ the stone start without
>> problems.
>>
>> But the message error "Server 'devKit_34' is not a stone" is a little
>> confusing :)
>>
>> regards,
>> bruno
>>
>>
>>
>>
>> --
>> Sent from: http://forum.world.st/GLASS-f1460844.html
>> _______________________________________________
>> Glass mailing list
>> [hidden email]
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass