Smalltalk › Gemtalk › GLASS

The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 12 messages Options
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
Hi,

i've performed a clean installation of Gemstone2.4.4.1 on Centos 5.5 within VMWare Fusion on a Mac, following these instructions: http://seaside.gemstone.com/userguide.html
All is looking good:

 gslist -lcv

Status  Version    Owner    Pid   Port   Started     Type  Name
------ --------- --------- ----- ----- ------------ ------ ----
  OK   2.4.4.1   nickager   8394 50377 Aug 09 13:39 Netldi gs64ldi
  OK   2.4.4.1   nickager   8435 50777 Aug 09 13:39 Stone  seaside
  OK   2.4.4.1   nickager   8436 41900 Aug 09 13:39 cache  [hidden email]

however when I try:

startSeaside_Hyper 50081

GemStone Smalltalk Compiler Errors:
 .
 .
 .
         [
           SeasidePlatformSupport transactionMutex 
 *         ^1                                                         *******
             critical: [ 
               SeasidePlatformSupport doAbortTransaction ].
           System enableSignaledAbortError.
         ] forkAt: Processor lowestPriority.
.
.
.
   service := SeasideHTTPService onPort: 50081 acceptInForeground: true multiThreading: false.
 *            ^2                                                                               
 
1: [1031] undefined symbol
2: [1031] undefined symbol

-------------

I've also tried connecting from the GemTools image, with a configuration of:

OGStandardSessionDescription new
name: 'Standard';
stoneHost: '172.16.181.138';
stoneName: 'seaside';
gemHost: '172.16.181.138';
netLDI: '50377';
userId: 'DataCurator';
password: 'swordfish';
backupDirectory: '';
yourself.

which results in the error: 'The Gemstone session has lost its connection to the Stone Repository Monitor, SocketRead failed"

Checking the log:

tail -f /opt/gemstone/log/seaside.log 
    Starting a Admin Gem process 
--- 08/09/2010 01:39:58 PM.670 BST :
    Starting a SymbolCreation Gem process 

    Session 2 with processId 8458 is now the Page Reclaim Gem for
    extents 0 through 0.

    Session 4 with processId 8462 is now the Admin Gem.
--- 08/09/2010 01:39:58 PM.744 BST :    Session 3 with processId 8466 is now the Symbol Creation Gem.

--- 08/09/2010 01:41:30 PM.418 BST : Could not get the network address of the Gem, session 5.
 Reason: No network error. , 
     Net 

------------

Any idea what I've forgotten to do?

Thanks

Nick
NorbertHartl
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

NorbertHartl
Hi,

On 09.08.2010, at 15:07, Nick Ager wrote:

Hi,

i've performed a clean installation of Gemstone2.4.4.1 on Centos 5.5 within VMWare Fusion on a Mac, following these instructions: http://seaside.gemstone.com/userguide.html
All is looking good:

 gslist -lcv

Status  Version    Owner    Pid   Port   Started     Type  Name
------ --------- --------- ----- ----- ------------ ------ ----
  OK   2.4.4.1   nickager   8394 50377 Aug 09 13:39 Netldi gs64ldi
  OK   2.4.4.1   nickager   8435 50777 Aug 09 13:39 Stone  seaside
  OK   2.4.4.1   nickager   8436 41900 Aug 09 13:39 cache  [hidden email]

however when I try:

startSeaside_Hyper 50081

I think it means you have no seaside installed or seaside 3.0. If you have installed seaside 3.0 than you need to use the startSeaside30_Adaptor script. The script isn't fully functional. So here is the way I got it running. Login into gemstone with the gemtools and issue on a workspace

WAGemStoneRunSeasideGems default adaptorClass: WAGsSwazooAdaptor

Than you can you need to start the script with two arguments

startSeaside30_Adaptor "http" 50081

Hope this helps,

Norbert
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
Hi Norbert,

Thanks for the reply.

