error at startup

Folks

I'm ussing appliance .
at startup  was following  error:


Starting stone: seaside
SHR_PAGE_CACHE_NUM_PROCS = 15;
 _____________________________________________________________________________
|                Gem Configuration Options for process id 7053                |
|_____________________________________________________________________________|

DUMP_OPTIONS = TRUE;
GEM_GCI_LOG_ENABLED = FALSE;
GEM_FREE_FRAME_CACHE_SIZE = -1;
GEM_FREE_FRAME_LIMIT = -1;
GEM_HALT_ON_ERROR = 0;
GEM_IO_LIMIT = 5000;
GEM_KEEP_MIN_SOFTREFS = 0;
GEM_MAX_SMALLTALK_STACK_DEPTH = 1000;
GEM_PRIVATE_PAGE_CACHE_KB = 1000;
GEM_PGSVR_FREE_FRAME_CACHE_SIZE = -1;
GEM_PGSVR_FREE_FRAME_LIMIT = -1;
GEM_PGSVR_UPDATE_CACHE_ON_READ = FALSE;
GEM_RPCGCI_TIMEOUT = 0;
GEM_SOFTREF_CLEANUP_PERCENT_MEM = 50;
GEM_TEMPOBJ_AGGRESSIVE_STUBBING = TRUE;
GEM_TEMPOBJ_CACHE_SIZE = 50000;
GEM_TEMPOBJ_INITIAL_SIZE not used on this platform
GEM_TEMPOBJ_MESPACE_SIZE = 0;
GEM_TEMPOBJ_OOPMAP_SIZE = 0;
GEM_TEMPOBJ_POMGEN_SIZE = 0;
GEM_TEMPOBJ_POMGEN_PRUNE_ON_VOTE = 50;
LOG_WARNINGS = FALSE;
SHR_NUM_FREE_FRAME_SERVERS = 1;
SHR_PAGE_CACHE_NUM_SHARED_COUNTERS = 1900;
SHR_PAGE_CACHE_SIZE_KB = 128000;
SHR_PAGE_CACHE_NUM_PROCS = 15;
SHR_TARGET_FREE_FRAME_COUNT = -1;
(vmGc spaceSizes: eden init 2000K max 9368K , survivor init 400K max 1568K,
 vmGc    old max 37496K, code max 10000K, perm max 5000K, pom 10 *
4168K = 41680K,
 vmGc    remSet 1008K, meSpace max 47800K oopMapSize 262144 )
cmdLine=
stopstone[Info]: GemStone version '2.3.0'

[Info]: Logging out at 02/20/10 10:18:52 PST
-----------------------------------------------------
GemStone: Error         Fatal
Unable to attach to shared cache. , unable to attach shared cache,
cache monitor connect failed, 2 0 The connection was rejected because:
The user limit has been reached.

Error Category: 231169 [GemStone] Number: 4139 Arg Count: 1 Context : 20
Arg 1:   20
startstone[Info]: GemStone version '2.3.0'
startstone[Info]: Server 'seaside' is already running.


any ideas?
best regards
MDC

Juan,

You are getting a userlimit error ... have you been editting the system.conf file on the appliance. I don't have a default appliance system.conf at hand, but it is suspicious that SHR_PAGE_CACHE_NUM_PROCS is set to 15, seems to be pretty low.


Here's the documentation on SHR_PAGE_CACHE_NUM_PROCS:

#=========================================================================
# SHR_PAGE_CACHE_NUM_PROCS
#
#   Maximum number of processes allowed to attach to the shared cache.
#   This parameter is used to allocate space in the shared page cache
#   for session information and cache statistics.
#   This cache space is in addition to extent page space allocated by
#   SHR_PAGE_CACHE_SIZE_KB.  This value must accommodate the GcGems and
#   various background GS processes, as well as user gem/topaz session
#   processes.  Using too small a value will result in sessions being
#   unable to login because they can't attach to the cache, while too
#   large a value will result in wasted space in the cache.
#
# Default: -1
#   The default setting causes the system to calculate a reasonable value
#   for this parameter based on:
#
#           STN_MAX_SESSIONS (for user sessions)
#           + 5 (for stone, pcmon, pagemanager, symbolgem and admingcgem)
#           + STN_NUM_GC_RECLAIM_SESSIONS (for reclaimgcgems)
#           + SHR_NUM_FREE_FRAME_SERVERS (for free frame page servers)
#           + STN_NUM_LOCAL_AIO_SERVERS  (for AIO page servers)
#           + 1 (for statmonitor, just in case)
#           + 1 (to allow stopstone to login)
#
#   While this value should be adequate for most cases, it may still yield
#   session login failures under special cases, such as:
#
#   * first-time startup of a system that needs to create new extents
#   * adding extents dynamically using SystemRepository>>createExtent:
#   * manually starting AIO or free frame page servers
#
#   Also, this value assumes that ALL sessions in the system will be
#   attaching to this cache.  If your architecture uses remote gem servers
#   with their own remote caches, you should specify a value for
#   SHR_PAGE_CACHE_NUM_PROCS using the above calculation but only allocating
#   space for those processes running on the local/remote host.  For example:
#
#   On stone machine:
#
#           Maximum number of user sessions running on stone machine
#           + 5 (for stone, pcmon, pagemanager, symbolgem, and admingcgem)
#           + STN_NUM_GC_RECLAIM_SESSIONS (for reclaimgcgems)
#           + SHR_NUM_FREE_FRAME_SERVERS (for free frame page servers)
#           + STN_NUM_LOCAL_AIO_SERVERS  (for AIO page servers)
#
#   On remote machine:
#
#           Maximum number of user sessions running on remote machine
#           + 2 (for pcmon, pgsvr)
#           + SHR_NUM_FREE_FRAME_SERVERS (for free frame page servers)
#
#
# Minimum:  number of extents (for startup page servers)
#           + 5 (for stone, pcmon, pagemanager, symbolgem and admingcgem)
#           + STN_NUM_GC_RECLAIM_SESSIONS (for reclaimgcgems)
#           + SHR_NUM_FREE_FRAME_SERVERS (for free frame page servers)
#           + STN_NUM_LOCAL_AIO_SERVERS (for AIO page servers)
#
#   While sufficient for starting the stone, the minimum may not
#   allow additional user or GcGem processes to attach to the cache,
#   regardless of the setting of STN_MAX_SESSIONS.
#
# Maximum:  STN_MAX_SESSIONS
#           + 5 (for stone, pcmon, pagemanager, symbolgem and admingcgem)
#           + 256 (maximum possible value for STN_NUM_GC_RECLAIM_SESSIONS)
#           + 30  (maximum possible value for SHR_NUM_FREE_FRAME_SERVERS)
#           + 256 (maximum possible value for STN_NUM_LOCAL_AIO_SERVERS)
#
#  The maximum may be further constrained by file descriptor limits.
#
#  If a value outside the range of minimum/maximum is specified, a warning
#  message will be printed and the value set to the minimum or maximum
#  as appropriate.
#
#SHR_PAGE_CACHE_NUM_PROCS = -1;

Dale

----- "Juan" <[hidden email]> wrote:

| Folks
|
| I'm ussing appliance .
| at startup  was following  error:
|
|
| Starting stone: seaside
| SHR_PAGE_CACHE_NUM_PROCS = 15;
|
| _____________________________________________________________________________
| |                Gem Configuration Options for process id 7053        
|        |
| |_____________________________________________________________________________|
|
| DUMP_OPTIONS = TRUE;
| GEM_GCI_LOG_ENABLED = FALSE;
| GEM_FREE_FRAME_CACHE_SIZE = -1;
| GEM_FREE_FRAME_LIMIT = -1;
| GEM_HALT_ON_ERROR = 0;
| GEM_IO_LIMIT = 5000;
| GEM_KEEP_MIN_SOFTREFS = 0;
| GEM_MAX_SMALLTALK_STACK_DEPTH = 1000;
| GEM_PRIVATE_PAGE_CACHE_KB = 1000;
| GEM_PGSVR_FREE_FRAME_CACHE_SIZE = -1;
| GEM_PGSVR_FREE_FRAME_LIMIT = -1;
| GEM_PGSVR_UPDATE_CACHE_ON_READ = FALSE;
| GEM_RPCGCI_TIMEOUT = 0;
| GEM_SOFTREF_CLEANUP_PERCENT_MEM = 50;
| GEM_TEMPOBJ_AGGRESSIVE_STUBBING = TRUE;
| GEM_TEMPOBJ_CACHE_SIZE = 50000;
| GEM_TEMPOBJ_INITIAL_SIZE not used on this platform
| GEM_TEMPOBJ_MESPACE_SIZE = 0;
| GEM_TEMPOBJ_OOPMAP_SIZE = 0;
| GEM_TEMPOBJ_POMGEN_SIZE = 0;
| GEM_TEMPOBJ_POMGEN_PRUNE_ON_VOTE = 50;
| LOG_WARNINGS = FALSE;
| SHR_NUM_FREE_FRAME_SERVERS = 1;
| SHR_PAGE_CACHE_NUM_SHARED_COUNTERS = 1900;
| SHR_PAGE_CACHE_SIZE_KB = 128000;
| SHR_PAGE_CACHE_NUM_PROCS = 15;
| SHR_TARGET_FREE_FRAME_COUNT = -1;
| (vmGc spaceSizes: eden init 2000K max 9368K , survivor init 400K max
| 1568K,
|  vmGc    old max 37496K, code max 10000K, perm max 5000K, pom 10 *
| 4168K = 41680K,
|  vmGc    remSet 1008K, meSpace max 47800K oopMapSize 262144 )
| cmdLine=
| stopstone[Info]: GemStone version '2.3.0'
|
| [Info]: Logging out at 02/20/10 10:18:52 PST
| -----------------------------------------------------
| GemStone: Error         Fatal
| Unable to attach to shared cache. , unable to attach shared cache,
| cache monitor connect failed, 2 0 The connection was rejected
| because:
| The user limit has been reached.
|
| Error Category: 231169 [GemStone] Number: 4139 Arg Count: 1 Context :
| 20
| Arg 1:   20
| startstone[Info]: GemStone version '2.3.0'
| startstone[Info]: Server 'seaside' is already running.
|
|
| any ideas?
| best regards
| MDC