[Glass] Restore 3.1.0.6 backup

[Dale Henrichs via Glass]

Dario,

You may have run into a memory manager bug that has been fixed in later 
versions of GemStone ... you might try using a larger TOC to avoid the bug:

GEM_TEMPOBJ_CACHE_SIZE=200000;

let me know if that works,

Dale


On 10/30/2018 02:11 PM, Dale Henrichs wrote:
>
> Okay you're getting a SigSegv during scavenge and that is what is 
> killing the gem ... I'm having the gem log file analyzed to see what 
> else we can learn.
>
> Dale
>
>
> On 10/30/2018 12:51 PM, Trussardi Dario Romano via Glass wrote:
>> Dale,
>>>
>>> Dario,
>>>
>>> In the tODE shell try running the following:
>>>
>>> script --script=rebuildSys
>> I do this command  in the system where i restored the data ( Where 
>> the system is "unstable" after the SystemRepository 
>> restoreFromBackup: ..... )
>>
>>> If you get some walkbacks about missing directories go ahead press 
>>> the terminate button ... most of the repair should be complete ... 
>>> the repository paths will have to be repaired separately.
>>
>> The system answer the following error:
>> *a InternalError occurred ( error 2261 ) , The object with object ID 
>> *remoteNil is corrupt.**
>> *
>> *
>> *Reason 'store past end'*
>>
>> I press the Abort for some time.
>>
>> After 60 seconds the Ubuntu system open a window :
>>
>> " The application  gemhas closed unexpectedly "
>>
>>
>> The system is running with 86% of memory (of  8GB ) and  Swap at 81% 
>> ( of 8GB )
>>
>> The tode shell report :GciSessionNotLoggedInError: Session no longer 
>> logged in
>> The recent gem log file is:
>>
>>
>>
>> I need to restart the system ?
>>
>> Now when i do the tode shellws command  i have:
>>
>> a error dialog and do some click on the Abort  button the tode 
>> shell report after 50 seconds:
>> GciSessionNotLoggedInError: Session no longer logged in.
>> Dario
>>
>>>
>>> When I did a restore to a different machine I did notice that doing 
>>> an `ls` in the tODE shell gave me an "odd" result, but I didn't see 
>>> the issues that you were reporting ... rebuildSys should connect the 
>>> tODE directory structure to the current GsDevKit_home directory 
>>> structure ... if you copy over your git repositories to 
>>> $GS_HOME/shared/repos then the missing repo directory errors might 
>>> go away ---
>>>
>>> If they don't I should be able to suggest additional things to try 
>>> ... at the end of the day, we should be able to build up a repair 
>>> script that properly repairs the tODE structures when you are 
>>> restoring to completely different machine ... a use case that I had 
>>> not planned for ... but a use case that I think is important ...
>>>
>>
>>
>>
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20181030/3e89bac2/attachment.html>