Smalltalk › Gemtalk › GLASS

was gems don't start

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

20 messages Options

Juan-2

was gems don't start

folks i have followind error , received on the browser.

InterpreterError 2258: Primitive failed , selector <#'_sessionCacheStatAt:'> receiver .

any clue?
best regards
mdc

Dale Henrichs

Re: was gems don't start

Juan,

So it seems that you have the seaside gems started? Are you runnning Seaside2.8?

There should be a stack dumped into the gem log ... the logs should be present in /op/gemstone/log (or is it /opt/gemstone/logs?)... There should be 3 *fastcgi* logs to look at ...

Dale

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, June 8, 2011 3:47:48 PM
| Subject: [GS/SS Beta] was gems don't start
|
| folks i have followind error , received on the browser.
|
|
| InterpreterError 2258: Primitive failed , selector
| <#'_sessionCacheStatAt:'> receiver .
| any clue?
| best regards
| mdc
|

Juan-2

Re: was gems don't start

On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

So it seems that you have the seaside gems started? Are you runnning Seaside2.8?

yes i copied the extent running at appliance, i do:

copydbf -i

show me transaction file necesary for extent
copy that files at data directory.

There should be a stack dumped into the gem log ... the logs should be present in /op/gemstone/log (or is it /opt/gemstone/logs?)... There should be 3 *fastcgi* logs to look at ...

Ok tomorrow i check

thanks a lot

mdc

Dale

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, June 8, 2011 3:47:48 PM
| Subject: [GS/SS Beta] was gems don't start
|
| folks i have followind error , received on the browser.
|
|
| InterpreterError 2258: Primitive failed , selector
| <#'_sessionCacheStatAt:'> receiver .
| any clue?
| best regards
| mdc
|

Juan-2

Re: was gems don't start

In reply to this post by Dale Henrichs

Hi Dale , folks

On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

So it seems that you have the seaside gems started? Are you runnning Seaside2.8?

There should be a stack dumped into the gem log ... the logs should be present in /op/gemstone/log (or is it /opt/gemstone/logs?)... There should be 3 *fastcgi* logs to look at ...

|             GemStone/S64 Object-Oriented Data Management System             |
|               Copyright (C) GemStone Systems, Inc. 1986-2011                |
|                            All rights reserved.                             |
|     covered by Patent Number 6,567,905 Generational Garbage Collector.      |
+-----------------------------------------------------------------------------+
|    PROGRAM: topaz, Linear GemStone Interface (Linked Session)               |
|    VERSION: 2.4.4.4, Thu Jan 27 14:16:02 2011                               |
|      BUILD: gss64_2_4_4_x_branch-25116                                      |
| BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 1-CPU glass x86_64 (Linux 2.6.36-gentoo-r8 #1 SMP Tue Mar 29 17:27:54
| Local time zone must be set--see zic ) 369MB                                |
| PROCESS ID: 16468     DATE: 06/08/11 19:30:16 ART                           |
|   USER IDS: REAL=glass (1000) EFFECTIVE=glass (1000)                        |
|   DATEFORMAT: %m/%d/%y %H:%M:%S                                             |
|_____________________________________________________________________________|
[Info]: LNK client/gem GCI levels = 844/844
[06/08/11 19:31:05.962 ART] gci login: currSession 1 rpc gem processId -1
topaz 1> Warning: GemStone is clearing the previous GemStone password.
topaz 1> topaz 1> topaz 1> topaz 1> topaz 1> -----------------------------------------------------
GemStone: Error         Nonfatal
The current GCI session is already logged in.
Error Category: 231169 [GemStone] Number: 2147 Arg Count: 0 Context : 20

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> topaz 1> [20 sz:0 cls: 76289 UndefinedObject] nil
topaz 1> topaz 1> FastCGI Server started on port 9001
----------- Internal FASTCGI LOG ENTRY: anArray-----------
----------- Internal FASTCGI ERROR Encountered: 2011-06-08T19:37:50-03:00
InterpreterError 2258: Primitive failed , selector <#'_sessionCacheStatAt:'> receiver <System> .
1 SeasidePlatformSupport class >> logError:title: @2 line 5 [GsMethod OOP 371936769]
2 FSSeasideHandler >> internalServerMalfunction: @21 line 16 [GsMethod OOP 104507649]
3 ComplexBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @50 line 48 [GsMethod OOP 375252737]
4 ExceptionA >> valueHandler: @7 line 8 [GsMethod OOP 11889665]
5 ComplexBlock in ExceptionHandler >> valueHandlerBlock @6 line 5 [GsMethod OOP 11916545]
6 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
7 ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
8 ExceptionHandler >> valueHandlerBlock @10 line 6 [GsMethod OOP 11916545]
9 ExceptionHandler >> caughtException @3 line 4 [GsMethod OOP 11916033]
10 ExceptionHandler >> caughtEx:number:cat:args: @16 line 19 [GsMethod OOP 11921665]
11 ComplexBlock in ExceptionHandler >> try:on:in:do: @9 line 9 [GsMethod OOP 11915521]
12 Exception >> _signal:number:args: @2 line 7 [GsMethod OOP 2974209]
13 System class >> signal:args:signalDictionary: @5 line 13 [GsMethod OOP 3264001]
14 Object >> _error:args: @7 line 10 [GsMethod OOP 1946113]
15 Object >> _primitiveFailed: @2 line 7 [GsMethod OOP 1945089]
16 System class >> _sessionCacheStatAt: @3 line 8 [GsMethod OOP 3206657]
17 ComplexVCBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @43 line 45 [GsMethod OOP 375252737]
18 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
19 ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
20 TransientRecursionLock >> critical: @15 line 8 [GsMethod OOP 28295169]
21 ComplexVCBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @46 line 6 [GsMethod OOP 375252737]
22 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
23 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
24 ComplexVCBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
25 FSSeasideHandler >> answerResponderRoleCheckingLock: @53 line 46 [GsMethod OOP 375252737]
26 FSSeasideHandler >> answerResponderRole: @3 line 6 [GsMethod OOP 104507905]
27 FSResponderRole >> answer @2 line 4 [GsMethod OOP 59729153]
28 FSRole >> handleConnection @3 line 5 [GsMethod OOP 59722241]
29 FSConnection >> unsafeServe @4 line 8 [GsMethod OOP 98192385]
30 ComplexBlock in FSConnection >> safeServe @5 line 8 [GsMethod OOP 105202177]
31 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
32 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
33 ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
34 ComplexVCBlock in FSConnection >> safeServe @8 line 9 [GsMethod OOP 105202177]
35 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
36 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
37 ComplexVCBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
38 ComplexVCBlock in FSConnection >> safeServe @11 line 12 [GsMethod OOP 105202177]
39 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
40 ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
41 FSConnection >> safeServe @14 line 15 [GsMethod OOP 105202177]
42 FSConnection >> serve @1 line 4 [GsMethod OOP 98188801]
43 ComplexBlock in FSSocketServer >> listen: @9 line 15 [GsMethod OOP 103703297]
44 GsProcess >> _startPart2 @13 line 17 [GsMethod OOP 2997761]
45 GsProcess >> _start @1 line 9 [GsMethod OOP 2998273]
-----------

best
MDC

Dale

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, June 8, 2011 3:47:48 PM
| Subject: [GS/SS Beta] was gems don't start
|
| folks i have followind error , received on the browser.
|
|
| InterpreterError 2258: Primitive failed , selector
| <#'_sessionCacheStatAt:'> receiver .
| any clue?
| best regards
| mdc
|

Juan-2

Re: was gems don't start

Dale

googling i'm find

System class >> sessionCacheStatAt: at
http://community.gemstone.com/download/attachments/6037520/GS64-ReleaseNotes-3.0Beta.pdf?version=1

