[GemStone-Smalltalk] Starting a repository fails after shutdown of server.

[James Foster via GemStone-Smalltalk]

Ezequiel,

In general, a firewall will restrict communications between hosts, but you can also configure a firewall to restrict communications between processes on a single host. If your machine is configured to limit communications between processes that are started by the same user, then you need to enable some additional ports. 

By default, the various processes listen on a random port (as assigned by the OS). You can use various configurations to specify the actual port used. This is typically more important with respect to the NetLDI process, since it is called from external processes, but it can be an issue for other processes as well.

In the System Administration Guide, search for ‘WELL_KNOWN’ and then configure your system to use well-known ports for the Stone and the Shared Page Cache Monitor. Then enable those ports in your internal firewall and try starting the system again and let us know the result.

James Foster


> On Sep 25, 2017, at 12:41 PM, brianstone via GemStone-Smalltalk <gemstone-smalltalk at lists.gemtalksystems.com> wrote:
> 
> James,
> 
> Here are all the log files obtained using "GEMSTONE_SOCKET_DEBUG=1"
> 
> logs.zip <http://forum.world.st/file/t370666/logs.zip>  
> 
> On the other hand, during the startup I've tried many times with gslist to
> see the result. 
> Using gslist-l
> 
> gslist -l
> Status       Version    Owner    Pid   Port   Started     Type       Name
> -------     --------- --------- ----- ----- ------------ ------      ----
> exists      3.2.8.1   gemst643281  9878 37052 Sep 25 15:48 cache      
> Newstone~7663a27bab8c7a96
> exists      3.2.8.1   gemst643281  9876 38044 Sep 25 15:48 Stone      
> Newstone
> exists      3.2.8.1   gemst643281  7912 50387 Sep 25 12:56 Netldi      
> gs64ldi-3281
> 
> Using gslist -clv
> 
> gslist -clv
> Status       Version    Owner    Pid   Port   Started     Type       Name
> -------     --------- --------- ----- ----- ------------ ------      ----
>  OK        3.2.8.1   gemst643281  9878 37052 Sep 25 15:48 cache      
> Newstone~7663a27bab8c7a96
> frozen      3.2.8.1   gemst643281  9876 38044 Sep 25 15:48 Stone      
> Newstone
>  OK        3.2.8.1   gemst643281  7912 50387 Sep 25 12:56 Netldi     
> gs64ldi-3281
> 
> 
> Based on the logs, I think that you are right and is a networking problem.
> 
> Regarding your questions:
> 
> This server belongs to the company which I work for. It's often used to keep
> some internal web sites running  during a short period, for example for
> internal contests. Since I'm the administrator of the server and I have full
> control over it, some time ago I decided to install and test Gemstone.
> Currently is not running any site, and is unused, so the server is not
> overloaded.
> Recently this machine have been moved to a different network which have a
> more restrictive firewall, but I requested to enable traffic through the
> netldi port (I thought it will be enough).
> 
> Summarizing, yes, I was able to run Gemstone before the network change, but
> I thought that enabling netldi port should be enough.
> 
> What are the networking requisites needed to start Gemstone?
> 
> Hope this info can help you to deveal the problem.
> 
> Ezequiel
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Gemstone-S-f1461796.html
> _______________________________________________
> GemStone-Smalltalk mailing list
> GemStone-Smalltalk at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk