seaside.gemstone.com obsolete or down ?
Locked
seaside.gemstone.com obsolete or down ?
 
|
[Info]: Gave this process preference for OOM killer: wrote to /proc/18387/oom_score_adj value 250
[05.01.2020 16:31:06.624 CET]
gci login: currSession 1 linked session
successful login
fileformat is now utf8
sourcestringclass is now Unicode16
topaz 1> doit
Gofer new
package: 'GsUpgrader-Core';
url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
load.
(Smalltalk at: #GsUpgrader) upgradeGrease.
%
--transcript--'======================'
--transcript--'=====Metacello Preview already loaded'
--transcript--'======================'
--transcript--'=====Upgrading 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(12,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(13,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(14,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(16,64.20.104.5,port=80) failed with errno=110,ETIMEDOUT, Connection timed out'''
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
References to gemstone.com should be replaced with gemtalksystems.com.
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
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 [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
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:
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:
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]
<a class="moz-txt-link-freetext" href="https://travis-ci.org/Metacello/metacello/jobs/631440582#L1159-L1173https://travis-ci.org/Metacello/metacello/jobs/631440582#L1159-L1173">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:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
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 <[hidden email]> hat am 5. Januar 2020 um 20:22 geschrieben: _______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
The errors I posted happened in the newly created update-3.5.1 database, which of course has strange content.
Marten
Dale Henrichs via Glass <[hidden email]> hat am 5. Januar 2020 um 20:22 geschrieben: _______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
I have found referencse to gemstone.com in the new updated 3.5.1 database:
ConfigurationOfGoferProjectLoader class>postLoadGSDoIt10alpha21
ConfigurationOfGofer class>>baseline100:, baseline1021:,baseline1051:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
And the reasons for that are, that ConfigurationOfGofer is dkh.39 (which references gemstone.com) and NOT dkh.45 (which references seaside.gemtalksystems.com). Now th question is, WHY is not a newer version of Gofer loaded ...
Marten
Marten Feldtmann via Glass <[hidden email]> hat am 5. Januar 2020 um 22:54 geschrieben: _______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
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:
With this information I should be able to reproduce your issue locally and provide information on how to proceed ... Dale On 1/5/20 1:14 PM, Marten Feldtmann
wrote:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
On 1/5/20 1:17 PM, Marten Feldtmann
wrote:
I'm not sure what you are telling me here? Why would a newly created 3.5.1 stone have "strange content"? Dale
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
That is not unusual, in my upgraded gs_343_351 stone there are references to seaside.gemstone.com all over:
However, these references should not be tripped across if you are
using the latest version of GLASS and the latest upgrade scripts
... Answering these questions should get us on track to understanding
your issue:
Dale
On 1/5/20 1:54 PM, Marten Feldtmann
wrote:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
This is interesting, but the critical information that is still missing is what version of GemStone are you starting your upgrade with and what version of GLASS do you have loaded in the image BEFORE starting the upgrade:
If I had both of these pieces of information, I would have a very
good chance of being able to reproduce your problem and be on my
way to providing a solution ... Dale On 1/5/20 2:14 PM, Marten Feldtmann
wrote:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
First this info: Its the version 3.4.0 I started from ... and ConfigurationOfGofer is dkh.39 is there loaded and in 3.5.1 its still dkh.39
Marten
Dale Henrichs <[hidden email]> hat am 6. Januar 2020 um 22:19 geschrieben: _______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
Ok, some further information.
a) I put the update code of Grease and loading of Glass not before doing the update ... no success. The problem is, that Gofer is NOT updated from 1.0.5.1 to 1.0.5.4
b) Then I installed Gofer 1.0.5.4 manually in the 3.4.0 database and the update does much more until an error occurs:
--transcript--'Loading baseline of BaselineOfGLASS1...'
--transcript--'...RETRY->BaselineOfGrease' --transcript--'...RETRY->BaselineOfGrease' --transcript--'gofer repository error: ''GoferRepositoryError: a MessageNotUnderstood occurred (error 2010), a FastUUIDGenerator class does not understand #''''default''''''...ignoring' --transcript--'...FAILED->BaselineOfGrease' Error 2710 , a MetacelloPackageSpecResolutionError occurred (error 2710), , Could not resolve: BaselineOfGrease [BaselineOfGrease] in cache github://GsDevKit/Grease:master/repository ERROR: 'GoferRepositoryError: a MessageNotUnderstood occurred (error 2010), a FastUUIDGenerator class does not understand #''default''' (MetacelloPackageSpecResolutionError) ERROR: UNEXPECTED ERROR
Here the upgradeLog:
--- _______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
Marten, In order to complete my analysis of your db, send me a copy of
the script that you use to update GLASS and the other projects in
the data base. I've downloaded a copy of your test db and I was able to
reproduce your error. I ran a test upgrade of an extent0.seaside.dbf for 3.4.0 and that upgrade completed successfully. I ran a test upgrade of a tODE stone built against 3.4.0 with a recent version of the GLASS git repository (commit 1c6a7a6a) and that upgrade completed successfully. Dale On 1/6/20 10:21 PM, Marten Feldtmann
wrote:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: seaside.gemstone.com obsolete or down ?
|
|
In reply to this post by GLASS mailing list
Marten, I have finally found a solution to your upgrade issue: remove `ConfigurationOfGofer` from you image prior to running the upgradeStone, using `ConfigurationOfGofer removeFromSystem. System commit`. There are additional details in this bug report[1] and I have submitted an internal GemStone bug 48510 "upgradeStone fails (referencing seaside.gemstone.com) for a stone built using a custom script" to track when the bug has been fixed in the GemStone release (looks like the fix will be in GemStone 3.5.2) ... Let me now if you have any additional issues, Dale [1] https://github.com/GsDevKit/GsDevKit_home/issues/280#issuecomment-574429989 On 1/6/20 10:21 PM, Marten Feldtmann
wrote:
_______________________________________________ Glass mailing list [hidden email] https://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |