web request on GLASS

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

web request on GLASS

dario trussardi
500 - Internal Server Error Hi,

into GLASS work on Gemstone/S 64 2.4.4.2 i load:


Gofer project load: 'Seaside30' group: 'Development'.

Gofer project load: 'Magritte2' group: 'Magritte-Seaside'.


Gofer project load: 'Seaside30' group: 'Seaside-Adaptors-FastCGI'.




And run :

WAGemStoneRunSeasideGems default
        name: 'FastCGI';
        adaptorClass
: WAFastCGIAdaptor;
        ports
: #(9020 9021 9022).


On the server i load lighttpd with this entry:


## Gestione indirizzamento selection $HTTP["url"] =~ "^/Welcome/" { server.document-root = "/mnt/dtrvarie/" } else $HTTP["url"]=~ "^/welcome" { fastcgi.server = ( "/welcome" => ( ("host" => "192.168.1.100","port" => 9020,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9021,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9022,"check-local" => "disable","mode" => "responder" ), ), ) }
 
.........................
.........................
.....
else $HTTP["url"]=~ "^/seaside" { fastcgi.server = ( "/seaside" => ( ("host" => "192.168.1.100","port" => 9020,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9021,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9022,"check-local" => "disable","mode" => "responder" ), ), ) }



NOW when submit request : 


the browser answer:

503 - Service Not Available      or      500 - Internal Server Error

I think the lighttpd server work fine, but i d'ont have idea about this error.

Thanks for any consideration.


Dario
Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

Dale Henrichs
If I'm not mistaken, the 500 errors are thrown by lighttpd servers when
they can't find anyone listening on the fastcgi ports ...

The expression that you ran, simply defines the configuration for the
seaside gems. you also need to start the gems (that may not be clear:).

Use either the Admin>>Seaside gems>>restart or:

   WAGemStoneRunSeasideGems restartGems.

to launch the gems.

Dale

Dario Trussardi wrote:

> Hi,
>
> into GLASS work on Gemstone/S 64 2.4.4.2 i load:
>
>
> Gofer project load: 'Seaside30' group: 'Development'.
>
>
> Gofer project load: 'Magritte2' group: 'Magritte-Seaside'.
>
>
> Gofer project load: 'Seaside30' group: 'Seaside-Adaptors-FastCGI'.
>
>
>
>
> And run :
>
> WAGemStoneRunSeasideGems default
>
>         name: 'FastCGI';
>         adaptorClass: WAFastCGIAdaptor;
>         ports: #(9020 9021 9022).
>
>
> On the server i load lighttpd with this entry:
>
>
> ## Gestione indirizzamento selection $HTTP["url"] =~ "^/Welcome/" { server.document-root = "/mnt/dtrvarie/" } else $HTTP["url"]=~ "^/welcome" { fastcgi.server = ( "/welcome" => ( ("host" => "192.168.1.100","port" => 9020,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9021,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9022,"check-local" => "disable","mode" => "responder" ), ), ) }
>
> .........................
> .........................
> .....
> else $HTTP["url"]=~ "^/seaside" { fastcgi.server = ( "/seaside" => ( ("host" => "192.168.1.100","port" => 9020,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9021,"check-local" => "disable","mode" => "responder" ), ("host" => "192.168.1.100","port" => 9022,"check-local" => "disable","mode" => "responder" ), ), ) }
>
>
>
> NOW when submit request :
>
> http://www.tobehungry.com/seaside or http://www.tobehungry.com/welcome
>
> the browser answer:
>
> 503 - Service Not Available      or      500 - Internal Server Error
>
> I think the lighttpd server work fine, but i d'ont have idea about this error.
>
> Thanks for any consideration.
>
>
> Dario
>

Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

dario trussardi

Dale,

        i,m setting some stone environment and i think do error .......

> If I'm not mistaken, the 500 errors are thrown by lighttpd servers when they can't find anyone listening on the fastcgi ports ...
>
> The expression that you ran, simply defines the configuration for the seaside gems. you also need to start the gems (that may not be clear:).
>
> Use either the Admin>>Seaside gems>>restart or:
>
>  WAGemStoneRunSeasideGems restartGems.

When do Admin>>Seaside gems>>start
          the Transcript report :

                Starting Gems....
                Starting FastCGI gem on port 9020
                Starting FastCGI gem on port 9021
                Starting FastCGI gem on port 9022
                Starting maintenance gem

But i,m not safe about it.

If after i do the Admin>>Seaside gems>>stop

        the Transcript report:

        ---Stopping Seaside gems (19 July 2010 11:28:02 pm)
        Stopping Gems...
   Stopping FastCGI topaz PID 4010 running on port 9020
        /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4010) - Nessun processo
   Stopping FastCGI topaz PID 4008 running on port 9021
        /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4008) - Nessun processo
   Stopping FastCGI topaz PID 4006 running on port 9022
        /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4006) - Nessun processo
   Stopping maintenance gem PID 4004
        /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 55: kill: (4004) - Nessun processo

        ---Finished stopping Seaside gems (19 July 2010 11:28:04 pm)

How i can understand if the gems start fine, are running ?

Thanks,

        Dario


Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

Dale Henrichs
Dario,

This is where something like DaemonTools comes into play
(http://code.google.com/p/glassdb/wiki/GLASSDaemonTools). I can't rely
on daemonTools being installed on the various machines, so I publish the
runSeasideGems script that gets the job done in a primitive, but
relatively portable way.

In development you hit your web-site and if you get an error you check
your log files for errors.

Dale

Dario Trussardi wrote:

> Dale,
>
> i,m setting some stone environment and i think do error .......
>
>> If I'm not mistaken, the 500 errors are thrown by lighttpd servers when they can't find anyone listening on the fastcgi ports ...
>>
>> The expression that you ran, simply defines the configuration for the seaside gems. you also need to start the gems (that may not be clear:).
>>
>> Use either the Admin>>Seaside gems>>restart or:
>>
>>  WAGemStoneRunSeasideGems restartGems.
>
> When do Admin>>Seaside gems>>start
>  the Transcript report :
>
> Starting Gems....
> Starting FastCGI gem on port 9020
> Starting FastCGI gem on port 9021
> Starting FastCGI gem on port 9022
> Starting maintenance gem
>
> But i,m not safe about it.
>
> If after i do the Admin>>Seaside gems>>stop
>
> the Transcript report:
>
> ---Stopping Seaside gems (19 July 2010 11:28:02 pm)
> Stopping Gems...
>    Stopping FastCGI topaz PID 4010 running on port 9020
> /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4010) - Nessun processo
>    Stopping FastCGI topaz PID 4008 running on port 9021
> /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4008) - Nessun processo
>    Stopping FastCGI topaz PID 4006 running on port 9022
> /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 42: kill: (4006) - Nessun processo
>    Stopping maintenance gem PID 4004
> /opt/gemstone/product/seaside/bin/runSeasideGems30: riga 55: kill: (4004) - Nessun processo
>
> ---Finished stopping Seaside gems (19 July 2010 11:28:04 pm)
>
> How i can understand if the gems start fine, are running ?
>
> Thanks,
>
> Dario
>
>

Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

dario trussardi
Dale,