New public API for session cache statistics
The method in System class to get and set sessionCacheStatistics (_sessionCacheStatAt:, etc.) have officially-public method interface, named without the leading underscore.
new methods are:
System class >> sessionCacheStatAt:
System class >> sessionCacheStatAt:put:
System class >> sessionCacheStatAt:decrementBy:
System class >> sessionCacheStatAt:incrementBy:
System class >> sessionCacheStatsForProcessSlot:
System class >> sessionCacheStatsForSessionId:
Although existing methods with the leading underscore are unchanged, we recommend using these public selectors.

but this is for 3.0 beta release. confuse to me, because i copied extent.dbf form 2.8 version (from old appliance 2.8 seaside ) and corresp. trans.log
this is confusing .. any clue?

best
MDC

On Fri, Jun 10, 2011 at 11:36 AM, Juan <[hidden email]> wrote:

Hi Dale , folks

On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

So it seems that you have the seaside gems started? Are you runnning Seaside2.8?

There should be a stack dumped into the gem log ... the logs should be present in /op/gemstone/log (or is it /opt/gemstone/logs?)... There should be 3 *fastcgi* logs to look at ...

|             GemStone/S64 Object-Oriented Data Management System             |
|               Copyright (C) GemStone Systems, Inc. 1986-2011                |
|                            All rights reserved.                             |
|     covered by Patent Number 6,567,905 Generational Garbage Collector.      |
+-----------------------------------------------------------------------------+
|    PROGRAM: topaz, Linear GemStone Interface (Linked Session)               |
|    VERSION: 2.4.4.4, Thu Jan 27 14:16:02 2011                               |
|      BUILD: gss64_2_4_4_x_branch-25116                                      |
| BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 1-CPU glass x86_64 (Linux 2.6.36-gentoo-r8 #1 SMP Tue Mar 29 17:27:54
| Local time zone must be set--see zic ) 369MB                                |
| PROCESS ID: 16468     DATE: 06/08/11 19:30:16 ART                           |
|   USER IDS: REAL=glass (1000) EFFECTIVE=glass (1000)                        |
|   DATEFORMAT: %m/%d/%y %H:%M:%S                                             |
|_____________________________________________________________________________|
[Info]: LNK client/gem GCI levels = 844/844
[06/08/11 19:31:05.962 ART] gci login: currSession 1 rpc gem processId -1
topaz 1> Warning: GemStone is clearing the previous GemStone password.
topaz 1> topaz 1> topaz 1> topaz 1> topaz 1> -----------------------------------------------------
GemStone: Error         Nonfatal
The current GCI session is already logged in.
Error Category: 231169 [GemStone] Number: 2147 Arg Count: 0 Context : 20

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> topaz 1> [20 sz:0 cls: 76289 UndefinedObject] nil
topaz 1> topaz 1> FastCGI Server started on port 9001
----------- Internal FASTCGI LOG ENTRY: anArray-----------
----------- Internal FASTCGI ERROR Encountered: 2011-06-08T19:37:50-03:00
InterpreterError 2258: Primitive failed , selector <#'_sessionCacheStatAt:'> receiver <System> .
1 SeasidePlatformSupport class >> logError:title: @2 line 5 [GsMethod OOP 371936769]
2 FSSeasideHandler >> internalServerMalfunction: @21 line 16 [GsMethod OOP 104507649]
3 ComplexBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @50 line 48 [GsMethod OOP 375252737]
4 ExceptionA >> valueHandler: @7 line 8 [GsMethod OOP 11889665]
5 ComplexBlock in ExceptionHandler >> valueHandlerBlock @6 line 5 [GsMethod OOP 11916545]
6 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
7 ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
8 ExceptionHandler >> valueHandlerBlock @10 line 6 [GsMethod OOP 11916545]
9 ExceptionHandler >> caughtException @3 line 4 [GsMethod OOP 11916033]
10 ExceptionHandler >> caughtEx:number:cat:args: @16 line 19 [GsMethod OOP 11921665]
11 ComplexBlock in ExceptionHandler >> try:on:in:do: @9 line 9 [GsMethod OOP 11915521]
12 Exception >> _signal:number:args: @2 line 7 [GsMethod OOP 2974209]
13 System class >> signal:args:signalDictionary: @5 line 13 [GsMethod OOP 3264001]
14 Object >> _error:args: @7 line 10 [GsMethod OOP 1946113]
15 Object >> _primitiveFailed: @2 line 7 [GsMethod OOP 1945089]
16 System class >> _sessionCacheStatAt: @3 line 8 [GsMethod OOP 3206657]
17 ComplexVCBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @43 line 45 [GsMethod OOP 375252737]
18 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
19 ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
20 TransientRecursionLock >> critical: @15 line 8 [GsMethod OOP 28295169]
21 ComplexVCBlock in FSSeasideHandler >> answerResponderRoleCheckingLock: @46 line 6 [GsMethod OOP 375252737]
22 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
23 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
24 ComplexVCBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
25 FSSeasideHandler >> answerResponderRoleCheckingLock: @53 line 46 [GsMethod OOP 375252737]
26 FSSeasideHandler >> answerResponderRole: @3 line 6 [GsMethod OOP 104507905]
27 FSResponderRole >> answer @2 line 4 [GsMethod OOP 59729153]
28 FSRole >> handleConnection @3 line 5 [GsMethod OOP 59722241]
29 FSConnection >> unsafeServe @4 line 8 [GsMethod OOP 98192385]
30 ComplexBlock in FSConnection >> safeServe @5 line 8 [GsMethod OOP 105202177]
31 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
32 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
33 ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
34 ComplexVCBlock in FSConnection >> safeServe @8 line 9 [GsMethod OOP 105202177]
35 ExceptionHandler >> try:on:in:do: @13 line 13 [GsMethod OOP 11915521]
36 ExceptionA class >> try:on:do: @2 line 4 [GsMethod OOP 12096257]
37 ComplexVCBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod OOP 2961153]
38 ComplexVCBlock in FSConnection >> safeServe @11 line 12 [GsMethod OOP 105202177]
39 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod OOP 2383105]
40 ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod OOP 2383105]
41 FSConnection >> safeServe @14 line 15 [GsMethod OOP 105202177]
42 FSConnection >> serve @1 line 4 [GsMethod OOP 98188801]
43 ComplexBlock in FSSocketServer >> listen: @9 line 15 [GsMethod OOP 103703297]
44 GsProcess >> _startPart2 @13 line 17 [GsMethod OOP 2997761]
45 GsProcess >> _start @1 line 9 [GsMethod OOP 2998273]
-----------

best
MDC

Dale

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, June 8, 2011 3:47:48 PM
| Subject: [GS/SS Beta] was gems don't start
|
| folks i have followind error , received on the browser.
|
|
| InterpreterError 2258: Primitive failed , selector
| <#'_sessionCacheStatAt:'> receiver .
| any clue?
| best regards
| mdc
|

Dale Henrichs

Re: was gems don't start

In reply to this post by Juan-2

Juan,

Sorry for the delay, but I was on vacation part of last week and this week:)

If you are running with 2.4.4.4 executables (and you are), then you need to start with the extent0.seaside.dbf extent that is shipped with 2.4.4.4.

Apparently you are using an extent that was copied from a 2.3.1 appliance .... A lot of the code is very similar, but when it comes to primitives there could very easily be changes (especialy with _* methods) that result in unexpected problems....Alternatively, if you do a 2.3.1 install, you can safely use the 2.3.1 extent as a starting point ... if you go this route, you may want to look at James Foster's post[1] on converting an early GLASS-based system to use Metacello.

Dale

[1] http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Thursday, June 9, 2011 9:22:16 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
|
|
|
| On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email] >
| wrote:
|
|
| Juan,
|
| So it seems that you have the seaside gems started? Are you runnning
| Seaside2.8?
|
| yes i copied the extent running at appliance, i do:
|
| copydbf -i
|
| show me transaction file necesary for extent
| copy that files at data directory.
|
|
|
| There should be a stack dumped into the gem log ... the logs should
| be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| There should be 3 *fastcgi* logs to look at ...
|
| Ok tomorrow i check
|
| thanks a lot
|
| mdc
|
|
|
| Dale
|
|
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
| | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | Subject: [GS/SS Beta] was gems don't start
| |
| | folks i have followind error , received on the browser.
| |
| |
| | InterpreterError 2258: Primitive failed , selector
| | <#'_sessionCacheStatAt:'> receiver .
| | any clue?
| | best regards
| | mdc
| |
|
|

Juan-2

Re: was gems don't start

hi Dale

On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

Sorry for the delay, but I was on vacation part of last week and this week:)

haa ok .

If you are running with 2.4.4.4 executables (and you are), then you need to start with the extent0.seaside.dbf extent that is shipped with 2.4.4.4.

Apparently you are using an extent that was copied from a 2.3.1 appliance .... A lot of the code is very similar, but when it comes to primitives there could very easily be changes (especialy with _* methods) that result in unexpected problems....Alternatively, if you do a 2.3.1 install, you can safely use the 2.3.1 extent as a starting point ... if you go this route, you may want to look at James Foster's post[1] on converting an early GLASS-based system to use Metacello.

ok I'll try thanks , and i will let you know

best
mdc

Dale

[1] http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>

| Sent: Thursday, June 9, 2011 9:22:16 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
|
|
|
| On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email] >
| wrote:
|
|
| Juan,
|
| So it seems that you have the seaside gems started? Are you runnning
| Seaside2.8?
|
| yes i copied the extent running at appliance, i do:
|
| copydbf -i
|
| show me transaction file necesary for extent
| copy that files at data directory.
|
|
|
| There should be a stack dumped into the gem log ... the logs should
| be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| There should be 3 *fastcgi* logs to look at ...
|
| Ok tomorrow i check
|
| thanks a lot
|
| mdc
|
|
|
| Dale
|
|
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
| | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | Subject: [GS/SS Beta] was gems don't start
| |
| | folks i have followind error , received on the browser.
| |
| |
| | InterpreterError 2258: Primitive failed , selector
| | <#'_sessionCacheStatAt:'> receiver .
| | any clue?
| | best regards
| | mdc
| |
|
|

Juan-2

Re: was gems don't start

In reply to this post by Dale Henrichs

hi Dale

thanks for responses.
one question, with extent0.seaside.dbf extent, gemtools (pharo ) connect to glass?
tia

mdc

On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

Sorry for the delay, but I was on vacation part of last week and this week:)

If you are running with 2.4.4.4 executables (and you are), then you need to start with the extent0.seaside.dbf extent that is shipped with 2.4.4.4.

Apparently you are using an extent that was copied from a 2.3.1 appliance .... A lot of the code is very similar, but when it comes to primitives there could very easily be changes (especialy with _* methods) that result in unexpected problems....Alternatively, if you do a 2.3.1 install, you can safely use the 2.3.1 extent as a starting point ... if you go this route, you may want to look at James Foster's post[1] on converting an early GLASS-based system to use Metacello.

Dale

[1] http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>

| Sent: Thursday, June 9, 2011 9:22:16 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
|
|
|
| On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email] >
| wrote:
|
|
| Juan,
|
| So it seems that you have the seaside gems started? Are you runnning
| Seaside2.8?
|
| yes i copied the extent running at appliance, i do:
|
| copydbf -i
|
| show me transaction file necesary for extent
| copy that files at data directory.
|
|
|
| There should be a stack dumped into the gem log ... the logs should
| be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| There should be 3 *fastcgi* logs to look at ...
|
| Ok tomorrow i check
|
| thanks a lot
|
| mdc
|
|
|
| Dale
|
|
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
| | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | Subject: [GS/SS Beta] was gems don't start
| |
| | folks i have followind error , received on the browser.
| |
| |
| | InterpreterError 2258: Primitive failed , selector
| | <#'_sessionCacheStatAt:'> receiver .
| | any clue?
| | best regards
| | mdc
| |
|
|

Dale Henrichs

Re: was gems don't start

Juan,

With extent0.seaside.dbf, GemTools is operational ...

Dale

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, June 15, 2011 3:04:23 PM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| hi Dale
|
| thanks for responses.
| one question, with extent0.seaside.dbf extent, gemtools (pharo )
| connect to glass?
| tia
|
| mdc
|
|
| On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs < [hidden email]
| > wrote:
|
|
| Juan,
|
| Sorry for the delay, but I was on vacation part of last week and this
| week:)
|
| If you are running with 2.4.4.4 executables (and you are), then you
| need to start with the extent0.seaside.dbf extent that is shipped
| with 2.4.4.4.
|
| Apparently you are using an extent that was copied from a 2.3.1
| appliance .... A lot of the code is very similar, but when it comes
| to primitives there could very easily be changes (especialy with _*
| methods) that result in unexpected problems....Alternatively, if you
| do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| starting point ... if you go this route, you may want to look at
| James Foster's post[1] on converting an early GLASS-based system to
| use Metacello.
|
| Dale
|
| [1]
| http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
|
|
|
| | Sent: Thursday, June 9, 2011 9:22:16 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| |
| |
| |
| | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email]
| | >
| | wrote:
| |
| |
| | Juan,
| |
| | So it seems that you have the seaside gems started? Are you
| | runnning
| | Seaside2.8?
| |
| | yes i copied the extent running at appliance, i do:
| |
| | copydbf -i
| |
| | show me transaction file necesary for extent
| | copy that files at data directory.
| |
| |
| |
| | There should be a stack dumped into the gem log ... the logs should
| | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | There should be 3 *fastcgi* logs to look at ...
| |
| | Ok tomorrow i check
| |
| | thanks a lot
| |
| | mdc
| |
| |
| |
| | Dale
| |
| |
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | Subject: [GS/SS Beta] was gems don't start
| | |
| | | folks i have followind error , received on the browser.
| | |
| | |
| | | InterpreterError 2258: Primitive failed , selector
| | | <#'_sessionCacheStatAt:'> receiver .
| | | any clue?
| | | best regards
| | | mdc
| | |
| |
| |
|
|

Juan-2

Re: was gems don't start

In reply to this post by Dale Henrichs

Hi Dale

With extent0.seaside.dbf shipping on GemStone64Bit2.4.4.4-x86_64.Linux.zip
startstone fail. i don't know why.
the log:

--- 07/06/11 16:20:00 ART ---
_____________________________________________________________________________
|    Key file: /opt/gemstone/etc/gemstone.key                                |
| GemStone ID: Free 4GB GS/S Web Edition Beta                                |
| LICENSED TO: GemStone Seaside Community                                    |
| KEY ORIGIN: 0x500abefa (a Linux x86)                                      |
|   REPOS MAX: The maximum repository size is 4096 Mbytes.                   |
|_____________________________________________________________________________|
WARNING: Argument size is too small to represent FileNames. (4095 vs 2048)

========================================================================
    Now starting GemStone monitor.

_____________________________________________________________________________
|     SESSION CONFIGURATION: The maximum number of concurrent sessions is 41. |
|_____________________________________________________________________________|

    Attaching the Shared Cache using Stone name: seaside

--- 07/06/11 16:25:01 ART ---
The stone was unable to start a cache page server on host '<stone's host>'.
Reason: The cache monitor connect failed.
Monitor process (8751) did not start.

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.
(END)

tia
Best
mc

On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

Sorry for the delay, but I was on vacation part of last week and this week:)

If you are running with 2.4.4.4 executables (and you are), then you need to start with the extent0.seaside.dbf extent that is shipped with 2.4.4.4.

Apparently you are using an extent that was copied from a 2.3.1 appliance .... A lot of the code is very similar, but when it comes to primitives there could very easily be changes (especialy with _* methods) that result in unexpected problems....Alternatively, if you do a 2.3.1 install, you can safely use the 2.3.1 extent as a starting point ... if you go this route, you may want to look at James Foster's post[1] on converting an early GLASS-based system to use Metacello.

Dale

[1] http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/

----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>

| Sent: Thursday, June 9, 2011 9:22:16 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
|
|
|
| On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email] >
| wrote:
|
|
| Juan,
|
| So it seems that you have the seaside gems started? Are you runnning
| Seaside2.8?
|
| yes i copied the extent running at appliance, i do:
|
| copydbf -i
|
| show me transaction file necesary for extent
| copy that files at data directory.
|
|
|
| There should be a stack dumped into the gem log ... the logs should
| be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| There should be 3 *fastcgi* logs to look at ...
|
| Ok tomorrow i check
|
| thanks a lot
|
| mdc
|
|
|
| Dale
|
|
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
| | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | Subject: [GS/SS Beta] was gems don't start
| |
| | folks i have followind error , received on the browser.
| |
| |
| | InterpreterError 2258: Primitive failed , selector
| | <#'_sessionCacheStatAt:'> receiver .
| | any clue?
| | best regards
| | mdc
| |
|
|

Dale Henrichs

Re: was gems don't start

Juan,

There should be more detailed error information in the seaside*pcmon.log file.

Did you do either of the following:

check for stale files in /opt/gemstone/locks/<stonename>*?
use ipcs to check for stale shared memory resources ?

Dale
----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, July 6, 2011 11:54:52 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Hi Dale
|
| With extent0.seaside.dbf shipping on
| GemStone64Bit2.4.4.4-x86_64.Linux.zip
| startstone fail. i don't know why.
| the log:
|
| --- 07/06/11 16:20:00 ART ---
| _____________________________________________________________________________
| | Key file: /opt/gemstone/etc/gemstone.key |
| | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | LICENSED TO: GemStone Seaside Community |
| | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| |_____________________________________________________________________________|
| WARNING: Argument size is too small to represent FileNames. (4095 vs
| 2048)
|
| ========================================================================
| Now starting GemStone monitor.
|
| _____________________________________________________________________________
| | SESSION CONFIGURATION: The maximum number of concurrent sessions is
| | 41. |
| |_____________________________________________________________________________|
|
| Attaching the Shared Cache using Stone name: seaside
|
| --- 07/06/11 16:25:01 ART ---
| The stone was unable to start a cache page server on host '<stone's
| host>'.
| Reason: The cache monitor connect failed.
| Monitor process (8751) did not start.
|
|
| 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.
| (END)
|
| tia
| Best
| mc
|
|
| On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs < [hidden email]
| > wrote:
|
|
| Juan,
|
| Sorry for the delay, but I was on vacation part of last week and this
| week:)
|
| If you are running with 2.4.4.4 executables (and you are), then you
| need to start with the extent0.seaside.dbf extent that is shipped
| with 2.4.4.4.
|
| Apparently you are using an extent that was copied from a 2.3.1
| appliance .... A lot of the code is very similar, but when it comes
| to primitives there could very easily be changes (especialy with _*
| methods) that result in unexpected problems....Alternatively, if you
| do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| starting point ... if you go this route, you may want to look at
| James Foster's post[1] on converting an early GLASS-based system to
| use Metacello.
|
| Dale
|
| [1]
| http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
|
|
|
| | Sent: Thursday, June 9, 2011 9:22:16 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| |
| |
| |
| | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email]
| | >
| | wrote:
| |
| |
| | Juan,
| |
| | So it seems that you have the seaside gems started? Are you
| | runnning
| | Seaside2.8?
| |
| | yes i copied the extent running at appliance, i do:
| |
| | copydbf -i
| |
| | show me transaction file necesary for extent
| | copy that files at data directory.
| |
| |
| |
| | There should be a stack dumped into the gem log ... the logs should
| | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | There should be 3 *fastcgi* logs to look at ...
| |
| | Ok tomorrow i check
| |
| | thanks a lot
| |
| | mdc
| |
| |
| |
| | Dale
| |
| |
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | Subject: [GS/SS Beta] was gems don't start
| | |
| | | folks i have followind error , received on the browser.
| | |
| | |
| | | InterpreterError 2258: Primitive failed , selector
| | | <#'_sessionCacheStatAt:'> receiver .
| | | any clue?
| | | best regards
| | | mdc
| | |
| |
| |
|
|

Juan-2

Re: was gems don't start

Dale

Thanks for response.

On Wed, Jul 6, 2011 at 7:46 PM, Dale Henrichs <[hidden email]> wrote:

Juan,

There should be more detailed error information in the seaside*pcmon.log file.

Did you do either of the following:

check for stale files in /opt/gemstone/locks/<stonename>*?
use ipcs to check for stale shared memory resources ?

glass ~$ ipcs -a
------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
------ Semaphore Arrays --------
key        semid      owner      perms      nsems
------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages

the log

glass ~$ less /opt/gemstone/log/seaside_14532pcmon.log
_____________________________________________________________________________
|                             GemStone Child Task                             |
|                                                                             |
|    VERSION: 2.4.4.4, Thu Jan 27 14:16:02 2011                               |
|      BUILD: gss64_2_4_4_x_branch-25116                                      |
| BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 1-CPU glass x86_64 (Linux 2.6.36-gentoo-r8 #1 SMP Tue Mar 29 17:27:54
| Local time zone must be set--see zic ) 369MB                                |
| PROCESS ID: 14532     DATE: 07/06/11 17:18:24 ART                           |
|   USER IDS: REAL=glass (1000) EFFECTIVE=glass (1000)                        |
|   DATEFORMAT: %m/%d/%y %H:%M:%S                                             |
|    COMMAND: /opt/gemstone/product/sys/startshrpcmon [hidden email] 4687
| 49 0 1 585 1 1900                                                           |
|_____________________________________________________________________________|
SharedPageCache Monitor Summary:
   the hostname is:    glass
   GEMSTONE is:        "/opt/gemstone/product"
   shrpcmon arguments are:
      SharedPageCache Monitor name [hidden email].
      Number of pages               4687.
      Number of processes           49.
      Cache locked in memory        0.
      SpinLockCount                 1.
      TargetFreeFrameCount          585.
      Number of free frame servers 1.
      Number of shared counters     1900.
_____________________________________________________________________________
|             GemStone/S64 Object-Oriented Data Management System             |
|               Copyright (C) GemStone Systems, Inc. 1986-2011                |
|                            All rights reserved.                             |
+-----------------------------------------------------------------------------+
|    PROGRAM: SHRPCMON, GemStone SharedPageCache Monitor                      |
|    VERSION: 2.4.4.4, Thu Jan 27 14:16:02 2011                               |
|      BUILD: gss64_2_4_4_x_branch-25116                                      |
| BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 1-CPU glass x86_64 (Linux 2.6.36-gentoo-r8 #1 SMP Tue Mar 29 17:27:54
| Local time zone must be set--see zic ) 369MB                                |
| PROCESS ID: 14532     DATE: 07/06/11 17:18:26 ART                           |
|   USER IDS: REAL=glass (1000) EFFECTIVE=glass (1000)                        |
|   DATEFORMAT: %m/%d/%y %H:%M:%S                                             |
|_____________________________________________________________________________|
|   GemStone could not retrieve the IPC identifier associated with the memory |
|   key 1275271162. shmget() error = errno=22,EINVAL, Invalid argument (programmer
| error).                                                                     |
|                                                                             |
GemStone could not attach to the shared page cache.

any clue?
best
mdc

Dale
----- Original Message -----
| From: "Juan" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>