I think it means you have no seaside installed or seaside 3.0. If you have installed seaside 3.0 than you need to use the startSeaside30_Adaptor script. The script isn't fully functional. So here is the way I got it running. Login into gemstone with the gemtools and issue on a workspace

Unfortunately I'm having problems logging into my Gemstone server from the Gemtools client - perhaps I need to fix that first! The login error I'm getting is: 'The Gemstone session has lost its connection to the Stone Repository Monitor, SocketRead failed', using a configuration of:

OGStandardSessionDescription new
name: 'Standard';
stoneHost: '172.16.181.138';
stoneName: 'seaside';
gemHost: '172.16.181.138';
netLDI: '50377';
userId: 'DataCurator';
password: 'swordfish';
backupDirectory: '';
yourself.

Checking the log:

tail -f /opt/gemstone/log/seaside.log 
    Starting a Admin Gem process 
--- 08/09/2010 01:39:58 PM.670 BST :
    Starting a SymbolCreation Gem process 

    Session 2 with processId 8458 is now the Page Reclaim Gem for
    extents 0 through 0.

    Session 4 with processId 8462 is now the Admin Gem.
--- 08/09/2010 01:39:58 PM.744 BST :    Session 3 with processId 8466 is now the Symbol Creation Gem.

--- 08/09/2010 01:41:30 PM.418 BST : Could not get the network address of the Gem, session 5.
 Reason: No network error. , 
     Net 

------------  
NorbertHartl
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

NorbertHartl

On 09.08.2010, at 15:51, Nick Ager wrote:

Hi Norbert,

Thanks for the reply.

I think it means you have no seaside installed or seaside 3.0. If you have installed seaside 3.0 than you need to use the startSeaside30_Adaptor script. The script isn't fully functional. So here is the way I got it running. Login into gemstone with the gemtools and issue on a workspace

Unfortunately I'm having problems logging into my Gemstone server from the Gemtools client - perhaps I need to fix that first! The login error I'm getting is: 'The Gemstone session has lost its connection to the Stone Repository Monitor, SocketRead failed', using a configuration of:

Uh, I'm not sure if I'm a great source of help for this one. Which extent did you use? I don't remember if the extent being installed is supposed to run seaside or offers remote login. There is a seaside extent in the installation. You might check the instruction manuals again if this should work. 
Could there be a firewall problem? Did you try the installation on localhost? 

Norbert


OGStandardSessionDescription new
name: 'Standard';
stoneHost: '172.16.181.138';
stoneName: 'seaside';
gemHost: '172.16.181.138';
netLDI: '50377';
userId: 'DataCurator';
password: 'swordfish';
backupDirectory: '';
yourself.

Checking the log:

tail -f /opt/gemstone/log/seaside.log 
    Starting a Admin Gem process 
--- 08/09/2010 01:39:58 PM.670 BST :
    Starting a SymbolCreation Gem process 

    Session 2 with processId 8458 is now the Page Reclaim Gem for
    extents 0 through 0.

    Session 4 with processId 8462 is now the Admin Gem.
--- 08/09/2010 01:39:58 PM.744 BST :    Session 3 with processId 8466 is now the Symbol Creation Gem.

--- 08/09/2010 01:41:30 PM.418 BST : Could not get the network address of the Gem, session 5.
 Reason: No network error. , 
     Net 

------------  
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
Uh, I'm not sure if I'm a great source of help for this one. Which extent did you use? I don't remember if the extent being installed is supposed to run seaside or offers remote login. There is a seaside extent in the installation.

Studying the installGemstone2.4-Linux-sh an extent is copied from /opt/gemstone/product/bin/extent0.seaside.dbf into /opt/gemstone/product/seaside/data/extent0.dbf
I renamed /opt/gemstone/product/seaside/data/extent0.dbf and ran the install again to get a fresh extent.  Unfortunately I saw the same errors when I ran startSeaside_Hyper 50081.

Could there be a firewall problem? Did you try the installation on localhost? 

I've disabled the firewall (temporarily) in case this was causing a problem.