This is where something like DaemonTools comes into play (http://code.google.com/p/glassdb/wiki/GLASSDaemonTools). I can't rely on daemonTools being installed on the various machines, so I publish the runSeasideGems script that gets the job done in a primitive, but relatively portable way.

I update the runSeasideGems for open the port 9020 9021 9022.

When i run it the one relative log ( /opt/gemstone/log/ FastCGI-server-9020.log)  report:

***************************************

 _____________________________________________________________________________
|                             Configuration Files                             |
|                                                                             |
| System File: /mnt/ISTDataBase/dbbase/system.conf                            |
|                                                                             |
| Executable File: /mnt/ISTDataBase/dbbase/gem.conf                           |
|_____________________________________________________________________________|
Using GEM_TEMPOBJ_CACHE_SIZE 50000 from -T command line option
 _____________________________________________________________________________
|                Gem Configuration Options for process id 4793                |
|_____________________________________________________________________________|

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 = 500000;
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-2010                |
|                            All rights reserved.                             |
|     covered by Patent Number 6,567,905 Generational Garbage Collector.      |
+-----------------------------------------------------------------------------+
|    PROGRAM: topaz, Linear GemStone Interface (Linked Session)               |
|    VERSION: 2.4.4.1, Tue Jul 13 15:19:49 2010                               |
|      BUILD: gss64_2_4_4_x_branch-23813                                      |
|  BUILT FOR: x86-64 (Linux)                                                  |
|       MODE: 64 bit                                                          |
| RUNNING ON: 2-CPU monviso x86_64 (Linux 2.6.32-21-server #32-Ubuntu SMP Fri |
| Apr 16 09:17:34 UTC 2010) 2008MB                                            |
| PROCESS ID: 4793      DATE: 20/07/2010 15:08:38 CEST                        |
|   USER IDS: REAL=dario (1000) EFFECTIVE=dario (1000)                        |
|   DATEFORMAT: %d/%m/%Y %T                                                   |
|_____________________________________________________________________________|
topaz> topaz> topaz> topaz> topaz> topaz> topaz> [Info]: LNK client/gem GCI levels = 844/844
[Info]: User ID: DataCurator
[Info]: Repository: base
[Info]: Session ID: 6
[Info]: GCI Client Host: <Linked>
[Info]: Page server PID: -1
[Info]: Login Time: 20/07/2010 15:08:38.217 CEST
[20/07/2010 15:08:38.243 CEST] gci login: currSession 1 rpc gem processId -1
successful login
topaz 1> topaz 1> [20 sz:0 cls: 76289 UndefinedObject] nil
topaz 1> topaz 1> GemStone Smalltalk Compiler Errors:
   true "enable for remote breakpoints and profiling"
     ifTrue: [
       GemToGemAnnouncement installStaticHandler.
       Exception
         installStaticException:
           [:ex :cat :num :args | 
             BreakpointNotification signal.
             "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 
 *         ^1                                                         *******
             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 ', 9020 printString.
   
   FSSeasideHandler startUp: 9020.
 * ^2                                                                 *******
   "does not return"

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

Now executing the following command saved from "iferr 1":
   where
Stack is not active
topaz 1> [268 sz:0 cls: 68097 Boolean] true
topaz 1> 
[Info]: Logging out at 20/07/2010 15:08:38 CEST
dario@monviso:/opt/gemstone/log$ 


******************************************


If after i do  runSeasideGems stop

the system report :


/opt/gemstone/log
Stopping Gems...
   Stopping topaz PID 4710 running on port 9020
/opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4710) - Nessun processo
   
Stopping topaz PID 4714 running on port 9021
/opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4714) - Nessun processo
   
Stopping topaz PID 4716 running on port 9022
/opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4716) - Nessun processo
 
Stopping maintenance gem PID 4712
/opt/gemstone/product/envbase/bin/runSeasideGems: riga 57: kill: (4712) - Nessun processo





I do in Gemtools the command :

 WAFastCGIAdaptor startOn: 9020.

After the web request relative to :  http:<a href="smb://........../welcome">\\..........\welcome 

fork fine.



Thanks for any consideration.

Dario







Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

Dale Henrichs
Aha,

It looks like you are running the wrong script for Seaside30. You should
be running the runSeasideGems30 scripts.

Dale


Dario Trussardi wrote:

> Dale,
>
>
> This is where something like DaemonTools comes into play (http://code.google.com/p/glassdb/wiki/GLASSDaemonTools). I can't rely on daemonTools being installed on the various machines, so I publish the runSeasideGems script that gets the job done in a primitive, but relatively portable way.
>
> I update the runSeasideGems for open the port 9020 9021 9022.
>
> When i run it the one relative log ( /opt/gemstone/log/ FastCGI-server-9020.log)  report:
>
> ***************************************
>
>  _____________________________________________________________________________
> |                             Configuration Files                             |
> |                                                                             |
> | System File: /mnt/ISTDataBase/dbbase/system.conf                            |
> |                                                                             |
> | Executable File: /mnt/ISTDataBase/dbbase/gem.conf                           |
> |_____________________________________________________________________________|
> Using GEM_TEMPOBJ_CACHE_SIZE 50000 from -T command line option
>  _____________________________________________________________________________
> |                Gem Configuration Options for process id 4793                |
> |_____________________________________________________________________________|
>
> 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 = 500000;
> 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-2010                |
> |                            All rights reserved.                             |
> |     covered by Patent Number 6,567,905 Generational Garbage Collector.      |
> +-----------------------------------------------------------------------------+
> |    PROGRAM: topaz, Linear GemStone Interface (Linked Session)               |
> |    VERSION: 2.4.4.1, Tue Jul 13 15:19:49 2010                               |
> |      BUILD: gss64_2_4_4_x_branch-23813                                      |
> |  BUILT FOR: x86-64 (Linux)                                                  |
> |       MODE: 64 bit                                                          |
> | RUNNING ON: 2-CPU monviso x86_64 (Linux 2.6.32-21-server #32-Ubuntu SMP Fri |
> | Apr 16 09:17:34 UTC 2010) 2008MB                                            |
> | PROCESS ID: 4793      DATE: 20/07/2010 15:08:38 CEST                        |
> |   USER IDS: REAL=dario (1000) EFFECTIVE=dario (1000)                        |
> |   DATEFORMAT: %d/%m/%Y %T                                                   |
> |_____________________________________________________________________________|
> topaz> topaz> topaz> topaz> topaz> topaz> topaz> [Info]: LNK client/gem GCI levels = 844/844
> [Info]: User ID: DataCurator
> [Info]: Repository: base
> [Info]: Session ID: 6
> [Info]: GCI Client Host: <Linked>
> [Info]: Page server PID: -1
> [Info]: Login Time: 20/07/2010 15:08:38.217 CEST
> [20/07/2010 15:08:38.243 CEST] gci login: currSession 1 rpc gem processId -1
> successful login
> topaz 1> topaz 1> [20 sz:0 cls: 76289 UndefinedObject] nil
> topaz 1> topaz 1> GemStone Smalltalk Compiler Errors:
>    true "enable for remote breakpoints and profiling"
>      ifTrue: [
>        GemToGemAnnouncement installStaticHandler.
>        Exception
>          installStaticException:
>            [:ex :cat :num :args |
>              BreakpointNotification signal.
>              "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
>  *         ^1                                                         *******
>              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 ', 9020 printString.
>
>    FSSeasideHandler startUp: 9020.
>  * ^2                                                                 *******
>    "does not return"
>
> 1: [1031] undefined symbol
> 2: [1031] undefined symbol
>
> Now executing the following command saved from "iferr 1":
>    where
> Stack is not active
> topaz 1> [268 sz:0 cls: 68097 Boolean] true
> topaz 1>
> [Info]: Logging out at 20/07/2010 15:08:38 CEST
> dario@monviso:/opt/gemstone/log$
>
>
> ******************************************
>
>
> If after i do  runSeasideGems stop
>
> the system report :
>
>
> /opt/gemstone/log
> Stopping Gems...
>    Stopping topaz PID 4710 running on port 9020
> /opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4710) - Nessun processo
>
> Stopping topaz PID 4714 running on port 9021
> /opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4714) - Nessun processo
>
> Stopping topaz PID 4716 running on port 9022
> /opt/gemstone/product/envbase/bin/runSeasideGems: riga 44: kill: (4716) - Nessun processo
>
> Stopping maintenance gem PID 4712
> /opt/gemstone/product/envbase/bin/runSeasideGems: riga 57: kill: (4712) - Nessun processo
>
>
>
>
>
> I do in Gemtools the command :
>
>  WAFastCGIAdaptor startOn: 9020.
>
> After the web request relative to :  http:\\..........\welcome<smb://........../welcome>
>
> fork fine.
>
>
>
> Thanks for any consideration.
>
> Dario
>
>
>
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

dario trussardi
Dale,


>
> It looks like you are running the wrong script for Seaside30. You should be running the runSeasideGems30 scripts.
>

I have create a script for start stone

        source /opt/gemstone/product/envbase/defSeaside
        export GEMSTONE_NAME=base
        export GEMSTONE_DATADIR=$GEMSTONE/envbase/data
        export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf
        export PATH=$GEMSTONE/envbase/bin:$PATH
        $GEMSTONE/envbase/bin/startGemstone
        $GEMSTONE/envbase/bin/runSeasideGems30 start WAFastCGIAdaptor "9020 9021 9022"
        $GEMSTONE/envbase/bin/startnet




and for stop stone

        source /opt/gemstone/product/envbase/defSeaside
        export GEMSTONE_NAME=base
        export GEMSTONE_DATADIR=$GEMSTONE/envbase/data
        export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf
        export PATH=$GEMSTONE/envbase/bin:$PATH
        $GEMSTONE/envbase/bin/runSeasideGems30 stop WAFastCGIAdaptor "9020 9021 9022"
        $GEMSTONE/envbase/bin/stopGemstone


Now after start the stone the web request work fine.

I have a problem when stop because the runSeasideGems30 stop WAFastCGIAdaptor "9020 9021 9022"

d'ont erase the WAFastCGIAdaptor_server-9020.pid  file.


And after the start stone d'ont create the new  relative process.

I think the error is into the runSeasideGems30 script:

..........
.........
        topaz_stop()

{
    echo "Stopping Gems..."
    for port in $PORTS; do

       pidfile=" $GEMSTONE_DATADIR/${SeasideAdaptor}_server-${port}.pid"

        if [ -e $pidfile ]; then
            pid=`cat $pidfile`
            echo "   Stopping ${SeasideAdaptor} topaz PID $pid running on port $port"
            kill $pid
            rm $pidfile
        else
            echo "   No PID file found for gem on port $port, not running?"
        fi


but i'm not expert on it .


The GemTools commads:

WAGemStoneRunSeasideGems default
        name: 'FastCGI';
        adaptorClass: WAFastCGIAdaptor;
        ports: #(9020 9021 9022).
WAGemStoneRunSeasideGems restartGems.

        d'ont work  because ....?????? do refernce to defaut /opt/gemstone/product/seaside   environment.

My environment in this case is /opt/gemstone/product/base.

Thanks,

        Dario











Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

Dale Henrichs
Dario,

To debug the script, I'd need to see the output from you commands ...
and you might want to throw in an echo $pidfile put some echos into the
start adaptor script, too for good measure since the pidfile is created
in that script.

Dale

Dario Trussardi wrote:

> Dale,
>
>
>> It looks like you are running the wrong script for Seaside30. You should be running the runSeasideGems30 scripts.
>>
>
> I have create a script for start stone
>
> source /opt/gemstone/product/envbase/defSeaside
> export GEMSTONE_NAME=base
> export GEMSTONE_DATADIR=$GEMSTONE/envbase/data
> export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf
> export PATH=$GEMSTONE/envbase/bin:$PATH
> $GEMSTONE/envbase/bin/startGemstone
> $GEMSTONE/envbase/bin/runSeasideGems30 start WAFastCGIAdaptor "9020 9021 9022"
> $GEMSTONE/envbase/bin/startnet
>
>
>
>
> and for stop stone
>
> source /opt/gemstone/product/envbase/defSeaside
> export GEMSTONE_NAME=base
> export GEMSTONE_DATADIR=$GEMSTONE/envbase/data
> export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf
> export PATH=$GEMSTONE/envbase/bin:$PATH
> $GEMSTONE/envbase/bin/runSeasideGems30 stop WAFastCGIAdaptor "9020 9021 9022"
> $GEMSTONE/envbase/bin/stopGemstone
>
>
> Now after start the stone the web request work fine.
>
> I have a problem when stop because the runSeasideGems30 stop WAFastCGIAdaptor "9020 9021 9022"
>
> d'ont erase the WAFastCGIAdaptor_server-9020.pid  file.
>
>
> And after the start stone d'ont create the new  relative process.
>
> I think the error is into the runSeasideGems30 script:
>
> ..........
> .........
> topaz_stop()
>
> {
>     echo "Stopping Gems..."
>     for port in $PORTS; do
>
>        pidfile=" $GEMSTONE_DATADIR/${SeasideAdaptor}_server-${port}.pid"
>
>         if [ -e $pidfile ]; then
>             pid=`cat $pidfile`
>             echo "   Stopping ${SeasideAdaptor} topaz PID $pid running on port $port"
>             kill $pid
>             rm $pidfile
>         else
>             echo "   No PID file found for gem on port $port, not running?"
>         fi
>
>
> but i'm not expert on it .
>
>
> The GemTools commads:
>
> WAGemStoneRunSeasideGems default
> name: 'FastCGI';
> adaptorClass: WAFastCGIAdaptor;
> ports: #(9020 9021 9022).
> WAGemStoneRunSeasideGems restartGems.
>
> d'ont work  because ....?????? do refernce to defaut /opt/gemstone/product/seaside   environment.
>
> My environment in this case is /opt/gemstone/product/base.
>
> Thanks,
>
> Dario
>
>
>
>
>
>
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: web request on GLASS

dario trussardi
Dale,

        today i restart the server and after all works fine.
>
> To debug the script, I'd need to see the output from you commands ... and you might want to throw in an echo $pidfile put some echos into the start adaptor script, too for good measure since the pidfile is created in that script.

        Thanks,

                        Dario