[Seaside] Seaside on EC2 Amazon Service
Nick Ager
nick.ager at gmail.com
Thu Oct 13 13:55:39 UTC 2011
Hi Larry,
So the problem seems to be in the /etc/init.d/gemstone script.
In the meantime if you want to start Gemstone.
cd /opt/gemstone/product/seaside/bin
startGemstone
startnet
runSeasideGems30 start WAFastCGIAdaptor 9001
and to stop:
runSeasideGems30 stop WAFastCGIAdaptor 9001
stopnetldi
stopGemstone
Nick
On 13 October 2011 14:47, Lawrence Kellogg <mac.hive at me.com> wrote:
>
> On Oct 13, 2011, at 9:44 AM, Nick Ager wrote:
>
> Hi Larry,
>
> I'm mystified. One last idea, try:
>
> cd /opt/gemstone/product/seaside/bin
> startGemstone
>
> Any luck?
>
> BTW I assume you downloaded Gemstone 2.4.4.1, not 3.0Beta...
>
>
>
> Well, that seems to work, I think....
>
> stopstone[Info]: Stone repository monitor "seaside" has been stopped.
> startstone[Info]: GemStone version '2.4.4.1'
> startstone[Info]: Starting Stone repository monitor "seaside".
> startstone[Info]: GEMSTONE is: "/opt/gemstone/product".
> startstone[Warning]: /usr/lib64/libposix-aio.so not found, using librt.so
> startstone[Info]:
>
> GEMSTONE_SYS_CONF=/opt/gemstone/GemStone64Bit2.4.4.1-x86_64.Linux/seaside/data/system.conf
>
> GEMSTONE_EXE_CONF=/opt/gemstone/GemStone64Bit2.4.4.1-x86_64.Linux/seaside/data/seaside.conf
> startstone[Info]: Log file is '/opt/gemstone/log/seaside.log'.
> startstone[Info]: GemStone server 'seaside' has been started.
>
>
> [seasideuser at domU-12-31-39-14-08-6B bin]$ gslist -l
> Status Version Owner Pid Port Started Type Name
> ------ --------- --------- ----- ----- ------------ ------ ----
> exists 2.4.4.1 seasideuser 20921 43237 Oct 13 13:45 cache
> seaside at domU-12-31-39-14-08-6B.compute-1.internal
> exists 2.4.4.1 seasideuser 20920 49298 Oct 13 13:45 Stone seaside
>
> Should the ldi process be running? Yes, it is version 2.4.4.1 according to
> this....
>
> Larry
>
>
> Nick
>
> On 13 October 2011 14:10, Lawrence Kellogg <mac.hive at me.com> wrote:
>
>>
>> On Oct 13, 2011, at 8:56 AM, Nick Ager wrote:
>>
>> Hi Larry,
>>
>> If you examine your /etc/init.d/gemstone what user does the script use to
>> execute the Gemstone scripts. In mine the key lines are:
>>
>> RUNASUSER="seasideuser"
>> GEMSTONE_BIN="/opt/gemstone/product/seaside/bin"
>> GEMSTONE_STOPNET="/opt/gemstone/product/bin"
>>
>> # Start GemStone
>> startGemStone() {
>> logger "Starting GemStone server: "
>> daemon --user=$RUNASUSER $GEMSTONE_BIN/startGemstone
>> daemon --user=$RUNASUSER $GEMSTONE_BIN/startnet
>>
>> the environment that 'startGemstone' and friends use will be defined by
>> the environment for user $RUNASUSER
>>
>>
>>
>> Yes, my RUNASUSER is also defined as seasideuser, but I still have the
>> same problem.
>>
>> seasideuser at domU-12-31-39-14-08-6B init.d]$ sudo /etc/init.d/gemstone
>> restart
>> echoing GEMSTONE:
>> /opt/gemstone/product
>> seasideuser <<<<<<<<<<<<<<<------------ echo $RUNASUSER here
>> Stopping Gems...
>> No PID file found for gem on port 9001, not running?
>> No PID file found for gem on port 9002, not running?
>> No PID file found for gem on port 9003, not running?
>> No PID file for for the maintenance gem, not running?
>> No PID file for for the service gem, not running?
>> [ OK ]
>> stopnetldi[Info]: GemStone version '2.4.4.1'
>> stopnetldi[Info]: Server 'gs64ldi' is not running.
>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret[ OK ]
>> [FAILED]
>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret
>> /opt/gemstone/product/seaside/bin/startnet: line 8: /bin/startnetldi: No
>> such file or directory
>> [ OK ]
>> Starting Gems....
>> Starting WAFastCGIAdaptor gem on port 9001
>>
>>
>> Nick
>>
>>
>> On 13 October 2011 11:24, Lawrence Kellogg <mac.hive at me.com> wrote:
>>
>>>
>>> On Oct 13, 2011, at 4:20 AM, Nick Ager wrote:
>>>
>>> Hi Larry
>>>
>>> I suspect that $GEMSTONE isn't defined in the context of the startup
>>> script. You could try adding:
>>>
>>> echo 'echoing GEMSTONE:'
>>> echo $GEMSTONE
>>>
>>> within the startup script and see if you get any output. Otherwise I'm at
>>> a loss.
>>>
>>>
>>> You're right, the variable is not defined in the context of the startup
>>> script.
>>> So, I added it to the gemstone startup script but it still cannot locate
>>> the files! Why?
>>>
>>> I'm at a loss too.... How strange.
>>>
>>> Here are all my environment variables:
>>>
>>> [seasideuser at domU-12-31-39-14-08-6B init.d]$ set | grep gem
>>> DYLD_LIBRARY_PATH=/opt/gemstone/product/lib:
>>> GEMSTONE=/opt/gemstone/product
>>> GEMSTONE_DATADIR=/opt/gemstone/product/seaside/data
>>> GEMSTONE_EXE_CONF=/opt/gemstone/product/seaside/data
>>> GEMSTONE_KEYFILE=/opt/gemstone/product/seaside/etc/gemstone.key
>>> GEMSTONE_LOGDIR=/opt/gemstone/log
>>> GEMSTONE_SYS_CONF=/opt/gemstone/product/seaside/data/system.conf
>>> LD_LIBRARY_PATH=/opt/gemstone/product/lib:
>>> MANPATH=/opt/gemstone/product/doc:
>>> OLDPWD=/opt/gemstone/product
>>>
>>> PATH=/opt/gemstone/product/bin:/opt/gemstone/product/seaside/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin:/home/seasideuser/bin
>>> _=gemstone
>>>
>>>
>>> Nick
>>>
>>> On 13 October 2011 03:23, Lawrence Kellogg <mac.hive at me.com> wrote:
>>>
>>>> I do have a gemstone.secret file
>>>>
>>>>
>>>> [seasideuser at domU-12-31-39-14-08-6B ~]$ ls
>>>> $GEMSTONE/seaside/etc/gemstone.secret
>>>> /opt/gemstone/product/seaside/etc/gemstone.secret
>>>> [seasideuser at domU-12-31-39-14-08-6B ~]$
>>>>
>>>>
>>>> so I'm not sure why the restart script is complaining....
>>>>
>>>> stopnetldi[Info]: Server 'gs64ldi' is not running.
>>>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret[ OK ]
>>>> [FAILED]
>>>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret
>>>> /opt/gemstone/product/seaside/bin/startnet: line 8: /bin/startnetldi: No
>>>> such file or directory
>>>>
>>>> It also says this is missing:
>>>>
>>>> $GEMSTONE/bin/startnetldi
>>>>
>>>> but here it is:
>>>>
>>>> [seasideuser at domU-12-31-39-14-08-6B bin]$ ls -l
>>>> $GEMSTONE/bin/startnetldi
>>>> -r-xr-xr-x 1 seasideuser seasideuser 311158 Jul 13 2010
>>>> /opt/gemstone/product/bin/startnetldi
>>>> [seasideuser at domU-12-31-39-14-08-6B bin]$
>>>>
>>>>
>>>> Confusing....
>>>>
>>>> Larry
>>>>
>>>>
>>>>
>>>> On Oct 12, 2011, at 5:30 PM, Nick Ager wrote:
>>>>
>>>> Hi Larry,
>>>>
>>>> It looks as Gemstone can't find the password file: gemstone.secret
>>>>
>>>> I'd suspect that the environment variable $GEMSTONE isn't setup
>>>> correctly. On my installation:
>>>>
>>>> echo $GEMSTONE
>>>>
>>>> gives:
>>>>
>>>> /opt/gemstone/product
>>>>
>>>> also if I try
>>>>
>>>> sudo echo $GEMSTONE
>>>>
>>>> I get the same result. Do you see something similar?
>>>>
>>>> Nick
>>>>
>>>> On 12 October 2011 21:23, Lawrence Kellogg <mac.hive at me.com> wrote:
>>>>
>>>>> Hello Nick,
>>>>> Well, I'm up to testing out my Gemstone install.
>>>>>
>>>>> sudo /etc/init.d/gemstone restart
>>>>> Stopping Gems...
>>>>> No PID file found for gem on port 9001, not running?
>>>>> No PID file found for gem on port 9002, not running?
>>>>> No PID file found for gem on port 9003, not running?
>>>>> No PID file for for the maintenance gem, not running?
>>>>> No PID file for for the service gem, not running?
>>>>> [ OK ]
>>>>> stopnetldi[Info]: GemStone version '2.4.4.1'
>>>>> stopnetldi[Info]: Server 'gs64ldi' is not running.
>>>>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret[ OK ]
>>>>> [FAILED]
>>>>> Missing password file $GEMSTONE/seaside/etc/gemstone.secret
>>>>> /opt/gemstone/product/seaside/bin/startnet: line 8: /bin/startnetldi:
>>>>> No such file or directory
>>>>> [ OK ]
>>>>> Starting Gems....
>>>>> Starting WAFastCGIAdaptor gem on port 9001
>>>>> Starting WAFastCGIAdaptor gem on port 9002
>>>>> Starting WAFastCGIAdaptor gem on port 9003
>>>>> Starting maintenance gem
>>>>> Starting service gem
>>>>> [ OK ]
>>>>> [seasideuser at domU-12-31-39-14-08-6B ~]$
>>>>> /opt/gemstone/product/seaside/bin/runSeasideGems30: line 21:
>>>>> /WAFastCGIAdaptor_start-9002.log: Permission denied
>>>>> /opt/gemstone/product/seaside/bin/runSeasideGems30: line 21:
>>>>> /WAFastCGIAdaptor_start-9001.log: Permission denied
>>>>> /opt/gemstone/product/seaside/bin/runSeasideGems30: line 21:
>>>>> /WAFastCGIAdaptor_start-9003.log: Permission denied
>>>>> /opt/gemstone/product/seaside/bin/runSeasideGems30: line 28:
>>>>> /maintenance_start.log: Permission denied
>>>>> /opt/gemstone/product/seaside/bin/runSeasideGems30: line 35:
>>>>> /service_start.log: Permission denied
>>>>>
>>>>>
>>>>> It looks like I am missing permissions to write to the log files.
>>>>> Did I miss some change that I had to make to those two script files,
>>>>> runSeasideGems30 and gemstone?
>>>>>
>>>>> It has been a while since I have done any Gemstone work so I'm a little
>>>>> lost.
>>>>>
>>>>> Larry
>>>>>
>>>>>
>>>>> On Oct 12, 2011, at 2:54 PM, Nick Ager wrote:
>>>>>
>>>>> Hi Larry.
>>>>>
>>>>> Try:
>>>>>
>>>>> http://seaside.gemstone.com/scripts/installGemstone.sh
>>>>>
>>>>> thanks for the corrections - I fix the blog post in due course.
>>>>>
>>>>> A good source of up-to-date information is:
>>>>>
>>>>> http://code.google.com/p/glassdb/
>>>>>
>>>>> Nick
>>>>>
>>>>> On 12 October 2011 19:29, Lawrence Kellogg <mac.hive at me.com> wrote:
>>>>>
>>>>>> Hey Nick,
>>>>>>
>>>>>> $ wget http://glass.gemstone.com/scripts/installGemstone.sh
>>>>>> --2011-10-12 18:25:48--
>>>>>> http://glass.gemstone.com/scripts/installGemstone.sh
>>>>>> Resolving glass.gemstone.com... 64.20.104.5
>>>>>> Connecting to glass.gemstone.com|64.20.104.5|:80... connected.
>>>>>> HTTP request sent, awaiting response... 301 Moved Permanently
>>>>>> Location: https://glass.gemstone.com/scripts/installGemstone.sh[following]
>>>>>> --2011-10-12 18:25:48--
>>>>>> https://glass.gemstone.com/scripts/installGemstone.sh
>>>>>> Connecting to glass.gemstone.com|64.20.104.5|:443... connected.
>>>>>> ERROR: certificate common name “magtrac.gemstone.com” doesn’t match
>>>>>> requested host name “glass.gemstone.com”.
>>>>>> To connect to glass.gemstone.com insecurely, use
>>>>>> ‘--no-check-certificate’.
>>>>>>
>>>>>> and with the no certificate option
>>>>>>
>>>>>> $ wget http://glass.gemstone.com/scripts/installGemstone.sh--no-check-certificate
>>>>>> --2011-10-12 18:26:35--
>>>>>> http://glass.gemstone.com/scripts/installGemstone.sh
>>>>>> Resolving glass.gemstone.com... 64.20.104.5
>>>>>> Connecting to glass.gemstone.com|64.20.104.5|:80... connected.
>>>>>> HTTP request sent, awaiting response... 301 Moved Permanently
>>>>>> Location: https://glass.gemstone.com/scripts/installGemstone.sh[following]
>>>>>> --2011-10-12 18:26:35--
>>>>>> https://glass.gemstone.com/scripts/installGemstone.sh
>>>>>> Connecting to glass.gemstone.com|64.20.104.5|:443... connected.
>>>>>> WARNING: certificate common name “magtrac.gemstone.com” doesn’t match
>>>>>> requested host name “glass.gemstone.com”.
>>>>>> HTTP request sent, awaiting response... 404 Not Found
>>>>>> 2011-10-12 18:26:35 ERROR 404: Not Found.
>>>>>>
>>>>>>
>>>>>> I guess the install script has been moved somewhere....
>>>>>>
>>>>>> Larry
>>>>>>
>>>>>>
>>>>>> On Oct 12, 2011, at 10:33 AM, Nick Ager wrote:
>>>>>>
>>>>>> Hi Larry,
>>>>>>
>>>>>> Make sure you include the " - " before your key and lines
>>>>>>> "#cloud-config" & "ssh_authorized_keys:"
>>>>>>> I find it helpful to form the syntax in a text editor prior to
>>>>>>> posting into the web-form.
>>>>>>>
>>>>>>>
>>>>>>> So, is there a space between the '-' and the 'ssh-rsa'? Does it
>>>>>>> matter?
>>>>>>>
>>>>>>
>>>>>> I haven't tried it without the spaces, but it works for me with the
>>>>>> spaces.
>>>>>>
>>>>>>
>>>>>>> I saw another parameter that said something about disabling metadata.
>>>>>>> I guess that parameter is not needed.
>>>>>>>
>>>>>>
>>>>>> Yes that is optional.
>>>>>>
>>>>>>
>>>>>>> By the way, your instructions say open SSH on Port 22 but the
>>>>>>> screen shot shows port 25, or
>>>>>>> vice versa. I assume that I only need to open up port 22 for SSH.
>>>>>>>
>>>>>>
>>>>>> Correct port 22 is SSH. I've corrected the spurious reference to port
>>>>>> 25 in the blog post - thanks. On the latest EC2 interface you can just pick
>>>>>> SSH and HTTP from the drop-down menu.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> It seems like the Security Group stuff has changed. I wasn't able
>>>>>>> to get the All Internet
>>>>>>> specification that you show. The entries I created all wanted a
>>>>>>> source, 0,0,0,0 or 1234567890/default.
>>>>>>> What do I do with that?
>>>>>>>
>>>>>>
>>>>>> Just pick SSH and HTTP from the drop-down, but I don't think this is
>>>>>> your problem.
>>>>>>
>>>>>>
>>>>>>> I wonder if it matters that I was trying this from my laptop over
>>>>>>> Wifi.
>>>>>>>
>>>>>>
>>>>>> I doubt that's an issue.
>>>>>>
>>>>>> Good luck
>>>>>>
>>>>>> Nick
>>>>>> _______________________________________________
>>>>>> seaside mailing list
>>>>>> seaside at lists.squeakfoundation.org
>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> seaside mailing list
>>>>>> seaside at lists.squeakfoundation.org
>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> seaside mailing list
>>>>> seaside at lists.squeakfoundation.org
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> seaside mailing list
>>>>> seaside at lists.squeakfoundation.org
>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>>
>>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>>
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20111013/14455893/attachment-0001.htm
More information about the seaside
mailing list