| Sent: Wednesday, July 6, 2011 11:54:52 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Hi Dale
|
| With extent0.seaside.dbf shipping on
| GemStone64Bit2.4.4.4-x86_64.Linux.zip
| startstone fail. i don't know why.
| the log:
|
| --- 07/06/11 16:20:00 ART ---
| _____________________________________________________________________________
| | Key file: /opt/gemstone/etc/gemstone.key |
| | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | LICENSED TO: GemStone Seaside Community |
| | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| |_____________________________________________________________________________|
| WARNING: Argument size is too small to represent FileNames. (4095 vs
| 2048)
|
| ========================================================================
| Now starting GemStone monitor.
|
| _____________________________________________________________________________
| | SESSION CONFIGURATION: The maximum number of concurrent sessions is
| | 41. |
| |_____________________________________________________________________________|
|
| Attaching the Shared Cache using Stone name: seaside
|
| --- 07/06/11 16:25:01 ART ---
| The stone was unable to start a cache page server on host '<stone's
| host>'.
| Reason: The cache monitor connect failed.
| Monitor process (8751) did not start.
|
|
| 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.
| (END)
|
| tia
| Best
| mc
|
|
| On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs < [hidden email]
| > wrote:
|
|
| Juan,
|
| Sorry for the delay, but I was on vacation part of last week and this
| week:)
|
| If you are running with 2.4.4.4 executables (and you are), then you
| need to start with the extent0.seaside.dbf extent that is shipped
| with 2.4.4.4.
|
| Apparently you are using an extent that was copied from a 2.3.1
| appliance .... A lot of the code is very similar, but when it comes
| to primitives there could very easily be changes (especialy with _*
| methods) that result in unexpected problems....Alternatively, if you
| do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| starting point ... if you go this route, you may want to look at
| James Foster's post[1] on converting an early GLASS-based system to
| use Metacello.
|
| Dale
|
| [1]
| http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
|
|
| ----- Original Message -----
| | From: "Juan" < [hidden email] >
| | To: "GemStone Seaside beta discussion" < [hidden email]
| | >
|
|
|
| | Sent: Thursday, June 9, 2011 9:22:16 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| |
| |
| |
| | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs < [hidden email]
| | >
| | wrote:
| |
| |
| | Juan,
| |
| | So it seems that you have the seaside gems started? Are you
| | runnning
| | Seaside2.8?
| |
| | yes i copied the extent running at appliance, i do:
| |
| | copydbf -i
| |
| | show me transaction file necesary for extent
| | copy that files at data directory.
| |
| |
| |
| | There should be a stack dumped into the gem log ... the logs should
| | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | There should be 3 *fastcgi* logs to look at ...
| |
| | Ok tomorrow i check
| |
| | thanks a lot
| |
| | mdc
| |
| |
| |
| | Dale
| |
| |
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | Subject: [GS/SS Beta] was gems don't start
| | |
| | | folks i have followind error , received on the browser.
| | |
| | |
| | | InterpreterError 2258: Primitive failed , selector
| | | <#'_sessionCacheStatAt:'> receiver .
| | | any clue?
| | | best regards
| | | mdc
| | |
| |
| |
|
|

Juan-2

Re: was gems don't start

Dale

seaside now start but topaz gems doesn't

the log.

_____________________________________________________________________________
|                             Configuration Files                             |
|                                                                             |
| System File: $GEMSTONE/data/system.conf                                     |
| Warning: File not found (errno=2,ENOENT, The file or directory specified cannot
| be found)                                                                   |
|           using defaults.                                                   |
|                                                                             |
| Executable File: /tmp/gem.conf                                              |
| Warning: File not found (errno=2,ENOENT, The file or directory specified cannot
| be found)                                                                   |
|           using defaults.                                                   |
|_____________________________________________________________________________|
Using GEM_TEMPOBJ_CACHE_SIZE 50000 from -T command line option
_____________________________________________________________________________
|               Gem Configuration Options for process id 17000                |
|_____________________________________________________________________________|

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;
GEM_TEMPOBJ_POMGEN_SCAVENGE_INTERVAL = 1800;
LOG_WARNINGS = TRUE;
SHR_NUM_FREE_FRAME_SERVERS = 1;
SHR_PAGE_CACHE_NUM_SHARED_COUNTERS = 1900;
SHR_PAGE_CACHE_SIZE_KB = 75000;
SHR_PAGE_CACHE_NUM_PROCS = 1017;
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 )
_____________________________________________________________________________
|             GemStone/S64 Object-Oriented Data Management System             |
|               Copyright (C) GemStone Systems, Inc. 1986-2011                |
|                            All rights reserved.                             |
|     covered by Patent Number 6,567,905 Generational Garbage Collector.      |
+-----------------------------------------------------------------------------+
|    PROGRAM: topaz, Linear GemStone Interface (Linked Session)               |
|    VERSION: 2.4.4.4, Thu Jan 27 14:16:02 2011                               |
|      BUILD: gss64_2_4_4_x_branch-25116                                      |
| BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 2-CPU glass x86_64 (Linux 2.6.36-gentoo-r8 #1 SMP Tue Mar 29 17:27:54
| Local time zone must be set--see zic ) 495MB                                |
| PROCESS ID: 17000     DATE: 07/07/11 14:33:32 ART                           |
|   USER IDS: REAL=glass (1000) EFFECTIVE=glass (1000)                        |
|   DATEFORMAT: %m/%d/%y %H:%M:%S                                             |
|_____________________________________________________________________________|
[Info]: LNK client/gem GCI levels = 844/844
[07/07/11 14:33:32.991 ART] gci login: currSession 1 rpc gem processId -1
topaz 1> Warning: GemStone is clearing the previous GemStone password.
topaz 1> topaz 1> topaz 1> topaz 1> topaz 1> -----------------------------------------------------
GemStone: Error         Nonfatal
The current GCI session is already logged in.
Error Category: 231169 [GemStone] Number: 2147 Arg Count: 0 Context : 20

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> topaz 1> GemStone Smalltalk Compiler Errors:
   "record gems pid in the pid file"
   | file |
   (GsFile isServerDirectory: '/opt/gemstone/product/seaside/data') ifFalse: [ ^nil ].
   file := GsFile openWriteOnServer: '/opt/gemstone/product/seaside/data/FastCGI_server-9001.pid'.
   file nextPutAll: (System gemVersionReport at: 'processId') printString.
   file cr.
   file close.
   (ObjectLogEntry
* ^1                                                                *******
     info: 'FastCGI: startup'
     object:
       'pid: ', (System gemVersionReport at: 'processId') printString, ' ',
       'port: ', 9001 printString) addToLog.
   System commitTransaction
       ifFalse: [
         System abortTransaction.
         nil error: 'Could not commit ObjectLog entry' ].

1: [1031] undefined symbol

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> topaz 1> GemStone Smalltalk Compiler Errors:
   true "enable for remote breakpoints and profiling"
     ifTrue: [
       GemToGemAnnouncement installStaticHandler.
*     ^1                                                             *******
       Exception
         installStaticException:
           [:ex :cat :num :args |
             BreakpointNotification signal.
*           ^2                                                       *******
             "needed to avoid infinite loop when resuming from a breakpoint"
             ex _incrementBreakpointsToIgnore. ]
         category: GemStoneError
         number: 6005
         subtype: nil.
      System commitTransaction ifFalse: [ nil error: 'Could not commit for GemToGemSignaling' ]].

   System transactionMode: #manualBegin.

   Exception
     installStaticException:
       [:ex :cat :num :args |
         "Run the abort in a lowPriority process, since we must acquire the
          transactionMutex."
         [
           SeasidePlatformSupport transactionMutex
*         ^3                                                         *******
             critical: [
               SeasidePlatformSupport doAbortTransaction ].
           System enableSignaledAbortError.
         ] forkAt: Processor lowestPriority.
       ]
     category: GemStoneError
     number: 6009
     subtype: nil.
   System enableSignaledAbortError.
   "This thread is needed to handle the SigAbort exception, when the primary
    thread is blocked on an accept. Assuming default 60 second
    STN_GEM_ABORT_TIMEOUT, wake up at 30 second intervals."
   [
     [ true ] whileTrue: [ (Delay forSeconds: 30) wait ].
   ] forkAt: Processor lowestPriority.

   GsFile gciLogServer: 'FastCGI Server started on port ', 9001 printString.

   FSSeasideHandler startUp: 9001.
