fastcgi - lighttpd - gemstone 2.4.4.1

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
seaside@localhost
  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

Tim,

Thanks Nick that was it however,  but now the css files are not being loaded for Seaside (from the /files directory).  Is that a configuration issue for lighttpd?

On Thu, 2010-09-02 at 18:48 +0100, Nick Ager wrote:

Tim,

 It makes an attempt
(very brief) but falls back the lighttpd login page.

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")
))

Seaside3.0 listens on the root and /seaside is only there for legacy reasons and I think redirects to /
So it could be that the redirect is occurring but your server isn't forwarding / requests onto Seaside.


Try modifying your lighttp configuration to:


 fastcgi.server = ("/" =>(
    ("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")
   )
  )


No guarantees, though something similar worked for me


Nick  

Timothy James Ziebart wrote:
> Thanks Nick that was it however,  but now the css files are not being
> loaded for Seaside (from the /files directory).  Is that a configuration
> issue for lighttpd?

Yes it is a lighttpd config issue ... I think you need to intercept the
'/file' explicitly or prevent it from being swallowed by the fastcgi
handler ... I have done it before, but the example is on my laptop at
home ... if you haven't got a response by tonight, I'll extract the
example when I get home ...

Hi,

add this to your lighttpd.conf .
       
## Gestione indirizzamento WAFileHandler
$HTTP["url"]=~ "^/files" {

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

I hope this help.

        Dario