[Glass] Starting Seaside Gems in GS 3.2.8.1

[Alejandro Zuzek via Glass]

Hi Dale,

I am still unable to make the upgraded image work, that is, I still cannot
start the Seaside Gems. I rerun the whole installation process on a backup
of my 3.1.0.4 system, including running upgradeImage and
upgradeSeasideImage. No errors were reported there, by the
WAGemStoneRunSeasideGems
class still doesn't understand #'startGemServerOn:

I tried to reload the Seaside Adaptors with this code:

MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [
  ConfigurationOfMetacello project updateProject.
  ConfigurationOfMetacello loadLatestVersion.
  Gofer project load: 'Seaside30' group: #('Seaside-Adaptors-FastCGI'
'Seaside-Adaptors-Swazoo').
].

but I get this error:

--transcript--'redirecting to
http://seaside.gemtalksystems.com/ss/Seaside30/Seaside-Adaptors-FastCGI-dkh.26.mcz
'
--transcript--'Fetched -> Seaside-Adaptors-FastCGI-dkh.26 ---
http://seaside.gemstone.com/ss/Seaside30 ---
http://seaside.gemstone.com/ss/Seaside30'
ERROR 2718 , a ArgumentError occurred (error 2718), (argument at: 1)
contains codePoint 16rd800 not legal for Unicode (ArgumentError)

Is it possible that the .26 version of FastCGI is broken (illegal
character?) and that this is preventing upgradeSeasideScript to reload
FastCGI code correctly?

Thanks,

Alejandro

On Sun, Sep 6, 2015 at 11:50 PM, Dale Henrichs via Glass <
glass at lists.gemtalksystems.com> wrote:

> Alejandro,
>
> It sounds like you didn't reload your application code after the
> upgradeSeasideImage completed - your "application code" includes anything
> that was loaded on top of GLASS, including running upgradeImage, loading
> Seaside code and your Seaside application itself ...
>
> I have written an upgradeGemStone script[1] (on the dev branch) for
> automating the upgrade steps (the script uses a user-specified tODE shell
> script to load your application code) and you might want to look at the
> script itself for inspiration ... feel free to ask additional questions.
>
> Dale
>
> [1] https://github.com/GsDevKit/gsDevKitHome/blob/dev/bin/upgradeGemStone
>
> On 9/5/15 4:05 PM, Alejandro Zuzek via Glass wrote:
>
>> I have just migrated from GS 3.1.0.4 to GS 3.2.8.1 (I followed the
>> procedure,
>> including running upgradeImage and upgradeSeasideImage scripts). In
>> 3.1.0.4
>> I would start the Seaside gems with this command:
>>
>> runSeasideGems30 start WAFastCGIAdaptor "9001 9002 9003"
>>
>> When I run the same command in the 3.2.8.1 version, the Gems don't start
>> and
>> in the start logs (for instance in WAFastCGIAdaptor_start-9003.log) I see
>> this error:
>>
>> a MessageNotUnderstood occurred (error 2010), a WAGemStoneRunSeasideGems
>> class does not understand  #'startGemServerOn:'
>>
>> Furthermore, in the new versión while the class WAGemStoneRunSeasideGems
>> exists, it doesn't have any methods at all.
>>
>> In the upgradeSeasideImage output (upgradeTo3x.out) I see many clases
>> being
>> loaded, but no trace of WAGemStoneRunSeasideGems). The script ended
>> sucessfully and I don't see any errors in the output log.
>>
>> Was there a problem in the upgrade of my image or is this intended and
>> there
>> is now a new procedure to start Seaside gems?
>>
>> Thanks,
>>
>> Alejandro
>>
>>
>>
>> --
>> View this message in context:
>> http://forum.world.st/Starting-Seaside-Gems-in-GS-3-2-8-1-tp4848347.html
>> Sent from the GLASS mailing list archive at Nabble.com.
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150911/7e6e6879/attachment.html>