* ^4                                                                 *******
   "does not return"

1: [1031] undefined symbol
2: [1031] undefined symbol
3: [1031] undefined symbol
4: [1031] undefined symbol

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> GemStone Smalltalk Compiler Errors:
   GemToGemAnnouncement uninstallStaticHandler.
* ^1                                                                 *******
   System beginTransaction.
   (ObjectLogEntry
* ^2                                                                *******
     fatal: 'FastCGI: topaz exit'
     object:
       'port: ', 9001 printString, ' ',
       'pid: ', (System gemVersionReport at: 'processId') printString) addToLog.
   System commitTransaction.

1: [1031] undefined symbol
2: [1031] undefined symbol

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1>
[Info]: Logging out at 07/07/11 14:33:32 ART

best regards
mdc

pd: I have the feeling that it lacks little to work well

Dale Henrichs

Re: was gems don't start

In reply to this post by Dale Henrichs

Juan,

I can send mail, but not receive mail...

>From your most recent mail, I see that you have got the stone started.

The fact that the ObjectLogEntry class is missing makes me think that you are starting the stone with the wrong extent. Actually, looking at the oput put from the topaz it appears that you are starting the stone in $GEMSTONE/data which is not the usual location ... I would expect you to be using $GEMSTONE/seaside/data .... most of the instructions that I have been giving you (and those on the glassdb site) assume that you are using $GEMSTONE/seaside/defSeaside to set up your GemStone environment and then using startGemstone and stopGemstone to start and stop the stone ...

Take a look at these instructions[1] for information about using defSeaside...

Dale

[1] http://seaside.gemstone.com/userguide.html#starting-gemstone

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, July 6, 2011 3:46:12 PM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Juan,
|
| There should be more detailed error information in the
| seaside*pcmon.log file.
|
| Did you do either of the following:
|
| check for stale files in /opt/gemstone/locks/<stonename>*?
| use ipcs to check for stale shared memory resources ?
|
| Dale
| ----- Original Message -----
| | From: "Juan" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Wednesday, July 6, 2011 11:54:52 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| | Hi Dale
| |
| | With extent0.seaside.dbf shipping on
| | GemStone64Bit2.4.4.4-x86_64.Linux.zip
| | startstone fail. i don't know why.
| | the log:
| |
| | --- 07/06/11 16:20:00 ART ---
| | _____________________________________________________________________________
| | | Key file: /opt/gemstone/etc/gemstone.key |
| | | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | | LICENSED TO: GemStone Seaside Community |
| | | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| | |_____________________________________________________________________________|
| | WARNING: Argument size is too small to represent FileNames. (4095
| | vs
| | 2048)
| |
| | ========================================================================
| | Now starting GemStone monitor.
| |
| | _____________________________________________________________________________
| | | SESSION CONFIGURATION: The maximum number of concurrent sessions
| | | is
| | | 41. |
| | |_____________________________________________________________________________|
| |
| | Attaching the Shared Cache using Stone name: seaside
| |
| | --- 07/06/11 16:25:01 ART ---
| | The stone was unable to start a cache page server on host '<stone's
| | host>'.
| | Reason: The cache monitor connect failed.
| | Monitor process (8751) did not start.
| |
| |
| | 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.
| | (END)
| |
| | tia
| | Best
| | mc
| |
| |
| | On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <
| | [hidden email]
| | > wrote:
| |
| |
| | Juan,
| |
| | Sorry for the delay, but I was on vacation part of last week and
| | this
| | week:)
| |
| | If you are running with 2.4.4.4 executables (and you are), then you
| | need to start with the extent0.seaside.dbf extent that is shipped
| | with 2.4.4.4.
| |
| | Apparently you are using an extent that was copied from a 2.3.1
| | appliance .... A lot of the code is very similar, but when it comes
| | to primitives there could very easily be changes (especialy with _*
| | methods) that result in unexpected problems....Alternatively, if
| | you
| | do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| | starting point ... if you go this route, you may want to look at
| | James Foster's post[1] on converting an early GLASS-based system to
| | use Metacello.
| |
| | Dale
| |
| | [1]
| | http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| |
| |
| |
| | | Sent: Thursday, June 9, 2011 9:22:16 AM
| | | Subject: Re: [GS/SS Beta] was gems don't start
| | |
| | |
| | |
| | |
| | | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <
| | | [hidden email]
| | | >
| | | wrote:
| | |
| | |
| | | Juan,
| | |
| | | So it seems that you have the seaside gems started? Are you
| | | runnning
| | | Seaside2.8?
| | |
| | | yes i copied the extent running at appliance, i do:
| | |
| | | copydbf -i
| | |
| | | show me transaction file necesary for extent
| | | copy that files at data directory.
| | |
| | |
| | |
| | | There should be a stack dumped into the gem log ... the logs
| | | should
| | | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | | There should be 3 *fastcgi* logs to look at ...
| | |
| | | Ok tomorrow i check
| | |
| | | thanks a lot
| | |
| | | mdc
| | |
| | |
| | |
| | | Dale
| | |
| | |
| | |
| | |
| | | ----- Original Message -----
| | | | From: "Juan" < [hidden email] >
| | | | To: "GemStone Seaside beta discussion" <
| | | | [hidden email]
| | | | >
| | | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | | Subject: [GS/SS Beta] was gems don't start
| | | |
| | | | folks i have followind error , received on the browser.
| | | |
| | | |
| | | | InterpreterError 2258: Primitive failed , selector
| | | | <#'_sessionCacheStatAt:'> receiver .
| | | | any clue?
| | | | best regards
| | | | mdc
| | | |
| | |
| | |
| |
| |
|

Dale Henrichs

Re: was gems don't start

In reply to this post by Dale Henrichs

Dale Henrichs

Re: was gems don't start

In reply to this post by Dale Henrichs

Dale Henrichs

Re: was gems don't start

In reply to this post by Dale Henrichs

Juan-2

Re: was gems don't start

Dale

i'm using the extent inside the 2.4.4.4 zip file .
Now i have maintenance Gem working, the others gems fail to start because erros in the topaz scipt, class not defined and so.
i'm using the extent.seaside.dbf ,how you vice to me use.
i'm doing progress with that extent .
this extent allow to me run some scripts ,for upgrade image , there some error
but i think how to do work ' i tell you soon.
another idea?
best
mdc

On Fri, Jul 8, 2011 at 12:52 AM, Dale Henrichs <[hidden email]> wrote:

Juan,

I can send mail, but not receive mail...

>From your most recent mail, I see that you have got the stone started.

The fact that the ObjectLogEntry class is missing makes me think that you are starting the stone with the wrong extent. Actually, looking at the oput put from the topaz it appears that you are starting the stone in $GEMSTONE/data which is not the usual location ... I would expect you to be using $GEMSTONE/seaside/data .... most of the instructions that I have been giving you (and those on the glassdb site) assume that you are using $GEMSTONE/seaside/defSeaside to set up your GemStone environment and then using startGemstone and stopGemstone to start and stop the stone ...

Take a look at these instructions[1] for information about using defSeaside...

Dale

[1] http://seaside.gemstone.com/userguide.html#starting-gemstone

----- Original Message -----

| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>