I've also tried the installation on openSuse 11.3 with the same result.

Using the Gemstone appliance all is well - I can connect using GemTools-1.0-beta.8-231x ... however my application uses Seaside30 and Pier and AFAIK the only appliance available is for Seaside 2.8..

Nick 
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
I decided to simplify things and installed Gemstone locally on my Mac - so client and server are running on the same machine.
After a false start when I started the netldi service with "startnetldi" rather than "startnet" and it complained about "password validation failed" I can know connect start to make progress.  Still have the startSeaside_Hyper errors, but at least I can easily browse the code now and investigate.

The errors are:

startSeaside_Hyper 50081

GemStone Smalltalk Compiler Errors:
 .
 .
 .
         [
           SeasidePlatformSupport transactionMutex 
 *         ^1                                                         *******
             critical: [ 
               SeasidePlatformSupport doAbortTransaction ].
           System enableSignaledAbortError.
         ] forkAt: Processor lowestPriority.
.
.
.
   service := SeasideHTTPService onPort: 50081 acceptInForeground: true multiThreading: false.
 *            ^2                                                                               
 
1: [1031] undefined symbol
2: [1031] undefined symbol
Johan Brichau-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Johan Brichau-2
Hi Nick,

The error seems familiar to me. We stumbled upon it too.
I seem to remember we found a more up-to-date startup description for the current Gemstone version, but I cannot find where now.

Anyway, on the commandline do:

startnet
startGemstone

then use the gemtools image to login to the gem and you can start seaside from the admin menu (given that you loaded Seaside).

to load Seaside, see http://code.google.com/p/glassdb/wiki/Seaside30LoadOptions

If this is wrong, I'm sure Dale will correct me so we get it right too (but it seems to work just fine ;-)

Good luck!
Johan

On 09 Aug 2010, at 21:12, Nick Ager wrote:

> I decided to simplify things and installed Gemstone locally on my Mac - so client and server are running on the same machine.
> After a false start when I started the netldi service with "startnetldi" rather than "startnet" and it complained about "password validation failed" I can know connect start to make progress.  Still have the startSeaside_Hyper errors, but at least I can easily browse the code now and investigate.
>
> The errors are:
>
> startSeaside_Hyper 50081
>
> GemStone Smalltalk Compiler Errors:
>  .
>  .
>  .
>          [
>            SeasidePlatformSupport transactionMutex
>  *         ^1                                                         *******
>              critical: [
>                SeasidePlatformSupport doAbortTransaction ].
>            System enableSignaledAbortError.
>          ] forkAt: Processor lowestPriority.
> .
> .
> .
>    service := SeasideHTTPService onPort: 50081 acceptInForeground: true multiThreading: false.
>  *            ^2                                                                              
>  
> 1: [1031] undefined symbol
> 2: [1031] undefined symbol

Dale Henrichs
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Dale Henrichs
In reply to this post by Nick
Nick,

The error about SeasidePlatformSupport not being defined is telling you
that Seaside2.8 is not installed.

The instructions on http://seaside.gemstone.com/userguide.html haven't
been updated for 2.4.4.1 and 1.0-beta.8. A better place to look for
guidance would be to start with the 2.4.4.1 post:

http://gemstonesoup.wordpress.com/2010/07/15/gemstones-64-version-2-4-4-1-is-shipping/

The extent that ships with 2.4.4.1 does not have Seaside pre-installed.
as Seaside2.8 and Seaside3.0 are incompatible. To install Seaside2.8
follow these instructions:

   http://code.google.com/p/glassdb/wiki/Seaside28Configuration

Follow these instructions for Seaside3.0:

   http://code.google.com/p/glassdb/wiki/Seaside30Configuration

Dale

Nick Ager wrote:

