[Glass] gsDevKit / tode first time setup

Jon Paynter via Glass glass at lists.gemtalksystems.com
Mon Oct 19 22:13:06 PDT 2015


ok I got the session properties updated on the client  - I changed
"seaside_ldi" to "netldi"

and now i can log in.
I opened the project list, but when poking around in the menus to try and
create a new project, something broke and now I get a dictionary error
"attempt to store nil as a key"
restarting the tode client doesnt seem to rollback whatever changes were
made, so now the project list is broken.

not sure how to get a stack dump or I would include one here.

On Mon, Oct 19, 2015 at 9:05 PM, Dale Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

> It looks like you have left seaside_ldi as your netldi and that does not
> work unless you have editted your /etc/services file (I thought I'd
> mentioned this in an earlier email and I think it's covered in the doc) ...
> if you don't edit the /etc/services file, you need to put the port number
> of seaside_ldi into your session description ("Client >Edit Description"
> menu item ... also select and doit in the workspace to write the updated
> session description) you get the port number from the netldi listing of the
> stones command run on the server ...
>
> Dale
>
>
> On 10/19/15 7:52 PM, Jon Paynter wrote:
>
> well i guess I was impatient - the testLogin eventually DID return, but
> with an error:
> Error running testLogin:
>
> 'Error: Unable to create a GemStone session, check netldi log file.
> service not found, on bigyan getaddrinfo(host ''ubuntu'', service
> ''seaside_ldi'') failed
> ;  service seaside_ldi not found  For further information about login
> failures, check the gem log file'
>
> So I changed the 'ubuntu' strings in the sessions file to the IP of my vm:
> 192.168.1.137, and I got the same error -- but a MUCH faster return.
>
> do I need to setup something with net ldi on my local PC?  or is the ssh
> port forward not working?
>
>
> On Mon, Oct 19, 2015 at 7:40 PM, Jon Paynter <kittle31 at gmail.com> wrote:
>
>> I will re-test when I return to work tomorrow -- it was probably the
>> corporate firewall getting in the way.
>>
>> On my home PC, the install worked last nite.
>>
>> I ran the long ssh cmd:
>> ssh 192.168.1.137 -l gemstone -L 55320:localhost:55320 -L
>> 55325:localhost:55325
>>
>> Which prompted for a pw and then I got the usual  prompt
>> I tried to run the startnetldi cmd from link you sent  (
>> https://github.com/GsDevKit/gsDevKitHome/blob/master/docs/portForwardingForRemoteLogins.md
>> )
>>
>> It complained when I had the -p (lowercase) option
>> but this one seemed to work:
>> $GEMSTONE/bin/startnetldi -a gemstone -g -P 55320 seaside_ldi
>>
>> startnetldi[Info]: GemStone version '3.2.8'
>> startnetldi[Info]: Starting GemStone network server 'seaside_ldi'.
>> startnetldi[Info]: GEMSTONE is:
>> '/home/gemstone/GsDevKit_home/server/stones/seaside/product'.
>> startnetldi[Info]: GEMSTONE_NRS_ALL is:
>> '#dir:$GEMSTONE_LOGDIR#log:%N%P.log'.
>> startnetldi[Info]: Log file is '/opt/gemstone/log/seaside_ldi.log'.
>> startnetldi[Info]: GemStone server 'seaside_ldi' has been started,
>> process 1879 .
>>
>> Then I started the stone process via startGemstone, and both of them show
>> up:
>>
>> gemstone at ubuntu:~/GsDevKit_home/server/stones/seaside$ gslist -lv
>> Status       Version    Owner    Pid   Port   Started     Type       Name
>> -------     --------- --------- ----- ----- ------------ ------      ----
>>   OK        3.2.8     gemstone   1890 48297 Oct 20 02:21 cache
>> seaside~e39397a912896488
>>   OK        3.2.8     gemstone   1888 33849 Oct 20 02:21 Stone
>> seaside
>>   OK        3.2.8     gemstone   1879 55320 Oct 20 02:16 Netldi
>>  seaside_ldi
>>
>> After that I went to my local host and ran 'startClient tode'
>> That launched a modified pharo image with just a single transcript window.
>> but the right-click menu looks nothing like what is in your screenshot --
>> I dont see a 'tode' menu.  I guess the layout changed?
>>
>> I managed to find the shell, and run 'testLogin'    but then the pharo
>> image became non-responsive and eventually I killed it
>> The log file only had 1 line in it
>>      [Info]: libssl-3.2.8-32.dll: loaded
>>
>>
>> where to next for debugging?
>>
>> On Mon, Oct 19, 2015 at 6:37 PM, Dale Henrichs <
>> <dale.henrichs at gemtalksystems.com>dale.henrichs at gemtalksystems.com>
>> wrote:
>>
>>> Unfortunately this is another case of a (random) partial pharo download
>>> ... I don't quite understand how it can fail partway through the download
>>> without errors ... it might help me figure out a solution if you enclosed a
>>> little bit more of the install log ... or did you get an error and then try
>>> again?
>>>
>>> If you did get an error during the pharo download, in a previous
>>> attempt, then I might be able to write a bash error handler that cleans
>>> things up in the event of failed download ... OTOH if the pharo download is
>>> silently failing then an error handler won't be triggered and an alternate
>>> solution will have to be tried ---- perhaps a validation step after the
>>> download to ensure that the pharo download worked correctly ...
>>>
>>> Could you let me know if there was an error triggered during the failed
>>> download (or pass along more of the log so I can determine for myself)?
>>>
>>> And yes Marianos workaround should work until I get a patch in place ...
>>>
>>>
>>> Dale
>>>
>>>
>>> On 10/19/15 5:24 PM, Mariano Martinez Peck wrote:
>>>
>>> rm -rf  $GS_HOME/shared/pharo/pharo-vm/  and try again?
>>> or.... do a mv  just to not loose pharo folder in case it is not
>>> recoverable until Dale answers ;)
>>>
>>>
>>> On Mon, Oct 19, 2015 at 8:54 PM, Jon Paynter via Glass <
>>> <glass at lists.gemtalksystems.com>glass at lists.gemtalksystems.com> wrote:
>>>
>>>> I see the docs getting updated -- this is good.
>>>>
>>>> but now the server install script is failing.  I re-ran installServer
>>>> on a different VM and now I get a new error:
>>>>
>>>>
>>>> gemstone at ubuntu:~/GsDevKit_home$ installServer seaside 3.2.8
>>>>      ............
>>>> create gsDevKitCommandLine.image image using
>>>> /home/gemstone/GsDevKit_home/sys/default/pharo/gsDevKitCommandLineLoad.st
>>>> /home/gemstone/GsDevKit_home/shared/pharo/pharo: line 11:
>>>> /home/gemstone/GsDevKit_home/shared/pharo/pharo-vm/pharo: No such file or
>>>> directory
>>>>
>>>> Any ideas on how to fix this one?
>>>>
>>>> On Mon, Oct 19, 2015 at 10:31 AM, Dale Henrichs <
>>>> <dale.henrichs at gemtalksystems.com>dale.henrichs at gemtalksystems.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On 10/18/2015 06:49 PM, Jon Paynter wrote:
>>>>>
>>>>> .. and reading the docs further, I see extra args for windows:
>>>>>
>>>>> $GS_HOME/bin/installClient -c https 3.2.9 tode
>>>>>
>>>>>
>>>>> But that should be:
>>>>> $GS_HOME/bin/installClient -c https tode 3.2.9
>>>>>
>>>>>
>>>>> Also, since the failed install leaves files behind, a  "git reset
>>>>> --hard"  is needed to cleanup so the installer will work.
>>>>>
>>>>> Okay I've updated the docs ($GS_HOME/bin/updateGsDevKit -g should pick
>>>>> up the the new docs)
>>>>>
>>>>>
>>>>>
>>>>> ... so after the installer finishes im confused what to do next.  The
>>>>> docs say:
>>>>>
>>>>> To setup SSH port forwarding,
>>>>>
>>>>> ssh -L 44834:hostNameOrIp user at example.com
>>>>>
>>>>>
>>>>> but what do I use for 'hostnameOrIp' ?
>>>>> I assume I run that cmd on my gemstone server.   The local IP of my VM
>>>>> is 192.168.1.137
>>>>>
>>>>> So do I run something like this?
>>>>> ssh -L 56152:192.168.1.137 <then what goes here?>
>>>>>
>>>>> where "56152" is the netldi port number I got from running the
>>>>> 'stones' cmd on my server.
>>>>>
>>>>>
>>>>> I tried, but it did not work:
>>>>> gemstone at ubuntu:~$ ssh -L 56152:192.168.1.137 <user at host.com>
>>>>> user at host.com
>>>>> Bad local forwarding specification '56152:192.168.1.137'
>>>>>
>>>>>
>>>>> It sounds like we have a bit of work to do in this area for flow and
>>>>> correctness .... perhaps this doc[1] will get you going. The ssh statement
>>>>> for port forwarding should look like the following:
>>>>>
>>>>>   ssh 192.168.100.129 -l dhenrich -L 56152:<localhosOrIP>:56152
>>>>>
>>>>> I should mention that the current session descriptions include a field
>>>>> for the netldi port:
>>>>>
>>>>> TDSessionDescription {
>>>>>     #name : 'xx_329',
>>>>>     #stoneHost : 'foos.gemtalksystems.com',
>>>>>     #stoneName : 'xx_329',
>>>>>     #gemHost : 'foos.gemtalksystems.com',
>>>>>     #netLDI : 'xx_329_ldi',
>>>>>     #netLDIPort : '56152',
>>>>>     #gemTask : 'gemnetobject',
>>>>>     #userId : 'DataCurator',
>>>>>     #password : 'swordfish',
>>>>>     #osUserId : nil,
>>>>>     #osPassword : nil,
>>>>>     #dataDirectory : nil,
>>>>>     #backupDirectory :
>>>>> '/export/foos1/users/dhenrich/dev/_home/server/stones/xx_329/backups/',
>>>>>     #snapshotDirectory :
>>>>> '/export/foos1/users/dhenrich/dev/_home/server/stones/xx_329/snapshots/',
>>>>>     #gemstoneVersion : '3.2.9',
>>>>>     #gciLibraryName : nil,
>>>>>     #adornmentColor : nil,
>>>>>     #serverGitRoot : nil,
>>>>>     #serverTodeRoot : '/export/foos1/users/dhenrich/dev/_home'
>>>>>
>>>>> that you can set along with the name to ensure that your netldi will
>>>>> open on the same port every time ... if you use /etc/services, then you can
>>>>> leave the netLDIPort field empty.
>>>>>
>>>>> [1]
>>>>> <https://github.com/GsDevKit/gsDevKitHome/blob/master/docs/portForwardingForRemoteLogins.md>
>>>>> https://github.com/GsDevKit/gsDevKitHome/blob/master/docs/portForwardingForRemoteLogins.md
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> The client setup also says to copy some files from the server - but
>>>>> the folder doesnt exist
>>>>>
>>>>> From the server installation, copy the server specificaion file to the
>>>>> client. This file is
>>>>>
>>>>> $GS_HOME/shared/tode/sys/local/client/descriptions/<myServerNodeName>
>>>>>
>>>>> If you are using the same name as these examples, it will be named:
>>>>>
>>>>> $GS_HOME/shared/tode/sys/local/client/descriptions/devKit_329
>>>>>
>>>>> to the same path on the client node.
>>>>> but I cannot find a 'descriptions' folder anywhere under GsDevKit_home
>>>>>
>>>>> This is a case, where I changed the structure used by the scripts
>>>>> without updating the docs ... the correct location is:
>>>>>
>>>>>   $GS_HOME/sys/local/sessions
>>>>>
>>>>> I'll update the docs.
>>>>>
>>>>> Dale
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Glass mailing list
>>>> Glass at lists.gemtalksystems.com
>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>>>
>>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>>
>>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20151019/994c3a1b/attachment-0001.html>


More information about the Glass mailing list