| Sent: Wednesday, July 6, 2011 3:46:12 PM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Juan,
|
| There should be more detailed error information in the
| seaside*pcmon.log file.
|
| Did you do either of the following:
|
| check for stale files in /opt/gemstone/locks/<stonename>*?
| use ipcs to check for stale shared memory resources ?
|
| Dale
| ----- Original Message -----
| | From: "Juan" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Wednesday, July 6, 2011 11:54:52 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| | Hi Dale
| |
| | With extent0.seaside.dbf shipping on
| | GemStone64Bit2.4.4.4-x86_64.Linux.zip
| | startstone fail. i don't know why.
| | the log:
| |
| | --- 07/06/11 16:20:00 ART ---
| | _____________________________________________________________________________
| | | Key file: /opt/gemstone/etc/gemstone.key |
| | | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | | LICENSED TO: GemStone Seaside Community |
| | | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| | |_____________________________________________________________________________|
| | WARNING: Argument size is too small to represent FileNames. (4095
| | vs
| | 2048)
| |
| | ========================================================================
| | Now starting GemStone monitor.
| |
| | _____________________________________________________________________________
| | | SESSION CONFIGURATION: The maximum number of concurrent sessions
| | | is
| | | 41. |
| | |_____________________________________________________________________________|
| |
| | Attaching the Shared Cache using Stone name: seaside
| |
| | --- 07/06/11 16:25:01 ART ---
| | The stone was unable to start a cache page server on host '<stone's
| | host>'.
| | Reason: The cache monitor connect failed.
| | Monitor process (8751) did not start.
| |
| |
| | 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.
| | (END)
| |
| | tia
| | Best
| | mc
| |
| |
| | On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <
| | [hidden email]
| | > wrote:
| |
| |
| | Juan,
| |
| | Sorry for the delay, but I was on vacation part of last week and
| | this
| | week:)
| |
| | If you are running with 2.4.4.4 executables (and you are), then you
| | need to start with the extent0.seaside.dbf extent that is shipped
| | with 2.4.4.4.
| |
| | Apparently you are using an extent that was copied from a 2.3.1
| | appliance .... A lot of the code is very similar, but when it comes
| | to primitives there could very easily be changes (especialy with _*
| | methods) that result in unexpected problems....Alternatively, if
| | you
| | do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| | starting point ... if you go this route, you may want to look at
| | James Foster's post[1] on converting an early GLASS-based system to
| | use Metacello.
| |
| | Dale
| |
| | [1]
| | http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| |
| |
| |
| | | Sent: Thursday, June 9, 2011 9:22:16 AM
| | | Subject: Re: [GS/SS Beta] was gems don't start
| | |
| | |
| | |
| | |
| | | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <
| | | [hidden email]
| | | >
| | | wrote:
| | |
| | |
| | | Juan,
| | |
| | | So it seems that you have the seaside gems started? Are you
| | | runnning
| | | Seaside2.8?
| | |
| | | yes i copied the extent running at appliance, i do:
| | |
| | | copydbf -i
| | |
| | | show me transaction file necesary for extent
| | | copy that files at data directory.
| | |
| | |
| | |
| | | There should be a stack dumped into the gem log ... the logs
| | | should
| | | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | | There should be 3 *fastcgi* logs to look at ...
| | |
| | | Ok tomorrow i check
| | |
| | | thanks a lot
| | |
| | | mdc
| | |
| | |
| | |
| | | Dale
| | |
| | |
| | |
| | |
| | | ----- Original Message -----
| | | | From: "Juan" < [hidden email] >
| | | | To: "GemStone Seaside beta discussion" <
| | | | [hidden email]
| | | | >
| | | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | | Subject: [GS/SS Beta] was gems don't start
| | | |
| | | | folks i have followind error , received on the browser.
| | | |
| | | |
| | | | InterpreterError 2258: Primitive failed , selector
| | | | <#'_sessionCacheStatAt:'> receiver .
| | | | any clue?
| | | | best regards
| | | | mdc
| | | |
| | |
| | |
| |
| |
|

Dale Henrichs

Re: was gems don't start

In reply to this post by Dale Henrichs

Juan,

I can finally send and receive mail...

>From your most recent mail, I see that you have got the stone started.

The fact that the ObjectLogEntry class is missing makes me think that you are starting the stone with the wrong extent. Actually, looking at the oput put from the topaz it appears that you are starting the stone in $GEMSTONE/data which is not the usual location ... I would expect you to be using $GEMSTONE/seaside/data .... most of the instructions that I have been giving you (and those on the glassdb site) assume that you are using $GEMSTONE/seaside/defSeaside to set up your GemStone environment and then using startGemstone and stopGemstone to start and stop the stone ...

Take a look at these instructions[1] for information about using defSeaside...

Dale

[1] http://seaside.gemstone.com/userguide.html#starting-gemstone

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Wednesday, July 6, 2011 3:46:12 PM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Juan,
|
| There should be more detailed error information in the
| seaside*pcmon.log file.
|
| Did you do either of the following:
|
| check for stale files in /opt/gemstone/locks/<stonename>*?
| use ipcs to check for stale shared memory resources ?
|
| Dale
| ----- Original Message -----
| | From: "Juan" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Wednesday, July 6, 2011 11:54:52 AM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| | Hi Dale
| |
| | With extent0.seaside.dbf shipping on
| | GemStone64Bit2.4.4.4-x86_64.Linux.zip
| | startstone fail. i don't know why.
| | the log:
| |
| | --- 07/06/11 16:20:00 ART ---
| | _____________________________________________________________________________
| | | Key file: /opt/gemstone/etc/gemstone.key |
| | | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | | LICENSED TO: GemStone Seaside Community |
| | | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| | |_____________________________________________________________________________|
| | WARNING: Argument size is too small to represent FileNames. (4095
| | vs
| | 2048)
| |
| | ========================================================================
| | Now starting GemStone monitor.
| |
| | _____________________________________________________________________________
| | | SESSION CONFIGURATION: The maximum number of concurrent sessions
| | | is
| | | 41. |
| | |_____________________________________________________________________________|
| |
| | Attaching the Shared Cache using Stone name: seaside
| |
| | --- 07/06/11 16:25:01 ART ---
| | The stone was unable to start a cache page server on host '<stone's
| | host>'.
| | Reason: The cache monitor connect failed.
| | Monitor process (8751) did not start.
| |
| |
| | 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.
| | (END)
| |
| | tia
| | Best
| | mc
| |
| |
| | On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <
| | [hidden email]
| | > wrote:
| |
| |
| | Juan,
| |
| | Sorry for the delay, but I was on vacation part of last week and
| | this
| | week:)
| |
| | If you are running with 2.4.4.4 executables (and you are), then you
| | need to start with the extent0.seaside.dbf extent that is shipped
| | with 2.4.4.4.
| |
| | Apparently you are using an extent that was copied from a 2.3.1
| | appliance .... A lot of the code is very similar, but when it comes
| | to primitives there could very easily be changes (especialy with _*
| | methods) that result in unexpected problems....Alternatively, if
| | you
| | do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| | starting point ... if you go this route, you may want to look at
| | James Foster's post[1] on converting an early GLASS-based system to
| | use Metacello.
| |
| | Dale
| |
| | [1]
| | http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
| |
| |
| | ----- Original Message -----
| | | From: "Juan" < [hidden email] >
| | | To: "GemStone Seaside beta discussion" <
| | | [hidden email]
| | | >
| |
| |
| |
| | | Sent: Thursday, June 9, 2011 9:22:16 AM
| | | Subject: Re: [GS/SS Beta] was gems don't start
| | |
| | |
| | |
| | |
| | | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <
| | | [hidden email]
| | | >
| | | wrote:
| | |
| | |
| | | Juan,
| | |
| | | So it seems that you have the seaside gems started? Are you
| | | runnning
| | | Seaside2.8?
| | |
| | | yes i copied the extent running at appliance, i do:
| | |
| | | copydbf -i
| | |
| | | show me transaction file necesary for extent
| | | copy that files at data directory.
| | |
| | |
| | |
| | | There should be a stack dumped into the gem log ... the logs
| | | should
| | | be present in /op/gemstone/log (or is it /opt/gemstone/logs?)...
| | | There should be 3 *fastcgi* logs to look at ...
| | |
| | | Ok tomorrow i check
| | |
| | | thanks a lot
| | |
| | | mdc
| | |
| | |
| | |
| | | Dale
| | |
| | |
| | |
| | |
| | | ----- Original Message -----
| | | | From: "Juan" < [hidden email] >
| | | | To: "GemStone Seaside beta discussion" <
| | | | [hidden email]
| | | | >
| | | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | | Subject: [GS/SS Beta] was gems don't start
| | | |
| | | | folks i have followind error , received on the browser.
| | | |
| | | |
| | | | InterpreterError 2258: Primitive failed , selector
| | | | <#'_sessionCacheStatAt:'> receiver .
| | | | any clue?
| | | | best regards
| | | | mdc
| | | |
| | |
| | |
| |
| |
|

