[Seaside] Seaside on EC2 Amazon Service
mac.hive at me.com
Tue Oct 18 18:32:04 UTC 2011
On Oct 18, 2011, at 12:09 PM, Nick Ager wrote:
> After doing this:
> Gofer project load: 'Seaside30' group: 'ALL'.
> Gofer project load: 'Pier2'.
> Gofer project load: 'PierAddOns2' group: 'ALL'.
> WAGemStoneRunSeasideGems default
> name: 'FastCGI';
> adaptorClass: WAFastCGIAdaptor;
> ports: #(9001 9002 9003).
> WAGemStoneRunSeasideGems restartGems.
> I hit the web server and get the 50x error file I had created.
> I just noticed that the Seaside classes are not loaded even though it takes forever to
> come back from the Gofer command, so I am puzzled about what I am doing wrong....
> Did you have a Transcript open when you tried loading?
> Have you configured a front-end server that understands FastCGI?
Ok, I got everything loaded and started up the Gems. Yes, I had a Transcript up
and didn't see anything suspicious, just that everything takes a long time.
Stopping FastCGI topaz PID 27420 running on port 9001
Stopping FastCGI topaz PID 27419 running on port 9002
Stopping FastCGI topaz PID 27416 running on port 9003
Stopping maintenance gem PID 27413
Stopping service gem PID 27417
Starting FastCGI gem on port 9001
Starting FastCGI gem on port 9002
Starting FastCGI gem on port 9003
Starting maintenance gem
Starting service gem
but still the 50x error message.
I'm running NGINX, as you suggested, and I thought that would give me
FastCGI capability, on port 9003, as you mentioned in the documentation.
I admit to being a little lost with this one.
> It's probably best to post Gemstone specific queries on the Gemstone mailing list.
I guess I'm in the wrong place. Sorry about that. I have asked to be subscribed to the GemStone Seaside list.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside