Quantcast

Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list


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:


?? It has been a long time since I started Seaside. What have I done wrong here ??







_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
Did you check the seaside gem logs? What happens with a netstat to 1750? Is the port opened? 

On May 17, 2017 4:52 PM, "Reg Krock via Glass" <[hidden email]> 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:


?? It has been a long time since I started Seaside. What have I done wrong here ??







_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
In reply to this post by GLASS mailing list

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:


?? It has been a long time since I started Seaside. What have I done wrong here ??








_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
Dale,

I have done some more investigation.

I tried to start the gemserver ((GemServer gemServerNamed: 'SeasideGems') startGems.) and as I stepped through the code
I came to the point of executing the script at 
~/GsDEvKit/_home/shared/repos/gsApplicationTools/bin/startGemServerGem
In this script it is attempting to set 

secret=${GEMSTONE_ETC_SECRET}
if [ "${GEMSTONE_ETC_SECRET}x" = "x" ] ; then
  secret=$GEMSTONE/seaside/etc/gemstone.secret
fi

When I echo $GEMSOTNE at the terminal level, I see it is not set. 

Could this be part of the problem?

Regards,

Reg
On 17 May2017, at 7:01 PM, Dale Henrichs via Glass <[hidden email]> wrote:

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:


?? It has been a long time since I started Seaside. What have I done wrong here ??








_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
In reply to this post by GLASS mailing list

Reg,

What instructions are you following to install seaside and run the gemServer?

The instructions on this page[1] are known to work ... I followed them yesterday and they ran without a hitch ...

The fact that you are having issues that I have never seen before, leads me to think that you are departing from the instructions in some way ...

Also are you starting your stone and netldi using $GS_HOME/bin/startStone and $GS_HOME/bin/startNetldi? If not then that could explain some things ...

Dale

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md

On 05/17/2017 07:45 PM, Reg Krock wrote:
Dale,

Attached is the file you requested. The

Also, I have included a copy of all the logs. The SeasideMaintenance… log looks very suspicious. It looks like a script somewhere is looking for gs64ldi. It probably should be looking for devKit_ss_ldi.

Regards,

Reg



























On 17 May2017, at 7:01 PM, Dale Henrichs via Glass <[hidden email]> wrote:

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:


?? It has been a long time since I started Seaside. What have I done wrong here ??








_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
In reply to this post by GLASS mailing list



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
You are missing a leading / in that line, but a missing leading slash gives a different error, so I assume this is a typo...

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
These classes are not required and when I ran the same script that you ran I did not get any compile errors and those two classes are not installed in my stone either ..

Here's an excerpt from my transcript following these instructions[1].:

transcript  'Loaded -> Tode-Server-TestTestTools-dkh.2 --- fil...  29579  05/17/2017 15:51:36:508
transcript  'Evaluated -> baseline [BaselineOfTode] >> initial...  29579  05/17/2017 15:51:36:580
transcript  '...finished baseline'                                 29579  05/17/2017 15:51:36:604
transcript  'Bulk migrate of 0 candidate classes '                 29579  05/17/2017 15:51:36:656
transcript  'No instance migrations performed.'                    29579  05/17/2017 15:51:37:732
transcript  '---Starting backup to ''/home/dhenrich/GsDevKit_h...  30758  05/17/2017 15:51:40:767
transcript  '05/17/2017 15:51:40'                                  30758  05/17/2017 15:51:40:772
transcript  ')'                                                    30758  05/17/2017 15:51:40:772
transcript  '---validating backup ('                               30758  05/17/2017 15:51:46:815
transcript  '05/17/2017 15:51:46'                                  30758  05/17/2017 15:51:46:816
transcript  ')'                                                    30758  05/17/2017 15:51:46:817
transcript  '''/home/dhenrich/GsDevKit_home/server/stones/seas...  30758  05/17/2017 15:51:47:368
transcript  'Source file: /home/dhenrich/GsDevKit_home/server/...  30758  05/17/2017 15:51:47:387
transcript  '---Finished backup to 17/05/2017 15:51:46 -- tode...  30758  05/17/2017 15:51:47:392
transcript  '---Starting snapshot to ''/home/dhenrich/GsDevKit...  30758  05/17/2017 15:51:52:554
transcript  '---Finishing snapshot 05/17/2017 15:51:53 -- /hom...  30758  05/17/2017 15:51:53:010
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  30803  05/17/2017 15:52:44:899
transcript  'Cloning into ''Seaside31''...
'                       30803  05/17/2017 15:52:44:917
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  30803  05/17/2017 15:52:46:486
transcript  'Already on ''gs_master''
Your branch is up-to-dat...  30803  05/17/2017 15:52:46:494
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  30803  05/17/2017 15:52:46:507
transcript  'refs/heads/gs_master
'                                30803  05/17/2017 15:52:46:513
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  30803  05/17/2017 15:52:51:381
transcript  'Cloning into ''gsApplicationTools''...
'              30803  05/17/2017 15:52:51:390
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  30803  05/17/2017 15:52:51:494
transcript  'Already on ''master''
Your branch is up-to-date w...  30803  05/17/2017 15:52:51:500
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  30803  05/17/2017 15:52:51:517
transcript  'refs/heads/master
'                                   30803  05/17/2017 15:52:51:523
transcript  'Fetched -> BaselineOfSeaside3-dkh.43 --- filetree...  30803  05/17/2017 15:53:26:763

The `Cloning into` entries indicate that I installed the seaside project:

  project install --url=http://gsdevkit.github.io/GsDevKit_home/Seaside3.ston


and your transcript indicates that you did not run the install:

transcript  'Loaded -> Tode-Remote-Server-dkh.18 --- filetree:...  73754  05/17/2017 12:43:42:402
transcript  'Evaluated -> baseline [BaselineOfTode] >> initial...  73754  05/17/2017 12:43:42:454
transcript  '...finished baseline'                                 73754  05/17/2017 12:43:42:473
transcript  'Bulk migrate of 0 candidate classes '                 73754  05/17/2017 12:43:42:547
transcript  'No instance migrations performed.'                    73754  05/17/2017 12:43:42:682
transcript  '---Starting backup to ''/Users/regkrock/GsDevKit_...  74961  05/17/2017 12:43:43:965
transcript  '05/17/2017 12:43:43'                                  74961  05/17/2017 12:43:43:977
transcript  ')'                                                    74961  05/17/2017 12:43:43:990
transcript  '---validating backup ('                               74961  05/17/2017 12:43:50:720
transcript  '05/17/2017 12:43:50'                                  74961  05/17/2017 12:43:50:733
transcript  ')'                                                    74961  05/17/2017 12:43:50:746
transcript  '''/Users/regkrock/GsDevKit_home/server/stones/dev...  74961  05/17/2017 12:43:51:206
transcript  'Source file: /Users/regkrock/GsDevKit_home/server...  74961  05/17/2017 12:43:51:232
transcript  '---Finished backup to 17/05/2017 12:43:50 -- tode...  74961  05/17/2017 12:43:51:259
transcript  '---Starting snapshot to ''/Users/regkrock/GsDevKi...  74961  05/17/2017 12:43:55:685
transcript  '---Finishing snapshot 05/17/2017 12:43:56 -- /Use...  74961  05/17/2017 12:43:56:659
transcript  'Fetched -> BaselineOfSeaside3-dkh.43 --- filetree...  75014  05/17/2017 12:49:10:001

I also see that I am getting different packages loaded than you were ... so I am wondering if perhaps we haven't run exactly the same Seaside load command or since I don't know how you cloned your local Seaside3 repository, it's possible that we are not using the same commit of Seaside ... a spot check of the variaous package versions indicates that we appear to be loading the same package versions of common packages, but I didn't dig in too deep .. I've attached my transcript log (reg.txt) for comparison.

If you do a `Window > print window` of the `project list`, I will be able to tell which commits you are using ... I've attached mine (projectList.txt) for comparison

Also I noticed that you have not loaded the master version of tODE and appear to have loaded the dev version of tODE ... that shouldn't be a problem, but I didn't run my tests yesterday using the dev version of tODE, so this is another area where we are doing things differently ... I'll do a test with the dev version of tODE later today to see what I get ...

Dale

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md

?? 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:


?? It has been a long time since I started Seaside. What have I done wrong here ??








_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

reg.txt (58K) Download Attachment
projectList.txt (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
However I did not have any problems with gemServer.ston script. That problem went away.

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.





All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.

I have also attached copies of all of the logs in case they are useful.













 
On 18 May2017, at 1:26 PM, Dale Henrichs via Glass <[hidden email]> wrote:



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
You are missing a leading / in that line, but a missing leading slash gives a different error, so I assume this is a typo...

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
These classes are not required and when I ran the same script that you ran I did not get any compile errors and those two classes are not installed in my stone either ..

Here's an excerpt from my transcript following these instructions[1].:


These appear to be the same now.

transcript  'Loaded -> Tode-Server-TestTestTools-dkh.2 --- fil...  29579  05/17/2017 15:51:36:508
transcript  'Evaluated -> baseline [BaselineOfTode] >> initial...  29579  05/17/2017 15:51:36:580
transcript  '...finished baseline'                                 29579  05/17/2017 15:51:36:604
transcript  'Bulk migrate of 0 candidate classes '                 29579  05/17/2017 15:51:36:656
transcript  'No instance migrations performed.'                    29579  05/17/2017 15:51:37:732
transcript  '---Starting backup to ''/home/dhenrich/GsDevKit_h...  30758  05/17/2017 15:51:40:767
transcript  '05/17/2017 15:51:40'                                  30758  05/17/2017 15:51:40:772
transcript  ')'                                                    30758  05/17/2017 15:51:40:772
transcript  '---validating backup ('                               30758  05/17/2017 15:51:46:815
transcript  '05/17/2017 15:51:46'                                  30758  05/17/2017 15:51:46:816
transcript  ')'                                                    30758  05/17/2017 15:51:46:817
transcript  '''/home/dhenrich/GsDevKit_home/server/stones/seas...  30758  05/17/2017 15:51:47:368
transcript  'Source file: /home/dhenrich/GsDevKit_home/server/...  30758  05/17/2017 15:51:47:387
transcript  '---Finished backup to 17/05/2017 15:51:46 -- tode...  30758  05/17/2017 15:51:47:392
transcript  '---Starting snapshot to ''/home/dhenrich/GsDevKit...  30758  05/17/2017 15:51:52:554
transcript  '---Finishing snapshot 05/17/2017 15:51:53 -- /hom...  30758  05/17/2017 15:51:53:010
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  30803  05/17/2017 15:52:44:899
transcript  'Cloning into ''Seaside31''...
'                       30803  05/17/2017 15:52:44:917
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  30803  05/17/2017 15:52:46:486
transcript  'Already on ''gs_master''
Your branch is up-to-dat...  30803  05/17/2017 15:52:46:494
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  30803  05/17/2017 15:52:46:507
transcript  'refs/heads/gs_master
'                                30803  05/17/2017 15:52:46:513
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  30803  05/17/2017 15:52:51:381
transcript  'Cloning into ''gsApplicationTools''...
'              30803  05/17/2017 15:52:51:390
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  30803  05/17/2017 15:52:51:494
transcript  'Already on ''master''
Your branch is up-to-date w...  30803  05/17/2017 15:52:51:500
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  30803  05/17/2017 15:52:51:517
transcript  'refs/heads/master
'                                   30803  05/17/2017 15:52:51:523
transcript  'Fetched -> BaselineOfSeaside3-dkh.43 --- filetree...  30803  05/17/2017 15:53:26:763

 transcript  'Loaded -> Tode-Server-TestTestTools-dkh.2 --- fil...  94159  05/18/2017 16:11:31:954
transcript  'Evaluated -> baseline [BaselineOfTode] >> initial...  94159  05/18/2017 16:11:32:022
transcript  '...finished baseline'                                 94159  05/18/2017 16:11:32:048
transcript  'Bulk migrate of 0 candidate classes '                 94159  05/18/2017 16:11:32:121
transcript  'No instance migrations performed.'                    94159  05/18/2017 16:11:32:385
transcript  '---Starting backup to ''/Users/regkrock/GsDevKit_...  95300  05/18/2017 16:11:34:242
transcript  '05/18/2017 16:11:34'                                  95300  05/18/2017 16:11:34:256
transcript  ')'                                                    95300  05/18/2017 16:11:34:268
transcript  '---validating backup ('                               95300  05/18/2017 16:11:42:225
transcript  '05/18/2017 16:11:42'                                  95300  05/18/2017 16:11:42:239
transcript  ')'                                                    95300  05/18/2017 16:11:42:251
transcript  '''/Users/regkrock/GsDevKit_home/server/stones/dev...  95300  05/18/2017 16:11:42:713
transcript  'Source file: /Users/regkrock/GsDevKit_home/server...  95300  05/18/2017 16:11:42:740
transcript  '---Finished backup to 18/05/2017 16:11:41 -- tode...  95300  05/18/2017 16:11:42:767
transcript  '---Starting snapshot to ''/Users/regkrock/GsDevKi...  95300  05/18/2017 16:11:46:285
transcript  '---Finishing snapshot 05/18/2017 16:11:46 -- /Use...  95300  05/18/2017 16:11:46:964
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  95534  05/18/2017 16:16:41:348
transcript  'Cloning into ''Seaside31''...
'                       95534  05/18/2017 16:16:41:381
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  95534  05/18/2017 16:16:45:048
transcript  'Already on ''gs_master''
Your branch is up-to-dat...  95534  05/18/2017 16:16:45:083
transcript  '''cd $GS_HOME/shared/repos/Seaside31; git --git-d...  95534  05/18/2017 16:16:45:139
transcript  'refs/heads/gs_master
'                                95534  05/18/2017 16:16:45:171
transcript  '''cd $GS_HOME/shared/repos; git clone  --no-check...  95534  05/18/2017 16:16:47:361
transcript  'Cloning into ''gsApplicationTools''...
'              95534  05/18/2017 16:16:47:390
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  95534  05/18/2017 16:16:47:575
transcript  'Already on ''master''
Your branch is up-to-date w...  95534  05/18/2017 16:16:47:601
transcript  '''cd $GS_HOME/shared/repos/gsApplicationTools; gi...  95534  05/18/2017 16:16:47:640
transcript  'refs/heads/master
'                                   95534  05/18/2017 16:16:47:667
transcript  'Fetched -> BaselineOfGsApplicationTools-dkh.10 --...  95534  05/18/2017 16:19:10:207

The `Cloning into` entries indicate that I installed the seaside project:

  project install --url=http://gsdevkit.github.io/GsDevKit_home/Seaside3.ston


and your transcript indicates that you did not run the install:

transcript  'Loaded -> Tode-Remote-Server-dkh.18 --- filetree:...  73754  05/17/2017 12:43:42:402
transcript  'Evaluated -> baseline [BaselineOfTode] >> initial...  73754  05/17/2017 12:43:42:454
transcript  '...finished baseline'                                 73754  05/17/2017 12:43:42:473
transcript  'Bulk migrate of 0 candidate classes '                 73754  05/17/2017 12:43:42:547
transcript  'No instance migrations performed.'                    73754  05/17/2017 12:43:42:682
transcript  '---Starting backup to ''/Users/regkrock/GsDevKit_...  74961  05/17/2017 12:43:43:965
transcript  '05/17/2017 12:43:43'                                  74961  05/17/2017 12:43:43:977
transcript  ')'                                                    74961  05/17/2017 12:43:43:990
transcript  '---validating backup ('                               74961  05/17/2017 12:43:50:720
transcript  '05/17/2017 12:43:50'                                  74961  05/17/2017 12:43:50:733
transcript  ')'                                                    74961  05/17/2017 12:43:50:746
transcript  '''/Users/regkrock/GsDevKit_home/server/stones/dev...  74961  05/17/2017 12:43:51:206
transcript  'Source file: /Users/regkrock/GsDevKit_home/server...  74961  05/17/2017 12:43:51:232
transcript  '---Finished backup to 17/05/2017 12:43:50 -- tode...  74961  05/17/2017 12:43:51:259
transcript  '---Starting snapshot to ''/Users/regkrock/GsDevKi...  74961  05/17/2017 12:43:55:685
transcript  '---Finishing snapshot 05/17/2017 12:43:56 -- /Use...  74961  05/17/2017 12:43:56:659
transcript  'Fetched -> BaselineOfSeaside3-dkh.43 --- filetree...  75014  05/17/2017 12:49:10:001

I also see that I am getting different packages loaded than you were ... so I am wondering if perhaps we haven't run exactly the same Seaside load command or since I don't know how you cloned your local Seaside3 repository, it's possible that we are not using the same commit of Seaside ... a spot check of the variaous package versions indicates that we appear to be loading the same package versions of common packages, but I didn't dig in too deep .. I've attached my transcript log (reg.txt) for comparison.

If you do a `Window > print window` of the `project list`, I will be able to tell which commits you are using ... I've attached mine (projectList.txt) for comparison

Also I noticed that you have not loaded the master version of tODE and appear to have loaded the dev version of tODE ... that shouldn't be a problem, but I didn't run my tests yesterday using the dev version of tODE, so this is another area where we are doing things differently ... I'll do a test with the dev version of tODE later today to see what I get ...

Dale

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md

?? 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:


?? It has been a long time since I started Seaside. What have I done wrong here ??








_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

<reg.txt><projectList.txt>_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

installationSteps.txt (8K) Download Attachment
loadingTranscript.txt (46K) Download Attachment
devKit_33_94049pagemanager.log (1K) Download Attachment
devKit_33_94050pcmon.log (5K) Download Attachment
devKit_33_94053pgsvrff.log (3K) Download Attachment
devKit_33_94055pgsvraio.log (3K) Download Attachment
devKit_33_94059reclaimgcgem.log (7K) Download Attachment
devKit_33_94060admingcgem.log (6K) Download Attachment
devKit_33_94061symbolgem.log (10K) Download Attachment
devKit_33.log (10K) Download Attachment
seaside_server-1750.log (7K) Download Attachment
SeasideMaintenanceVM_server-instance.log (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list



On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
Hi all,

I ran into those NetLDI issues recently, the fix was to add my hostname to the /etc/hosts file (next to localhost).

Best,
Ricardo

On 19 May 2017, 05:42 +0200, Dale Henrichs via Glass <[hidden email]>, wrote:



On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
Dale,

That reminded me another problem with the .topazini.  Remember we concluded we want to rollback this issue [1] ? 
The reason is simple.... if we have the netldi line in the topazini then all logins are RPC (not linked...even if I explicitly pass a -l ) hence we loose logs. 



Cheers,

On Fri, May 19, 2017 at 8:14 AM, Ricardo Correa via Glass <[hidden email]> wrote:
Hi all,

I ran into those NetLDI issues recently, the fix was to add my hostname to the /etc/hosts file (next to localhost).

Best,
Ricardo

On 19 May 2017, 05:42 +0200, Dale Henrichs via Glass <[hidden email]>, wrote:



On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass




--

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list

re-opened the bug ... I think I'll leave the line and comment it out ... that way there is a template gemnetid present ...

Dale

On 5/19/17 4:46 AM, Mariano Martinez Peck wrote:
Dale,

That reminded me another problem with the .topazini.  Remember we concluded we want to rollback this issue [1] ? 
The reason is simple.... if we have the netldi line in the topazini then all logins are RPC (not linked...even if I explicitly pass a -l ) hence we loose logs. 



Cheers,

On Fri, May 19, 2017 at 8:14 AM, Ricardo Correa via Glass <[hidden email]> wrote:
Hi all,

I ran into those NetLDI issues recently, the fix was to add my hostname to the /etc/hosts file (next to localhost).

Best,
Ricardo

On 19 May 2017, 05:42 +0200, Dale Henrichs via Glass <[hidden email]>, wrote:



On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass




--


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
In reply to this post by GLASS mailing list

On 18 May2017, at 11:42 PM, Dale Henrichs <[hidden email]> wrote:

On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.


I had added my computer name to the host file back in 2014 [1]. The server starts fine and I can connect with the tode1 client. 

It is just the seaside connection that appears to be a problem. I have even turned my mac’s own firewall off to ensure that was not the source of the problem.

port: 1750
seaside server class:  aZnSeasideNewGemServer
browser: localhost:1750

[1] etc/hosts file contents. I think that I added rk.home for the installation of 3.1.x in 2014.
rk:etc regkrock$ cat hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
127.0.0.1 rk.home
::1             localhost 
fe80::1%lo0 localhost

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

Yes.


I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175


_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list

Reg,

Did you notice that in my email I identified the .topazini in your $HOME directory as the culprit?

Your (probably old) .topazini has a `gemnetid` entry that causes toaz to be opened in rpc mode using the default netldi `gs64ldi` ... the topaz sessions for the gemserver are intended to be run as linked logins, so no attempt was made for setting up a netldi.

Remove the .topazini in your $HOME directory and things should run as expected ...

Dale


On 5/19/17 6:50 AM, Reg Krock wrote:

On 18 May2017, at 11:42 PM, Dale Henrichs <[hidden email]> wrote:

On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.


I had added my computer name to the host file back in 2014 [1]. The server starts fine and I can connect with the tode1 client. 

It is just the seaside connection that appears to be a problem. I have even turned my mac’s own firewall off to ensure that was not the source of the problem.

port: 1750
seaside server class:  aZnSeasideNewGemServer
browser: localhost:1750

[1] etc/hosts file contents. I think that I added rk.home for the installation of 3.1.x in 2014.
rk:etc regkrock$ cat hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
127.0.0.1 rk.home
::1             localhost 
fe80::1%lo0 localhost

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

Yes.


I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175



_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Seaside - Installation - (1) problem with gemServer.ston script; (2) attaching via localhost

GLASS mailing list
Dale,

I missed it. 

Everything works like a charm now.

Regards

Reg

On 19 May2017, at 9:57 AM, Dale Henrichs <[hidden email]> wrote:

Reg,

Did you notice that in my email I identified the .topazini in your $HOME directory as the culprit?

Your (probably old) .topazini has a `gemnetid` entry that causes toaz to be opened in rpc mode using the default netldi `gs64ldi` ... the topaz sessions for the gemserver are intended to be run as linked logins, so no attempt was made for setting up a netldi.

Remove the .topazini in your $HOME directory and things should run as expected ...

Dale


On 5/19/17 6:50 AM, Reg Krock wrote:

On 18 May2017, at 11:42 PM, Dale Henrichs <[hidden email]> wrote:

On 5/18/17 5:14 PM, Reg Krock wrote:
This continues to be frustrating. Do you know if there is anything special that needs to be done on OS/X?
Up until now, I didn't know you were on a mac. When Sierra was first released there were issues with running a stone[1]. Those issues were resolved with the release of 10.2.2[2]. Since then Johan reported some issues with getting the hostname set up correctly for Sierra[3]. James had some issues with running GemStone on Sierra, but I don't have an email trail for his issue -- I'll ask him to see if he remembers what the problem was and what he did to fix or work around it ... Other than James, it seems that there are a number of people  using GsDevKit_home and Seaside without hitting the type of problem you are reporting, but then you are using a relatively recent version of Sierra and I don't know (yet) if your issue is related to the new version or something else.


I had added my computer name to the host file back in 2014 [1]. The server starts fine and I can connect with the tode1 client. 

It is just the seaside connection that appears to be a problem. I have even turned my mac’s own firewall off to ensure that was not the source of the problem.

port: 1750
seaside server class:  aZnSeasideNewGemServer
browser: localhost:1750

[1] etc/hosts file contents. I think that I added rk.home for the installation of 3.1.x in 2014.
rk:etc regkrock$ cat hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
127.0.0.1 rk.home
::1             localhost 
fe80::1%lo0 localhost

I'm running on OS/X 10.10.5 ... at home ... up until now and I've been testing against linux .. at work. When Sierra first came out it didn't support the VPN client that I use and then there were the basic problems with GemStone and then there were the issues with running stones at all, so I've been a bit gun shy about updating ...

[1] http://forum.world.st/GS3-3-0-and-macOS-Sierra-100-CPU-td4918469.html
[2] http://forum.world.st/MacOS-Sierra-support-td4928733.html
[3] http://forum.world.st/SmalltalkCI-gemstone-on-mac-os-sierra-td4939640.html#a4939669

I am running both code client and gemstone server on my MacBook (OS/X 10.12.4) and I have answered ‘Allow’ to ‘’stoned’’ and “netldi” accepting incoming network connections.

What I did today was to rename my GsDevKit_home to GsDevKit_home_old and then I have three reinstalled 3.3.5 from scratching using port 1750. All to no avail.
Okay ... I'm building a Seaside stone on my own laptop so that I've got something to compare with ....
However I did not have any problems with gemServer.ston script. That problem went away.
Okay ... I'll guess that I've got an issue with on the dev branch of tODE ...

The two files below are: (1) the installation steps including ‘project load’ prints and inspector prints of the seaside server and WADisplatcher; (2) the transcript.
I notice in the installation steps that you explicitly installed GsApplicationTools (step 13) --- it shouldn't make a difference because Seaside itself should install GsApplicationTools --- I'm just curious why you felt it necessary to do that step, since it isn't listed in the Seaside steps that I've recommended that you use[1] ...

[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/docs/gettingStartedWithSeaside.md







All attempts to connect from the Web Browser to the seaside gem failed.

I then took a Pharo 5.0 image, loaded in seaside and started seaside. I was able to connect.
Did you use port 1750 for the seaside port in Pharo5.0?

Yes.


I have also attached copies of all of the logs in case they are useful.


I'm suspicious that the seaside gems aren't properly starting ... and concerned that the you didn't get any error feedback (if indeed the gems didn't start properly)... My first clue is in your transcript. At the very end your transcript looks like the following

transcript  '---Finished backup to 18/05/2017 16:22:35 -- seas...  95534  05/18/2017 16:22:36:469
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  95534  05/18/2017 16:23:20:291
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  95534  05/18/2017 16:23:20:371
and when I ran the /home/seaside/gemServer script I got the following entries:

transcript  '---Finished backup to 17/05/2017 15:55:19 -- seas...  30803  05/17/2017 15:55:21:314
transcript  'scriptLogEvent: ''performOnServer: seaside :: $GS...  30803  05/17/2017 15:55:47:562
transcript  'scriptLogEvent: ''performOnServer: SeasideMainten...  30803  05/17/2017 15:55:47:655
transcript  'scriptLogEvent: ''-->>Script Start seaside on 175...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''recordGemPid: seaside on 1750''...  32375  05/17/2017 15:55:47:686
transcript  'scriptLogEvent: ''setStatmonCacheName: seaside'''     32375  05/17/2017 15:55:47:688
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32375  05/17/2017 15:55:47:689
transcript  'scriptLogEvent: ''-->>Script Start SeasideMainten...  32385  05/17/2017 15:55:47:696
transcript  'scriptLogEvent: ''recordGemPid: SeasideMaintenanc...  32385  05/17/2017 15:55:47:700
transcript  'scriptLogEvent: ''setStatmonCacheName: SeasideMai...  32385  05/17/2017 15:55:47:704
transcript  'scriptLogEvent: ''enableRemoteBreakpointHandling:...  32385  05/17/2017 15:55:47:704

This implies that there is something fishy going on ... and sure enough, when I look at your seaside_server-1750.log file, the login is failing:

GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Login failed due to errors.
topaz > exec iferr 1 : stack
STACK can't be used prior to logging in.
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------

The maintenance vm is having a similar problem:

topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20

Sooo for some reason the gemserver script is not failing when the gem fails to start, so that looks like a bug in the gem server starting code and/or tode script ...

I've compared the post-Seaside load `project list` and other than the fact that your listing of the short SHA does not exactly match the short SHA that I see in my list, we have loaded and are using exactly the same code .... so thank you for rebuilding the system and providing me with the additional details, so I can confirm that we're on the same page and eliminate those variables ...

Well my build just finished and of course the servers start just fine for me ...

You are obviously able to connect to the netldi, since you are using tODE ...

Looking closer at the  seaside_server-1750.log note that topaz is processing the $HOME/.topazini file which also appears to be doing a login ...
================
Reading initialization file /Users/regkrock/.topazini
topaz> set gemstone gs64stone
topaz> set gemnetid gemnetobject
topaz> set username DataCurator
topaz> set password swordfish
topaz> lo
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems devKit_33
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Now, I've created a similar .topazini file in my $HOME and I get the same login failure:

==========================
Reading initialization file /Users/dhenrich/.topazini
topaz> SET GEMSTONE gss_344
topaz> set gemnetid gemnetobject
topaz> set user DataCurator
topaz> set password swordfish
topaz> login
[Info]: libssl-3.3.5-64.dylib: loaded
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(14,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: [GemStone] Number: 4042  Arg Count: 0

Login failed due to errors.
topaz>
End of initialization files
topaz>
topaz> set user DataCurator pass swordfish gems reg_335
Warning: clearing the previous GemStone password.
topaz>
topaz> display oops
topaz> iferror stack
topaz>
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
Unable to create a session, check netldi and gem log files.
NetLDI service 'gs64ldi' not found on node 'localhost6' port 50377 :
connect(11,::ffff:127.0.0.1,port=50377) failed with errno=22,EINVAL, Invalid argument (programmer error)
Error Category: 231169 [GemStone] Number: 4042  Arg Count: 0 Context : 20 exception : 20
==========================

Sooooo, it's the .topazini file in your home directory that is the culprit ... if you remove that file, the scripts should start the gemservers properly ...

I've submitted a bug on this[4] and I consider it a bug that the gemserver script was not exiting with an error message ...

Hopefully things will start to go a bit smoother for you ...

Dale

[4] https://github.com/GsDevKit/GsDevKit_home/issues/175




_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass
Loading...