[Glass] startStone after reboot

[Dario Trussardi via Glass]

Ciao,

	i have a doubt.
	
	I need to create a Glass user profile? 

	Thanks,

		Dario

> Dario,
> 
> I'm not that familiar with GLASS or the devkit, but know a bit about GemStone and can comment at that level -- Dale may chime in with a more informed idea later...
> 
> The help text gives you some clues where to look:
> 
> > An error occurred when initializing the shared cache
> 
> Clear enough -- this is what the problem is, now to figure out what caused it...
> 
> > Help: 
> >   Operating system kernel configured for shared memory?
> 
> Well you got the system started at least once, so it's unlikely you haven't configured shared memory properly or it wouldn't have worked the first time.
> 
> >  Check SharedPageCache Monitor log file (*pcmon.log).
> 
> This is your best place to start  -- check this log file for errors and it should offer more insight into why the shared page cache could not be initialized.  It should point to one of the following possibilities:
> 
> >  Check SHR_PAGE_CACHE_NUM_PROCS in stone config file.
> 
> Not likely -- it would have prevented the first startup from working.
> 
> >  Stale files in /opt/gemstone/locks/<stonename>*?
> >  ipcs - check for stale resources ?
> 
> These two are possibilities -- the log file should give some indication.
> 
> Good Luck,
> 
> ------------------------------------------------------------------------
> Bill Erickson 
> GemTalk Systems Engineering
> 15220 NW Greenbrier Parkway #240, Beaverton OR 97006
> ------------------------------------------------------------------------
> 
> On Sat, Feb 21, 2015 at 4:26 AM, Dario Trussardi via Glass <glass at lists.gemtalksystems.com> wrote:
> Ciao,
> 
> 	i have a Ubuntu system where i load Development Kit Server Installation and
> 
> 	installServer devkit 3.1.0.6
> 
> 	After installation all works fine and i can login the repository from Gemtools.
> 
> 	Now i reboot the system and the	startStone devkit 		  answer:
> 
> startStone devkit
> Starting stone: devkit
> --- 21/02/2015 13:01:31.584 CET ---
> stopstone[Info]: GemStone version '3.1.0.6'
> stopstone[Info]: Server 'devkit' is not running.
> startstone[Info]: GemStone version '3.1.0.6'
> startstone[Info]: Starting Stone repository monitor 'devkit'.
> startstone[Info]: GEMSTONE is: '/opt/oodb/gsDevKitHome/gemstone/stones/devkit/product'.
> startstone[Info]: GEMSTONE_NRS_ALL is: '#dir:$GEMSTONE_LOGDIR#log:%N%P.log'.
> startstone[Info]:
>     GEMSTONE_SYS_CONF=/opt/oodb/gsDevKitHome/gemstone/stones/devkit/extents/system.conf
>     GEMSTONE_EXE_CONF=/opt/oodb/gsDevKitHome/gemstone/stones/devkit/devkit.conf
> startstone[Info]: Log file is '/opt/oodb/gsDevKitHome/gemstone/stones/devkit/logs/devkit.log'.
> 
> startstone[Error]: Stone process (id=1807) has died.
> startstone[Error]: Examine '/opt/oodb/gsDevKitHome/gemstone/stones/devkit/logs/devkit.log' for more information.  Excerpt follows:
>  The stone was unable to start a cache page server on host '<stone's host>'.
> Reason:  connect to cache monitor failed.
>   Monitor process (1809) did not start.
> 
> 
> Help: 
>   Operating system kernel configured for shared memory?
>   Check SharedPageCache Monitor log file (*pcmon.log).
>   Check SHR_PAGE_CACHE_NUM_PROCS in stone config file.
>   Stale files in /opt/gemstone/locks/<stonename>*?
>   ipcs - check for stale resources ?
> 
> An error occurred when initializing the shared cache
> 
>     Stone startup has failed.
> 
> 
> The relative devkit.log    report:
> 
> 	|    Key file:  /opt/oodb/gsDevKitHome/gemstone/products/GemStone64Bit3.1.0.6-x86_64.Linux/seaside/etc/gemstone.key
> | GemStone ID:  Free GS/S Web Edition                                         |
> | LICENSED TO:  GemStone Seaside Community                                    |
> |  KEY ORIGIN:  0x5e0a1e8d (a Linux x86)                                      |
> |_____________________________________________________________________________|
> 
> ========================================================================
>     Now starting GemStone monitor.
> 
> Write to /proc/1749/oom_score_adj failed with EACCES , linux user does not have CAP_SYS_RESOURCE
> No server process protection from OOM killer
>  _____________________________________________________________________________
> |     SESSION CONFIGURATION: The maximum number of concurrent sessions is 41. |
> |_____________________________________________________________________________|
> 
>     Attaching the Shared Cache using Stone name: devkit
> 
>  The stone was unable to start a cache page server on host '<stone's host>'.
> Reason:  connect to cache monitor failed.
>   Monitor process (1751) did not start.
> 
> Help:
>   Operating system kernel configured for shared memory?
>   Check SharedPageCache Monitor log file (*pcmon.log).
>   Check SHR_PAGE_CACHE_NUM_PROCS in stone config file.
>   Stale files in /opt/gemstone/locks/<stonename>*?
>   ipcs - check for stale resources ?
> 
> An error occurred when initializing the shared cache
> 
>     Stone startup has failed.
>                                           
> 
> Thanks for any consideration.
> 
> 	Dario
> 
> P.S.  After reboot the system, before any other command,  i do the command :    apt-get install gdisk.
> 
> 	Can this create some problem?
> 
> _______________________________________________
> 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/20150223/080f8aad/attachment.html>