Comments on: Setting up GLASS on Slicehost

By: GemStone on SliceHost « Programming Gems (on GemStone)

GemStone on SliceHost « Programming Gems (on GemStone) — Tue, 12 Jan 2010 23:56:29 +0000

[...] 12, 2010 in Uncategorized Some time ago I prepared some instructions for setting up GemStone on SliceHost.com. Since then some things have changed and I’ve had [...]

By: James Foster

James Foster — Wed, 22 Jul 2009 03:56:25 +0000

I updated the comment to add a hostname to the telnet command.

By: Kent Beck

Kent Beck — Wed, 22 Jul 2009 02:51:37 +0000

I got it figured out. The rules you suggest adding to iptables need to be at the beginning of the file, not at the end. Thanks for the help.

By: Kent Beck

Kent Beck — Wed, 22 Jul 2009 02:37:36 +0000

Sorry to be dense here. I suspect you are right, that I did something wrong in setting up the firewall.

I see what you’re trying to do with debugging. Unfortunately, telnet tries to interpret “8008″ as a host name, not a port number.

I’ll eyeball the iptables step again. I suppose another approach is to go back to a completely open firewall, make sure access works, then add rules one at a time until access doesn’t work again.

By: James Foster

James Foster — Wed, 22 Jul 2009 02:07:51 +0000

Kent, My suspicion is that the firewall is blocking the request. I’d try using telnet to see if the connection works. From within the slice try ‘telnet hostname 8008′. That should connect. If you are really adventuresome, you can type ‘GET /seaside’ and press return twice. That should give some nonsense back and disconnect you. Next try the same command from outside. If it works differently, then something is blocking the connection and I’d review the “Secure Your Server” section above.

James

By: Kent Beck

Kent Beck — Wed, 22 Jul 2009 01:48:24 +0000

James,

Thank you for the detailed instructions. Everything seemed to go perfectly until I got to the:
http://slice:8008/seaside/
step. My browser just waits a while and then gives me:
Error 101 (net::ERR_CONNECTION_RESET): Unknown error.

I’m at a bit of loss to even figure out how to debug this. Any suggestions?

Kent

By: Using GemTools to Access and Update GLASS « Programming Gems (on GemStone)

Using GemTools to Access and Update GLASS « Programming Gems (on GemStone) — Wed, 21 Jan 2009 15:21:38 +0000

[...] next step is to start the NetLDI service. This service listens on a port (during our initial setup the script defined 50377 as the port for NetLDI), starts gems in guest mode with the glass account, [...]

By: Install Gemstone/S 64 on a KVM virtual machine | The command line

Install Gemstone/S 64 on a KVM virtual machine | The command line — Mon, 15 Dec 2008 18:47:16 +0000

[...] instructions are very similar to the slicehost setup from James Foster’s post, but this time on a KVM virtual [...]

By: James Foster

James Foster — Sun, 16 Nov 2008 11:20:00 +0000

Yes, 256 is fine. In fact, you can see in step #4 above under “Get a Slicehost Account” that is what I am using.

By: isaiah

isaiah — Sat, 15 Nov 2008 21:58:04 +0000

In the GemStone/S documentation they recommend atleast 1GB of ram. Say i got 256mb ram on my slice, would glass still run reasonable well ?