[Glass] Need to restart GLASS...

Tue Sep 16 07:34:28 PDT 2014

  I’m struggling with getting the squeak image to display windows on my laptop. I upgraded XQuartz for X11 support under Maverick, and I ran ‘host +’ to allow any host to display windows on my machine. I set ‘export DISPLAY=myipaddress:0’ on the Amazon instance and bring up Squeak, but no windows display on my machine! This has always worked for me before, so I’m puzzled as to what is wrong. 

  Squeak is running fine in the background. 

  If I do get the Pharo windows to display again, do I have to start anything from the image to get Seaside up and running? I start FastCGI Gems from a script. 

  Any thoughts?

  Larry

On Sep 16, 2014, at 2:46 AM, Lawrence Kellogg via Glass <glass at lists.gemtalksystems.com> wrote:

> Well, it looks like I can start and stop Gemstone without any problem, as well as netldi, but I’m having trouble getting nginx to talk to my fastcgi gems. Perhaps it has something to do with my A record from Register.com, I’m not sure. I checked the IP address of my running Amazon instance, and I see that I have an elastic IP address allocated, which is in the A record on Register. Register sticks some other ip address in the first line of my A record, something I have noticed in the past. I removed that other ip address, but changes take a while to propagate.
> 
>  Strangely, while the ip address seems fine in the nginx error log, the hostname is wrong, it somehow to think it is a different server than the one I’m accessing. 
> 
> upstream timed out (110: Connection timed out) while connecting to upstream, client: zz.zz.zz.zz, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://xx.xx.xx.xx:9001", host: “www.practjour.com"
> 
> (should be www.practicemusic.com) I also own www.practjour.com.
> 
>  I wrote a little supervise job to bring up the fast cgi gems automatically if they ever fall down. that seems to work. I changed my nginx.conf file to make sure it points to the ip address of my server, plus :9001, :9002, and :9003 for the gems.
> 
>  So, I’m kind of stumped at the moment. I’ll work on it some more later.
> 
>  Larry
> 
> 
> On Sep 15, 2014, at 9:59 PM, James Foster <james.foster at gemtalksystems.com> wrote:
> 
>> The “Killed” status can be cleared by using ‘gslist -c’ to “clear” the lock files (typically in /opt/gemstone/locks). And, yes, the GemStone system will restore to the last commit point. As to the other processes, I don’t have much to contribute.
>> 
>> James
>> 
>> On Sep 15, 2014, at 6:42 PM, Lawrence Kellogg via Glass <glass at lists.gemtalksystems.com> wrote:
>> 
>>> Well, I knew it had to happen eventually. It looks like Amazon took down my instance and did some maintenance on it, so all of my GemStone processes list as Killed when I run the gslist command. I’m going to have to dig up my notes on how to get the whole system up and running again, as it has been running nonstop for something like two years, IIRC. As I’m no longer actively working on this project, I’m at a little bit of a loss as to all the things I have to do, LOL.
>>> 
>>> Anything I should be aware of when trying to bring it all back up? I have to bring up nginx, FastCGI, and all the rest. It should just restore to the last commit point in the logs, I assume. 
>>> 
>>> Regards, 
>>> 
>>> Larry
>>> _______________________________________________
>>> 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