[Glass] seaside.gemstone.com obsolete or down ?
Dale Henrichs
dale.henrichs at gemtalksystems.com
Mon Jan 6 13:04:28 PST 2020
Marten,
With the information that you are using upgradeStone and upgrading to
3.5.1, I looked at the Travis-CI test matrix[1] and noticed that I had
only added upgrade coverage for 3.3.9 to 3.5.1. So I had no test
coverage for 3.4.x to 3.5.1 on Travis-CI. I have adjusted that by adding
upgrade coverage for 3.2.17, 3.3.6, and 3.4.3 to 3.5.1 ... and those new
tests are all passing.
I also ran my own local test of a 3.4.3 stone to 3.5.1 using
`upgradeStone gs_343 gs_343_351 3.5.1` and it completed successfully:
Starting GemStone/S 64 3.x Seaside upgrade.
Note: This script should be run AFTER upgradeImage has been run.
SessionMethods will be enabled and all code included in the
GLASS, GLASS1 or tODE project will be reloaded.
There are 4 phases performed by this script and each script is
performed in its own topaz session:
1. As SystemUser, install GsDevKit_upgrade code and
GsuAbstractGsDevKitUpgrade>>prepareImage.
2. As DataCurator, GsuAbstractGsDevKitUpgrade>>prepareImage_pragma_user
3. As SystemUser, GsuAbstractGsDevKitUpgrade>>prepareImage_pragma_systemuser
4. As DataCurator, GsuAbstractGsDevKitUpgrade>>prepareImage_user and
GsuAbstractGsDevKitUpgrade>>prepareGsDevKitImage
For additional details about the work performed during each phase see
https://github.com/GsDevKit/GsDevKit_upgrade .
Stone name is gs_343_351.
Press the return key to continue...
Mon Jan 6 10:13:01 PST 2020
Starting GLASS/GLASS1/GsDevKit/TODE upgrade for gs_343_351...
############################################################################
1. As SystemUser, install GsDevKit_upgrade code and GsuAbstractGsDevKitUpgrade>>prepareImage.
############################################################################
2. As DataCurator, GsuAbstractGsDevKitUpgrade>>prepareImage_pragma_user
############################################################################
3. As SystemUser, GsuAbstractGsDevKitUpgrade>>prepareImage_pragma_systemuser
############################################################################
4. As DataCurator, GsuAbstractGsDevKitUpgrade>>prepareImage_user and GsuAbstractGsDevKitUpgrade>>prepareGsDevKitImage
############################################################################
5. As SystemUser, Remove globals created during upgrade.
GsDevKit Upgrade completed (GLASS/GLASS1/GsDevKit/tODE). No errors detected.
Unfortunately, you did not supply the GemStone version that you are
upgrading from ... I upgraded from 3.4.3 and the closest I can come to a
pattern of log entries in upgradeSeasideImage.out (you don't mention the
name of the log file where you gathered your information either) is the
following:
--------------------
Starting Standard GsDevKit upgrade: prepare gsdevkit image as DataCurator
--------------------
Prepare gsdevkit image
update dbf history for upgrade start
Prepare gsdevkit - patch bug 45952
Prepare gsdevkit - create existing configuration list
create existing configuration list (commit)
ConfigurationOfGsMisc
ConfigurationOfGsCore
existing configuration collected (2)
Prepare gsdevkit - enableSessionMethods
session methods enabled (commit)
Prepare gsdevkit - clear Monticello caches
Monticello caches cleared (commit)
Prepare gsdevkit - Metacello caches NOT cleared
Patching ...Behavior>>compileMethod:category:
unload 2.x only packages
reset Monticello package registry
Prepare gsdevkit - reset existing global state
update dbf history for upgrade finish
Prepare gsdevkit - load GsDevKit application code
load BaselineOfMetacello and BaselineOfTode (default)
removing configuration classes
ConfigurationOfGsMisc
ConfigurationOfGsCore
done removing configuration classes (2)
--------------------
Reloading Project 'Metacello' loads: anArray( 'default', 'Tests')
--------------------
--transcript--'Fetched -> BaselineOfMetacello-EstebanLorenzano.97 --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository [bc444b6c:issue_504] --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository'
--transcript--'Loaded -> BaselineOfMetacello-EstebanLorenzano.97 --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository [bc444b6c:issue_504] --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository'
--transcript--'Fetched -> BaselineOfMetacello-EstebanLorenzano.97 --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository [bc444b6c:issue_504] --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository'
--transcript--'Loaded -> BaselineOfMetacello-EstebanLorenzano.97 --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository [bc444b6c:issue_504] --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository'
--transcript--'Loading baseline of BaselineOfMetacello...'
--transcript--'Warning: LOCK ENFORCED: Attempt to ''load with conflicts'' new project: ''BaselineOfFileTree [baseline] from github://dalehenrich/filetree:gemstone2.4/repository'' when existing project: ''BaselineOfFileTree [baseline] from filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/filetree/repository'' is locked. New project not loaded. Use #onLock: to intercept.'
--transcript--'Warning: LOCK ENFORCED: Attempt to ''load with conflicts'' new project: ''BaselineOfFileTree [baseline] from github://dalehenrich/filetree:gemstone2.4/repository'' when existing project: ''BaselineOfFileTree [baseline] from filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/filetree/repository'' is locked. New project not loaded. Use #onLock: to intercept.'
--transcript--'Fetched -> Metacello-Base-topa.124 --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository [bc444b6c:issue_504] --- filetree:///home/dhenrich/rogue/_homes/rogue/_home/shared/repos/metacello-work/repository'
--transcript--'Project: Gofer stable'
--transcript--' [1.0.5.4]'
--transcript--'Fetched -> Gofer-Core.gemstone-dkh.138 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello'
The `Reloading Project 'Metacello'` log entry is very curious, the fact
that line is different implies that you are not using the same version
of GemStone to upgrade from or ???
The critical information is that in my case we are (successfully)
installing Gofer 1.0.5.4 and in your case you are (unsuccessfully)
installing Gofer 1.0.5.1 .... it is possible that this difference is due
to the version of GemStone that you are starting with ... It is also
possible that this is due to the version of GLASS that you are using in
whatever version of GemStone you are using ...
Here's screenshot of the versions of all the projects that am using
prior to the upgrade (from 3.4.3):
Here's a screenshot of the versions of all of the projects that I end up
using after the upgrade:
You can see that I am using upgrade_351 (commit d63666a) of
GsDevKit_home which is a recent branch off of the master branch ... so
if you are not using the latest commit on the master branch of
GsDevKit_home, I would recommend that update again (using
`updateGsDevKit -gd`)...
Also it is worth noting that you _should_ be using a fairly recent
version of GLASS (commit 1c6a7a6a is the latest commit on both the
master and issue_120 branches) ... and you should update whatever
version GemStone you are using to this version before attempting an
upgrade to GemStone 3.5.1 ... For example, if you are not using commit
007a114 (June of last year) or later of GLASS:
The version of GLASS that you _ARE_ using will not function correctly
with 3.5.0 ....
So again please try to answer the following questions as completely as
possible:
1. What version of GemStone are you using in your `update_test` stone?
2. Please provide a complete list of the SHAs for all of the projects
that you have loaded in the stone that you are upgrading from .... a
snapshot of the tODE project list is the best ... presumably you
have tODE loaded in your stone, so if you aren't prepared to connect
using a tODE client, I can supply you with a doit that you can run
to get the same information from either topaz (if you don't have
tODE installed) or tODE (via the todeIt script)
With this information I should be able to reproduce your issue locally
and provide information on how to proceed ...
Dale
[1] https://travis-ci.org/GsDevKit/GsDevKit_home/builds/629825252
On 1/5/20 1:14 PM, Marten Feldtmann wrote:
> Hello Dale,
>
> here are some more informations. Actually its an update of a 3.4.x
> database to 3.5.1 - which failed. I made another test with upgradinig
> the database via
>
> upgradeStone update_test update_test3 3.5.1
>
> and here I get also a problem:
>
> ||||
> Stone name is update_test3.
> ||||
> Press the return key to continue...
> So 5. Jan 22:11:07 CET 2020
> Starting upgrade...
> ||||
> Upgrade completed. No errors detected.
> STARTING upgradeSeasideImage
>
> |...|
> |Prepare gsdevkit - patch bug 45952|
> |Prepare gsdevkit - create existing configuration list|
> |create existing configuration list (commit)|
> |ConfigurationOfGsMisc|
> |ConfigurationOfGsCore|
> |existing configuration collected (2)|
> |Prepare gsdevkit - enableSessionMethods|
> |session methods enabled (commit)|
> |Prepare gsdevkit - clear Monticello caches|
> |Monticello caches cleared (commit)|
> |Prepare gsdevkit - Metacello caches NOT cleared|
> |Patching ...Behavior>>compileMethod:category:|
> |unload 2.x only packages|
> |reset Monticello package registry|
> |Prepare gsdevkit - reset existing global state|
> |update dbf history for upgrade finish|
> |Prepare gsdevkit - load GsDevKit application code|
> |load BaselineOfMetacello and BaselineOfGLASS1 (default)|
> |removing configuration classes|
> |ConfigurationOfGsMisc|
> |ConfigurationOfGsCore|
> |done removing configuration classes (2)|
> |--------------------|
> |Reloading Project 'Metacello'|
> |--------------------|
> |--transcript--'Fetched -> BaselineOfMetacello-EstebanLorenzano.97 ---
> github://dalehenrich/metacello-work:master/repository [a7e9323:master]
> --- github://dalehenrich/metacello-work:master/repository'|
> |--transcript--'Loaded -> BaselineOfMetacello-EstebanLorenzano.97 ---
> github://dalehenrich/metacello-work:master/repository [a7e9323:master]
> --- github://dalehenrich/metacello-work:master/repository'|
> |--transcript--'Fetched -> BaselineOfMetacello-EstebanLorenzano.97 ---
> github://dalehenrich/metacello-work:master/repository [a7e9323:master]
> --- github://dalehenrich/metacello-work:master/repository'|
> |--transcript--'Loaded -> BaselineOfMetacello-EstebanLorenzano.97 ---
> github://dalehenrich/metacello-work:master/repository [a7e9323:master]
> --- github://dalehenrich/metacello-work:master/repository'|
> |--transcript--'Loading baseline of BaselineOfMetacello...'|
> |--transcript--'Fetched -> BaselineOfFileTree-dkh.4 ---
> github://dalehenrich/filetree:gemstone2.4/repository
> [d7eee41:gemstone2.4] ---
> github://dalehenrich/filetree:gemstone2.4/repository'|
> |--transcript--'Loaded -> BaselineOfFileTree-dkh.4 ---
> github://dalehenrich/filetree:gemstone2.4/repository
> [d7eee41:gemstone2.4] ---
> github://dalehenrich/filetree:gemstone2.4/repository'|
> |--transcript--'Fetched -> Metacello-Base-topa.124 ---
> github://dalehenrich/metacello-work:master/repository [a7e9323:master]
> --- github://dalehenrich/metacello-work:master/repository'|
> |--transcript--'Project: Gofer stable'|
> |--transcript--' [1.0.5.1]'|
> |--transcript--'Retrying
> ''http://seaside.gemstone.com/ss/metacello/?C=M;O=D'' (1)
> ''SpSocketError: Socket connect error: connect(14,64.20.104.5,port=80)
> failed with errno=110,ETIMEDOUT, Connection timed out'''|
> |--transcript--'Retrying
> ''http://seaside.gemstone.com/ss/metacello/?C=M;O=D'' (2)
> ''SpSocketError: Socket connect error: connect(15,64.20.104.5,port=80)
> failed with errno=110,ETIMEDOUT, Connection timed out'''|
> |--transcript--'Retrying
> ''http://seaside.gemstone.com/ss/metacello/?C=M;O=D'' (3)
> ''SpSocketError: Socket connect error: connect(16,64.20.104.5,port=80)
> failed with errno=110,ETIMEDOUT, Connection timed out'''|
> |--transcript--'...RETRY->Gofer-Core.gemstone-dkh.135'|
> |--transcript--'Retrying
> ''http://seaside.gemstone.com/ss/metacello/?C=M;O=D'' (1)
> ''SpSocketError: Socket connect error: connect(18,64.20.104.5,port=80)
> failed with errno=110,ETIMEDOUT, Connection timed out'''|
> |--transcript--'Retrying
> ''http://seaside.gemstone.com/ss/metacello/?C=M;O=D'' (2)
> ''SpSocketError: Socket connect error: connect(19,64.20.104.5,port=80)
> failed with errno=110,ETIMEDOUT, Connection timed out'''|
>
> My software is working within the 3.4.x database. I can create a new
> fresh database and all software is loaded.
>
> Marten
>> Dale Henrichs via Glass <glass at lists.gemtalksystems.com> hat am 5.
>> Januar 2020 um 20:22 geschrieben:
>>
>> Marten,
>>
>> seaside.gemstone.com has been off-line for several years now and when
>> it was taken off line permanently I did a sweep of a number of the
>> public packages and cleaned up all of the references to
>> seaside.gemstone.com that created build problems, so things have been
>> running smoothly without seaside.gemstone.com for a couple of years
>> now ...
>>
>> There is a GsDevKit_home Travis-CI job that runs monthly[1] and there
>> are a number of upgrade tests that are run. The last (greeen) run was
>> 10 days ago ...
>>
>> According to the log information you have provided, commit a7e9323 of
>> https://github.com/dalehenrich/metacello-work is being used and that
>> is the latest version of the repository (last commit as of June of
>> last year) and the last Travis-CI cron job ran 5 days ago[2]
>>
>> The latest GsUpgrader-Core package on
>> http://ss3.gemtalksystems.com/ss/gsUpgrader.html was
>> GsUpgrader-Core-dkh.121.mcz and it was updated in February of 2016.
>> Your log does not indicate which version of GsUpgrader-Core was
>> actually downloaded, so it _is_ possible that you've used older
>> version of GsUpgrader-Core, but I'm going to guess that the stone you
>> are working with was created sometime since 2016 so I'm going to
>> assume that you were using the latest GsUpgrader-Core package. If you
>> print the result of running:
>>
>> MCWorkingCopy allManagers select: [:wc |
>> wc packageName = 'GsUpgrader-Core']
>>
>> after the `Gofer load` we'll know for sure.
>>
>> Something could have changed in the last 5-10 days to create a
>> problem or there is something unique to the stone that you are running.
>>
>> When I look at the travis log for a successful 3.4.3 build[3] and
>> compare the package versions downloaded to the ones listed in your
>> log, they all match ... the first package downloaded (successfully)
>> in the Travis-Ci job is Metacello-Core:
>>
>> Loaded -> BaselineOfMetacello-EstebanLorenzano.97 ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repository
>> [a7e93239:master] ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repositoryLoading
>> baseline of BaselineOfMetacello...Warning: LOCK ENFORCED: Attempt
>> to 'load with conflicts' new project: 'BaselineOfFileTree
>> [baseline] from
>> github://dalehenrich/filetree:gemstone2.4/repository' when
>> existing project: 'BaselineOfFileTree [baseline] from
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/filetree/repository'
>> is locked. New project not loaded. Use #onLock: to
>> intercept.Warning: LOCK ENFORCED: Attempt to 'load with
>> conflicts' new project: 'BaselineOfFileTree [baseline] from
>> github://dalehenrich/filetree:gemstone2.4/repository' when
>> existing project: 'BaselineOfFileTree [baseline] from
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/filetree/repository'
>> is locked. New project not loaded. Use #onLock: to
>> intercept.Fetched -> Metacello-Base-topa.124 ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repository
>> [a7e93239:master] ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repositoryProject:
>> Gofer stable [1.0.5.4]Fetched ->
>> Metacello-Core-EstebanLorenzano.832 ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repository
>> [a7e93239:master] ---
>> filetree:///home/travis/smalltalkCI-master/_builds/GsDevKit_home/shared/repos/metacello-work/repository
>>
>> and it is downloaded from the the same repository that
>> BaselineOfMetacello is loaded from (which is filetree in the case of
>> the Travis-Ci) and _SHOULD_ be the github repository used by
>> BaselineOfMetacello in your case ...
>>
>> There are no references to seaside.gemstone.com in
>> BaselineOfMetacello-EstebanLorenzano.97, so the mystery is why and
>> what package are you trying to download.
>>
>> You are not using a standard GsDevKit_home script (otherwise you
>> would be using the git repositories that are downloaded as part of
>> the GsDevKit_home system), but that should be okay, but there is
>> clearly something unique about the stone that you are using,
>> otherwise things would be working as expected.
>>
>> Sooo, in order for me to try to reproduce your problem and help you,
>> I need the following information:
>>
>> 1. What version of GemStone are you using?
>> 2. What extent are you using?
>> 1. is it freshly copied from $GEMSTONE/bin/,
>> 2. is it an existing extent that you've been using for awhile
>> 3. What are you intending to do?
>> 1. Using GsUpgrader is usually a step along the way to
>> installing/upgrading GLASS and it is important to know which
>> path you are one ... since it _can_ be important to know
>> 4. I'd also like to know if you are doing something that you have
>> done in the past
>> 1. Are you following a series of steps that have been proven to
>> work for you in the past?
>> 1. if so, what are the series of steps that you're following
>> 2. Are trying to do something that you've never tried before
>> 1. If so, what is it that you are trying to do ... three may
>> already be an existing GsDevKit_home script that does
>> what you want ..
>>
>> Please try to give me as much information as possible in answering
>> all of these questions... otherwise it is very difficult for me to
>> provide meaningful help ...
>>
>> Dale
>>
>>
>>
>>
>>
>> [1] https://travis-ci.org/GsDevKit/GsDevKit_home/builds/629825252
>> [2] https://travis-ci.org/Metacello/metacello/builds/631440571
>> [3]
>> https://travis-ci.org/Metacello/metacello/jobs/631440582#L1159-L1173https://travis-ci.org/Metacello/metacello/jobs/631440582#L1159-L1173
>>
>>
>> On 1/5/20 8:14 AM, Marten Feldtmann via Glass wrote:
>>> Ok, than it means that the whole stone upgrading stuff within
>>> GsDevKit_home is not working any more ? upgradeSeasideImage is also
>>> executing these commands ...
>>>
>>> This network stuff is a real mess ....
>>>
>>> _______________________________________________
>>> Glass mailing list
>>> Glass at lists.gemtalksystems.com <mailto:Glass at lists.gemtalksystems.com>
>>> https://lists.gemtalksystems.com/mailman/listinfo/glass
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> https://lists.gemtalksystems.com/mailman/listinfo/glass
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gemtalksystems.com/mailman/private/glass/attachments/20200106/b571679c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gkglhicbeeaeieco.png
Type: image/png
Size: 133138 bytes
Desc: not available
URL: <https://lists.gemtalksystems.com/mailman/private/glass/attachments/20200106/b571679c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cnomaknlacjmfdho.png
Type: image/png
Size: 210059 bytes
Desc: not available
URL: <https://lists.gemtalksystems.com/mailman/private/glass/attachments/20200106/b571679c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ceopodeaegnjhnbd.png
Type: image/png
Size: 55772 bytes
Desc: not available
URL: <https://lists.gemtalksystems.com/mailman/private/glass/attachments/20200106/b571679c/attachment-0005.png>
More information about the Glass
mailing list