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

[James Foster via GemStone-Smalltalk]

Hi Ezequiel,

It appears from your observations below and the earlier log files (with extra socket logging) that you are right that at least some connections are succeeding. Thus, it is probably not a firewall issue. After further review of the logs it does seem that there is a problem with how the AIO page server is connecting to the stone. In one of the logs we see a response of SOCK_EINPROGRESS but there is never a full connection. Without looking deeper, we aren’t really sure why the failure happens.

Is there a reason you are using version 3.2.8.1 and not something more recent? That was released in August 2015, so is over two years old. Could you try starting a stone for the most recent version, say 3.3.6 or even 3.4.0-Alpha5 (see http://downloads.gemtalksystems.com/pub/GemStone64/ <http://downloads.gemtalksystems.com/pub/GemStone64/>)? I think we could get more traction in investigating this on a newer version.

Regards,

James Foster

> On Sep 28, 2017, at 8:21 AM, brianstone via GemStone-Smalltalk <gemstone-smalltalk at lists.gemtalksystems.com> wrote:
> 
> Hi,
> 
> I followed James's advice and configured the ports for the Stone and the
> Shared Page Cache Monitor.
> 
> I'm using this configuration:
> 
> STN_WELL_KNOWN_PORT_NUMBER = 51001;
> SHR_WELL_KNOWN_PORT_NUMBER = 51002;
> 
> Regarding an internall firewall, I tested by deactivating any firewall in
> the machine but anyway the problem still there.
> 
> On my last test I have activated again iptables and configured to allow
> traffic through these ports(51001 and 51002). After that, I tried again to
> start Gemstone, and during the startup I tested the following commands:
> 
> *netstat -uptona | grep 51001*
> tcp        0      0 :::51001                    :::*                       
> LISTEN      30145/stoned        off (0.00/0/0)
> tcp      160      0 ::1:51001                   ::1:47588                  
> ESTABLISHED 30145/stoned        off (0.00/0/0)
> tcp        0      0 ::1:47588                   ::1:51001                  
> ESTABLISHED 30157/pgsvrmain     off (0.00/0/0)
> 
> *netstat -uptona | grep 51002*
> tcp        0      0 ::ffff:127.0.0.1:51002      :::*                       
> LISTEN      30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:51002                   :::*                       
> LISTEN      30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:45972                   ::1:51002                  
> ESTABLISHED 30157/pgsvrmain     off (0.00/0/0)
> tcp        0      0 ::1:45970                   ::1:51002                  
> ESTABLISHED 30154/pgsvrmain     off (0.00/0/0)
> tcp        0      0 ::1:45968                   ::1:51002                  
> ESTABLISHED 30145/stoned        off (0.00/0/0)
> tcp        0      0 ::1:51002                   ::1:45974                  
> ESTABLISHED 30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:51002                   ::1:45970                  
> ESTABLISHED 30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:51002                   ::1:45968                  
> ESTABLISHED 30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:51002                   ::1:45972                  
> ESTABLISHED 30147/shrpcmonitor  off (0.00/0/0)
> tcp        0      0 ::1:45974                   ::1:51002                  
> ESTABLISHED 30145/stoned        off (0.00/0/0)
> 
> 
> *nmap -p1-52000 localhost*
> 
> Starting Nmap 5.51 ( http://nmap.org ) at 2017-09-28 11:49 -03
> Nmap scan report for localhost (127.0.0.1)
> Host is up (0.0000040s latency).
> rDNS record for 127.0.0.1: SRVR23
> Not shown: 51992 closed ports
> PORT      STATE SERVICE
> 22/tcp    open  ssh
> 25/tcp    open  smtp
> 111/tcp   open  rpcbind
> 631/tcp   open  ipp
> 5989/tcp  open  wbem-https
> 27017/tcp open  unknown
> 51001/tcp open  unknown
> 51002/tcp open  unknown
> 
> Nmap done: 1 IP address (1 host up) scanned in 1.04 seconds
> 
> 
> In the result of 'netstat' shows that there is an entablished connection.
> For me, that is a clearly proof that the connection is not a problem. I'm
> right?
> 
> I'm suspecting about a configuration with file descriptors. Can it be a
> problem?
> 
> Thanks in advance.
> 
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/gemstone-smalltalk/attachments/20170928/bc4e0de5/attachment.html>