Dale Henrichs

Re: was gems don't start

Sorry for the spam ... apparently the mail was sent every time I pressed the send button, even though the server gave me an error and never acknowledged the send :(

Dale

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Friday, July 8, 2011 8:40:11 AM
| Subject: Re: [GS/SS Beta] was gems don't start
|
| Juan,
|
| I can finally send and receive mail...
|
| >From your most recent mail, I see that you have got the stone
| >started.
|
|
| The fact that the ObjectLogEntry class is missing makes me think that
| you are starting the stone with the wrong extent. Actually, looking
| at the oput put from the topaz it appears that you are starting the
| stone in $GEMSTONE/data which is not the usual location ... I would
| expect you to be using $GEMSTONE/seaside/data .... most of the
| instructions that I have been giving you (and those on the glassdb
| site) assume that you are using $GEMSTONE/seaside/defSeaside to set
| up your GemStone environment and then using startGemstone and
| stopGemstone to start and stop the stone ...
|
| Take a look at these instructions[1] for information about using
| defSeaside...
|
| Dale
|
| [1] http://seaside.gemstone.com/userguide.html#starting-gemstone
|
| ----- Original Message -----
| | From: "Dale Henrichs" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Wednesday, July 6, 2011 3:46:12 PM
| | Subject: Re: [GS/SS Beta] was gems don't start
| |
| | Juan,
| |
| | There should be more detailed error information in the
| | seaside*pcmon.log file.
| |
| | Did you do either of the following:
| |
| | check for stale files in /opt/gemstone/locks/<stonename>*?
| | use ipcs to check for stale shared memory resources ?
| |
| | Dale
| | ----- Original Message -----
| | | From: "Juan" <[hidden email]>
| | | To: "GemStone Seaside beta discussion"
| | | <[hidden email]>
| | | Sent: Wednesday, July 6, 2011 11:54:52 AM
| | | Subject: Re: [GS/SS Beta] was gems don't start
| | |
| | | Hi Dale
| | |
| | | With extent0.seaside.dbf shipping on
| | | GemStone64Bit2.4.4.4-x86_64.Linux.zip
| | | startstone fail. i don't know why.
| | | the log:
| | |
| | | --- 07/06/11 16:20:00 ART ---
| | | _____________________________________________________________________________
| | | | Key file: /opt/gemstone/etc/gemstone.key |
| | | | GemStone ID: Free 4GB GS/S Web Edition Beta |
| | | | LICENSED TO: GemStone Seaside Community |
| | | | KEY ORIGIN: 0x500abefa (a Linux x86) |
| | | | REPOS MAX: The maximum repository size is 4096 Mbytes. |
| | | |_____________________________________________________________________________|
| | | WARNING: Argument size is too small to represent FileNames. (4095
| | | vs
| | | 2048)
| | |
| | | ========================================================================
| | | Now starting GemStone monitor.
| | |
| | | _____________________________________________________________________________
| | | | SESSION CONFIGURATION: The maximum number of concurrent
| | | | sessions
| | | | is
| | | | 41. |
| | | |_____________________________________________________________________________|
| | |
| | | Attaching the Shared Cache using Stone name: seaside
| | |
| | | --- 07/06/11 16:25:01 ART ---
| | | The stone was unable to start a cache page server on host
| | | '<stone's
| | | host>'.
| | | Reason: The cache monitor connect failed.
| | | Monitor process (8751) did not start.
| | |
| | |
| | | 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.
| | | (END)
| | |
| | | tia
| | | Best
| | | mc
| | |
| | |
| | | On Wed, Jun 15, 2011 at 1:56 PM, Dale Henrichs <
| | | [hidden email]
| | | > wrote:
| | |
| | |
| | | Juan,
| | |
| | | Sorry for the delay, but I was on vacation part of last week and
| | | this
| | | week:)
| | |
| | | If you are running with 2.4.4.4 executables (and you are), then
| | | you
| | | need to start with the extent0.seaside.dbf extent that is shipped
| | | with 2.4.4.4.
| | |
| | | Apparently you are using an extent that was copied from a 2.3.1
| | | appliance .... A lot of the code is very similar, but when it
| | | comes
| | | to primitives there could very easily be changes (especialy with
| | | _*
| | | methods) that result in unexpected problems....Alternatively, if
| | | you
| | | do a 2.3.1 install, you can safely use the 2.3.1 extent as a
| | | starting point ... if you go this route, you may want to look at
| | | James Foster's post[1] on converting an early GLASS-based system
| | | to
| | | use Metacello.
| | |
| | | Dale
| | |
| | | [1]
| | | http://programminggems.wordpress.com/2011/01/02/migrating-to-metacello-based-seaside-2-8/
| | |
| | |
| | | ----- Original Message -----
| | | | From: "Juan" < [hidden email] >
| | | | To: "GemStone Seaside beta discussion" <
| | | | [hidden email]
| | | | >
| | |
| | |
| | |
| | | | Sent: Thursday, June 9, 2011 9:22:16 AM
| | | | Subject: Re: [GS/SS Beta] was gems don't start
| | | |
| | | |
| | | |
| | | |
| | | | On Wed, Jun 8, 2011 at 8:33 PM, Dale Henrichs <
| | | | [hidden email]
| | | | >
| | | | wrote:
| | | |
| | | |
| | | | Juan,
| | | |
| | | | So it seems that you have the seaside gems started? Are you
| | | | runnning
| | | | Seaside2.8?
| | | |
| | | | yes i copied the extent running at appliance, i do:
| | | |
| | | | copydbf -i
| | | |
| | | | show me transaction file necesary for extent
| | | | copy that files at data directory.
| | | |
| | | |
| | | |
| | | | There should be a stack dumped into the gem log ... the logs
| | | | should
| | | | be present in /op/gemstone/log (or is it
| | | | /opt/gemstone/logs?)...
| | | | There should be 3 *fastcgi* logs to look at ...
| | | |
| | | | Ok tomorrow i check
| | | |
| | | | thanks a lot
| | | |
| | | | mdc
| | | |
| | | |
| | | |
| | | | Dale
| | | |
| | | |
| | | |
| | | |
| | | | ----- Original Message -----
| | | | | From: "Juan" < [hidden email] >
| | | | | To: "GemStone Seaside beta discussion" <
| | | | | [hidden email]
| | | | | >
| | | | | Sent: Wednesday, June 8, 2011 3:47:48 PM
| | | | | Subject: [GS/SS Beta] was gems don't start
| | | | |
| | | | | folks i have followind error , received on the browser.
| | | | |
| | | | |
| | | | | InterpreterError 2258: Primitive failed , selector
| | | | | <#'_sessionCacheStatAt:'> receiver .
| | | | | any clue?
| | | | | best regards
| | | | | mdc
| | | | |
| | | |
| | | |
| | |
| | |
| |
|