The cache monitor connect failed on Gemstone startup.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

The cache monitor connect failed on Gemstone startup.

ARNi.e.
I'm moving an application in Smalltalk / Gemstone from Solaris box v5.8 to v5.10
Following the documentation from "System Administration Guide for GemStone/S 64 Bit Version 3.1 July 2012"
I have made the configurations. However something doesn't seem right.

Here is what is configured :

 _____________________________________________________________________________
|                             Configuration Files                             |
|                                                                             |
| System File: /gemstone/GemStone5.1.5-sparc.Solaris/data/system.conf         |
|                                                                             |
| Executable File: /home/gemadmin/gem.conf                                    |
| Warning:  File not found (errno=2, ENOENT, The file or directory specified  |
| cannot be found)                                                            |
|           using defaults.                                                   |
|_____________________________________________________________________________|


WARNING: SHR_NUM_FREE_FRAME_SERVERS is not a known GemStone option.
 _____________________________________________________________________________
|               Gem Configuration Options for process id 23379                |
|_____________________________________________________________________________|

GEM_DETACH_PAGES_ON_COMMIT = FALSE;
GEM_DETACH_PAGES_ON_ABORT = FALSE;
DUMP_OPTIONS = TRUE;
GEM_DBF_FILE_LOCK = TRUE;
GEM_GCI_LOG_ENABLED = FALSE;
GEM_FREE_FRAME_LIMIT = -1;
GEM_HALT_ON_ERROR = 0;
GEM_IO_LIMIT = 5000;
GEM_MAX_SMALLTALK_STACK_DEPTH = 1000;
GEM_NATIVE_CODE_MAX = 2048;
GEM_NATIVE_CODE_THRESHOLD = 4;
GEM_NOT_CONNECTED_DELTA = 300;
GEM_NOT_CONNECTED_THRESHOLD = 2000;
GEM_PRIVATE_PAGE_CACHE_KB = 20000,
20000;
GEM_RPCGCI_TIMEOUT = 0;
GEM_SHR_PAGE_CACHE_ENABLED = TRUE;
GEM_TEMPOBJ_CACHE_SIZE = 600;
LOG_WARNINGS = TRUE;
SHR_PAGE_CACHE_SIZE_KB = 400000;
SHR_PAGE_CACHE_NUM_PROCS = 8185;

Which configuration would help me solve the error "The cache monitor connect failed on Gemstone startup."  ?
Reply | Threaded
Open this post in threaded view
|

Re: The cache monitor connect failed on Gemstone startup.

James Foster-9
I’m not sure that this is a problem that will be solved with editing the configuration file. Could you provide more output from the stone log and from the shared page cache log file?

On Jun 26, 2014, at 2:20 AM, ARNi.e. <[hidden email]> wrote:

> *I'm moving an application in Smalltalk / Gemstone from Solaris box v5.8 to
> v5.10
> Following the documentation from "System Administration Guide for GemStone/S
> 64 Bit Version 3.1 July 2012"
> I have made the configurations. However something doesn't seem right.
>
> Here is what is configured :*
>
> _____________________________________________________________________________
> |                             Configuration Files                            
> |
> |                                                                            
> |
> | System File: /gemstone/GemStone5.1.5-sparc.Solaris/data/system.conf        
> |
> |                                                                            
> |
> | Executable File: /home/gemadmin/gem.conf                                  
> |
> | Warning:  File not found (errno=2, ENOENT, The file or directory specified
> |
> | cannot be found)                                                          
> |
> |           using defaults.                                                  
> |
> |_____________________________________________________________________________|
>
>
> WARNING: SHR_NUM_FREE_FRAME_SERVERS is not a known GemStone option.
>
> _____________________________________________________________________________
> |               Gem Configuration Options for process id 23379              
> |
> |_____________________________________________________________________________|
>
> GEM_DETACH_PAGES_ON_COMMIT = FALSE;
> GEM_DETACH_PAGES_ON_ABORT = FALSE;
> DUMP_OPTIONS = TRUE;
> GEM_DBF_FILE_LOCK = TRUE;
> GEM_GCI_LOG_ENABLED = FALSE;
> GEM_FREE_FRAME_LIMIT = -1;
> GEM_HALT_ON_ERROR = 0;
> GEM_IO_LIMIT = 5000;
> GEM_MAX_SMALLTALK_STACK_DEPTH = 1000;
> GEM_NATIVE_CODE_MAX = 2048;
> GEM_NATIVE_CODE_THRESHOLD = 4;
> GEM_NOT_CONNECTED_DELTA = 300;
> GEM_NOT_CONNECTED_THRESHOLD = 2000;
> GEM_PRIVATE_PAGE_CACHE_KB = 20000,
> 20000;
> GEM_RPCGCI_TIMEOUT = 0;
> GEM_SHR_PAGE_CACHE_ENABLED = TRUE;
> GEM_TEMPOBJ_CACHE_SIZE = 600;
> LOG_WARNINGS = TRUE;
> SHR_PAGE_CACHE_SIZE_KB = 400000;
> SHR_PAGE_CACHE_NUM_PROCS = 8185;
> *
> Which configuration would help me solve the error "The cache monitor connect
> failed on Gemstone startup."  ?*
>
>
>
> --
> View this message in context: http://forum.world.st/The-cache-monitor-connect-failed-on-Gemstone-startup-tp4764905.html
> Sent from the Gemstone/S mailing list archive at Nabble.com.
> _______________________________________________
> GemStone-Smalltalk mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk

_______________________________________________
GemStone-Smalltalk mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: The cache monitor connect failed on Gemstone startup.

ARNi.e.
Stone.log file :

--- Tue 01 Jul 2014 06:21:43 PDT ---
 The stone was unable to attach to a shared page cache on host '<stone's host>'.
Reason:  The cache monitor connect failed.
  Netldi 'netldi51' on host 'hstst631' reports the request 'shrpcmonitor gemserver51@135.161.94.133 50000 44 1 300' failed:
NetLdi interactive time limit (30 seconds) has been exceeded.

Help:
  Operating system kernel configured for shared memory?
  Check SharedPageCache Monitor log file.
  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 SHR_PAGE_CACHE_SIZE_KB = 400000;

<SHRPCMON, shell for GemStone SharedPageCache Monitor>
<Taking commands from command line.>
  NOTE:  Shared cache could not be locked in memory because this
         user does not have sufficient privileges to do so. (EPERM)
Shared memory region number 1 has id = 1509949494.
The shared semaphore array has id = 117440620.

What kind of permission do I need in order to go past this ? Will this resolve my issue ?
Reply | Threaded
Open this post in threaded view
|

Re: The cache monitor connect failed on Gemstone startup.

jgfoster
Tell us a bit more about the setup. What is the version of the stone (from the stone log)? What is the version of the NetLDI (from the NetLDI log)? What is the hostname and IP address of the stone machine? Does the Shared Page Cache Monitor report that the cache was created successfully? Have you compared notes with Abhishek Bahukhandi? He was working on a similar problem in May.

On Jul 1, 2014, at 6:35 AM, ARNi.e. <[hidden email]> wrote:

> *Stone.log file :*
>
> --- Tue 01 Jul 2014 06:21:43 PDT ---
> The stone was unable to attach to a shared page cache on host '<stone's
> host>'.
> Reason:  The cache monitor connect failed.
>  Netldi 'netldi51' on host 'hstst631' reports the request 'shrpcmonitor
> gemserver51@135.161.94.133 50000 44 1 300' failed:
> NetLdi interactive time limit (30 seconds) has been exceeded.
>
> Help:
>  Operating system kernel configured for shared memory?
>  Check SharedPageCache Monitor log file.
>  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 SHR_PAGE_CACHE_SIZE_KB = 400000;*
>
> <SHRPCMON, shell for GemStone SharedPageCache Monitor>
> <Taking commands from command line.>
>  NOTE:  Shared cache could not be locked in memory because this
>         user does not have sufficient privileges to do so. (EPERM)
> Shared memory region number 1 has id = 1509949494.
> The shared semaphore array has id = 117440620.
>
> *What kind of permission do I need in order to go past this ? Will this
> resolve my issue ?*
>
>
>
> --
> View this message in context: http://forum.world.st/The-cache-monitor-connect-failed-on-Gemstone-startup-tp4764905p4765933.html
> Sent from the Gemstone/S mailing list archive at Nabble.com.
> _______________________________________________
> GemStone-Smalltalk mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk
>

_______________________________________________
GemStone-Smalltalk mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: The cache monitor connect failed on Gemstone startup.

ARNi.e.
The command : chmod u+s $GEMSTONE/sys/shrpcmonitor $GEMSTONE/sys/startshrpcmon resolved the issue