> Hi,
>
> i've performed a clean installation of Gemstone2.4.4.1 on Centos 5.5
> within VMWare Fusion on a Mac, following these
> instructions: http://seaside.gemstone.com/userguide.html
> All is looking good:
>
>  gslist -lcv
>
> Status  Version    Owner    Pid   Port   Started     Type  Name
> ------ --------- --------- ----- ----- ------------ ------ ----
>   OK   2.4.4.1   nickager   8394 50377 Aug 09 13:39 Netldi gs64ldi
>   OK   2.4.4.1   nickager   8435 50777 Aug 09 13:39 Stone  seaside
>   OK   2.4.4.1   nickager   8436 41900 Aug 09 13:39 cache
>  [hidden email]
>
> however when I try:
>
> startSeaside_Hyper 50081
>
> GemStone Smalltalk Compiler Errors:
>  .
>  .
>  .
>          [
>            SeasidePlatformSupport transactionMutex
>  *         ^1                                                        
> *******
>              critical: [
>                SeasidePlatformSupport doAbortTransaction ].
>            System enableSignaledAbortError.
>          ] forkAt: Processor lowestPriority.
> .
> .
> .
>    service := SeasideHTTPService onPort: 50081 acceptInForeground: true
> multiThreading: false.
>  *            ^2                                                        
>                      
>  
> 1: [1031] undefined symbol
> 2: [1031] undefined symbol
>
> -------------
>
> I've also tried connecting from the GemTools image, with a configuration of:
>
> OGStandardSessionDescription new
> name: 'Standard';
> stoneHost: '172.16.181.138';
> stoneName: 'seaside';
> gemHost: '172.16.181.138';
> netLDI: '50377';
> userId: 'DataCurator';
> password: 'swordfish';
> backupDirectory: '';
> yourself.
>
> which results in the error: 'The Gemstone session has lost its
> connection to the Stone Repository Monitor, SocketRead failed"
>
> Checking the log:
>
> tail -f /opt/gemstone/log/seaside.log
>     Starting a Admin Gem process
> --- 08/09/2010 01:39:58 PM.670 BST :
>     Starting a SymbolCreation Gem process
>
>     Session 2 with processId 8458 is now the Page Reclaim Gem for
>     extents 0 through 0.
>
>     Session 4 with processId 8462 is now the Admin Gem.
> --- 08/09/2010 01:39:58 PM.744 BST :    Session 3 with processId 8466 is
> now the Symbol Creation Gem.
>
> --- 08/09/2010 01:41:30 PM.418 BST : Could not get the network address
> of the Gem, session 5.
>  Reason: No network error. ,
>      Net
>
> ------------
>
> Any idea what I've forgotten to do?
>
> Thanks
>
> Nick

Dale Henrichs
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Dale Henrichs
In reply to this post by Nick
Nick Ager wrote:
> I decided to simplify things and installed Gemstone locally on my Mac -
> so client and server are running on the same machine.

Things get more complex when you are looking to connect GemTools from a
remote host. For instructions on doing do see:

   http://programminggems.wordpress.com/2010/01/12/slicehost-2/

There is also more info about how to manage remote gems in the System
Administration Guide.

Dale
SeanTAllen
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

SeanTAllen
Nick,

I've done plenty of connecting to remote gemstone instances via
gemtools. If you need help, let me know.

On Mon, Aug 9, 2010 at 5:46 PM, Dale Henrichs <[hidden email]> wrote:

> Nick Ager wrote:
>>
>> I decided to simplify things and installed Gemstone locally on my Mac - so
>> client and server are running on the same machine.
>
> Things get more complex when you are looking to connect GemTools from a
> remote host. For instructions on doing do see:
>
>  http://programminggems.wordpress.com/2010/01/12/slicehost-2/
>
> There is also more info about how to manage remote gems in the System
> Administration Guide.
>
> Dale
>
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
In reply to this post by Dale Henrichs
Hi Dale,

Thanks for the reply. Now I've managed to connect with GemTools it's all starting to make a lot more sense; I can see what in the system etc.
So far so good...

Nick

On 9 August 2010 22:33, Dale Henrichs <[hidden email]> wrote:
Nick,

