fastcgi - lighttpd - gemstone 2.4.4.1

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

fastcgi - lighttpd - gemstone 2.4.4.1

Timothy James Ziebart-2
Problem: Seaside fails to load in browser. When I try and access seaside via fastcgi  using: http://localhost/seaside the browser loads the lighty main page and points to the url: http://localhost.  No error messages and none in the log files I can find.  It makes an attempt (very brief) but falls back the lighttpd login page.

Background:

I did a fresh install of gemstone 2.4.4.1 on ubuntu lucid.  Client and server are on the same server.  The gemstone server installation went well and gemstone and the netldi start just fine.

gslist -lcv:

Status  Version    Owner    Pid   Port   Started     Type  Name
------ --------- --------- ----- ----- ------------ ------ ----
  OK   2.4.4.1   timothy    7767 50377 Sep 02 10:01 Netldi gs64ldi
  OK   2.4.4.1   timothy   23308 38594 Sep 02 09:39 cache  [hidden email]
  OK   2.4.4.1   timothy   23307 35445 Sep 02 09:39 Stone  seaside

I am using Pharo and installed/ updated gemtools to 1.0-beta.8.2.   Logged on and updated Glass:

1.0-beta.8.3 workspace: 'Seaside 3.0' auto: [commit migrate] backup: 'backup.dbf'.

Seaside 3.0.0.rc.2 was loaded.

I run the command:
  runSeasideGems30 start WAFastCGIAdaptor "9001 9002 9003"
to start the Gems and check the logfiles.  Gems started fine and logfile showed a successful topaz  login

In configuring lighttpd I put the following in the fastcgi.conf file.

server.modules   += ( "mod_fastcgi" )

fastcgi.server = ( "/seaside" => (
    ( "host" => "127.0.0.1", "port" => 9001, "check-local" => "disable"),
    ( "host" => "127.0.0.1", "port" => 9002, "check-local" => "disable"),
    ( "host" => "127.0.0.1", "port" => 9003, "check-local" => "disable")
))

The configuration is loaded by lighttpd.  No error messages in lighttpd logfiles.  Not sure what to check next.

Any suggestions?
Thank you in advance.

Tim
Reply | Threaded
Open this post in threaded view
|

Re: fastcgi - lighttpd - gemstone 2.4.4.1 - Disregard - duplicate entry.

Timothy James Ziebart-2
On Thu, 2010-09-02 at 10:17 -0700, Timothy James Ziebart wrote:
Problem: Seaside fails to load in browser. When I try and access seaside via fastcgi  using: http://localhost/seaside the browser loads the lighty main page and points to the url: http://localhost.  No error messages and none in the log files I can find.  It makes an attempt (very brief) but falls back the lighttpd login page.

Background:

I did a fresh install of gemstone 2.4.4.1 on ubuntu lucid.  Client and server are on the same server.  The gemstone server installation went well and gemstone and the netldi start just fine.

gslist -lcv:

Status  Version    Owner    Pid   Port   Started     Type  Name
------ --------- --------- ----- ----- ------------ ------ ----
  OK   2.4.4.1   timothy    7767 50377 Sep 02 10:01 Netldi gs64ldi
  OK   2.4.4.1   timothy   23308 38594 Sep 02 09:39 cache  [hidden email]
  OK   2.4.4.1   timothy   23307 35445 Sep 02 09:39 Stone  seaside

I am using Pharo and installed/ updated gemtools to 1.0-beta.8.2.   Logged on and updated Glass:

1.0-beta.8.3 workspace: 'Seaside 3.0' auto: [commit migrate] backup: 'backup.dbf'.

Seaside 3.0.0.rc.2 was loaded.

I run the command:
  runSeasideGems30 start WAFastCGIAdaptor "9001 9002 9003"
to start the Gems and check the logfiles.  Gems started fine and logfile showed a successful topaz  login

In configuring lighttpd I put the following in the fastcgi.conf file.

server.modules   += ( "mod_fastcgi" )

fastcgi.server = ( "/seaside" => (
    ( "host" => "127.0.0.1", "port" => 9001, "check-local" => "disable"),
    ( "host" => "127.0.0.1", "port" => 9002, "check-local" => "disable"),
    ( "host" => "127.0.0.1", "port" => 9003, "check-local" => "disable")
))

The configuration is loaded by lighttpd.  No error messages in lighttpd logfiles.  Not sure what to check next.

Any suggestions?
Thank you in advance.

Tim