[Glass] Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost
Dale Henrichs via Glass
glass at lists.gemtalksystems.com
Wed May 17 16:01:40 PDT 2017
Reg,
The commands that you've listed look right, but just now I followed the
instructions for installing here[1] and everything installed fine and
the geserver started as expected without compile errors ...
My test was run against 3.3.5, but it shouldn't differ that much from
3.3.3 ...
The compile error you list makes me think that for some reason the stone
that you ran the command in did not have seaside installed at all ...
In the tODE shell, if you do `ol view transcript` and then in the window
that comes up use the `Window > print window` menu item, that window
will have a complete record of everything that you installed in the
stone ... if you want you could send that to me to look at see what
might have happened ...
Dale
[1]
https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md
On 05/17/2017 01:52 PM, Reg Krock via Glass wrote:
>
>
> I installed a new DevKit_33 (3.3.3)
>
> I have installed Seaside in a server GsDevKit sever using the command:
> createStone -f devKit_33 3.3.3 | tee -a $GS_HOME/install.log
>
> Then I executed the following to install Seside3
> project load --loads=`#('Seaside-Welcome' 'Zinc' 'Development'
> 'Examples')` Seaside3
>
> I then tried to register the port:
> home/seaside/gemServer --register=devKit_33 --type=zinc --port=1750
>
> This failed with the message:
>
> a CompileError occurred (error 1001),
> undefined symbol GemServer;
> undefined symbol ZnSeasideNewGemServer;
> undefined symbol ZnSeasideGemServer;
> undefined symbol GemServer;
> undefined symbol Dictionary;
> undefined symbol WARemoteDebuggingWalkbackErrorHandler;
> undefined symbol WAGemStoneProductionErrorHandler;
> undefined symbol WAInteractiveGemServerErrorHandler;
> undefined symbol WAAdmin;
> undefined symbol OrderedCollection;
> undefined symbol WADispatcher;
> undefined symbol TDManPage
>
> and whenI then find that the following classes which are referenced in
> the gemServer script are not loaded into the image.
> FastCGISeasideGems, SwazooSeasideGemServer
>
> ?? Should I have loaded another package or is there a problem with
> the gemServer script ??
>
> I then turned the two references into symbols and seaside server started.
>
> tode 1 > ./gemServer --start=devKit_33
>
> scriptLogEvent: 'performOnServer: devKit_33 ::
> $GS_HOME/shared/repos/gsApplicationTools/bin/startGemServerGem
> devKit_33 "1750" "/Users/regkrock/GsDevKit_home/server/stones/devKit_33"'
> scriptLogEvent: 'performOnServer: SeasideMaintenanceVM ::
> $GS_HOME/shared/repos/gsApplicationTools/bin/startGemServerGem
> SeasideMaintenanceVM
> "''instance’' "/Users/regkrock/GsDevKit_home/server/stones/devKit_33"'[260393985
> sz:17 ZnSeasideNewGemServer]
>
> I then tried to open the web page with no success:
>
> http://localhost:1750/
>
> ?? It has been a long time since I started Seaside. What have I done
> wrong here ??
>
>
>
>
>
>
>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170517/0619cd0b/attachment.html>
More information about the Glass
mailing list