The error about SeasidePlatformSupport not being defined is telling you that Seaside2.8 is not installed.

The instructions on http://seaside.gemstone.com/userguide.html haven't been updated for 2.4.4.1 and 1.0-beta.8. A better place to look for guidance would be to start with the 2.4.4.1 post:

http://gemstonesoup.wordpress.com/2010/07/15/gemstones-64-version-2-4-4-1-is-shipping/

The extent that ships with 2.4.4.1 does not have Seaside pre-installed. as Seaside2.8 and Seaside3.0 are incompatible. To install Seaside2.8 follow these instructions:

 http://code.google.com/p/glassdb/wiki/Seaside28Configuration

Follow these instructions for Seaside3.0:

 http://code.google.com/p/glassdb/wiki/Seaside30Configuration

Dale


Nick Ager wrote:
Hi,

i've performed a clean installation of Gemstone2.4.4.1 on Centos 5.5 within VMWare Fusion on a Mac, following these instructions: http://seaside.gemstone.com/userguide.html
All is looking good:

 gslist -lcv

Status  Version    Owner    Pid   Port   Started     Type  Name
------ --------- --------- ----- ----- ------------ ------ ----
 OK   2.4.4.1   nickager   8394 50377 Aug 09 13:39 Netldi gs64ldi
 OK   2.4.4.1   nickager   8435 50777 Aug 09 13:39 Stone  seaside
 OK   2.4.4.1   nickager   8436 41900 Aug 09 13:39 cache  [hidden email]

however when I try:

startSeaside_Hyper 50081

GemStone Smalltalk Compiler Errors:
 .
 .
 .
        [
          SeasidePlatformSupport transactionMutex  *         ^1                                                         *******
            critical: [                SeasidePlatformSupport doAbortTransaction ].
          System enableSignaledAbortError.
        ] forkAt: Processor lowestPriority.
.
.
.
  service := SeasideHTTPService onPort: 50081 acceptInForeground: true multiThreading: false.
 *            ^2                                                                                1: [1031] undefined symbol
2: [1031] undefined symbol

-------------

I've also tried connecting from the GemTools image, with a configuration of:

OGStandardSessionDescription new
name: 'Standard';
stoneHost: '172.16.181.138';
stoneName: 'seaside';
gemHost: '172.16.181.138';
netLDI: '50377';
userId: 'DataCurator';
password: 'swordfish';
backupDirectory: '';
yourself.

which results in the error: 'The Gemstone session has lost its connection to the Stone Repository Monitor, SocketRead failed"

Checking the log:

tail -f /opt/gemstone/log/seaside.log     Starting a Admin Gem process --- 08/09/2010 01:39:58 PM.670 BST :
   Starting a SymbolCreation Gem process
   Session 2 with processId 8458 is now the Page Reclaim Gem for
   extents 0 through 0.

   Session 4 with processId 8462 is now the Admin Gem.
--- 08/09/2010 01:39:58 PM.744 BST :    Session 3 with processId 8466 is now the Symbol Creation Gem.

--- 08/09/2010 01:41:30 PM.418 BST : Could not get the network address of the Gem, session 5.
 Reason: No network error. ,      Net
------------

Any idea what I've forgotten to do?

Thanks

Nick
Nick
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: The Gemstone session has lost its connection to the Stone Repository monitor, SocketRead failed.

Nick
In reply to this post by SeanTAllen
Hi Sean,

I've done plenty of connecting to remote gemstone instances via
gemtools. If you need help, let me know.


Thanks for the offer of assistance, I'll certainly let you know when I get stuck again. Now I've managed to connect GemTools to a local Gemstone server, my immediate focus is moving my app into Gemstone, but I'll revisit my Linux Gemstone setup in the next few days. There's nothing that immediately jumps out at me that I missed or did incorrectly from reading Jame's slice host post, though as I say I'll revisit in the next few days with a fresh set of eyes.

Thanks again

Nick
Free forum by Nabble Edit this page