[GemStone-Smalltalk] Warnings and errors in stone log on startup - , linux user does not have CAP_SYS_RESOURCE; Error: listen on ::ffff:127.0.1.1 (127.0.1.1) port 34580 failed,

James Foster Smalltalk at JGFoster.net
Tue Jan 29 07:19:05 PST 2019


Gary,

That shows that you already have a stone running that is using port 34580. This is why another stone startup attempting to use port 34580 fails with “port already in use”.

Regarding the startup message
>  [Warning]: No server process protection from OOM killer
I suggest that you Google "gemstone OOM killer CAP_SYS_RESOURCE”. From there you will see that two of the top four responses point you to the install guide. So, go to https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-InstallGuide-Linux-3.4/GS64-InstallGuide-Linux-3.4.htm?https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-InstallGuide-Linux-3.4/1-Installation.htm <https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-InstallGuide-Linux-3.4/GS64-InstallGuide-Linux-3.4.htm?https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-InstallGuide-Linux-3.4/1-Installation.htm> and search for OOM. 

If you are setting up your own GemStone installation and want to look at Seaside, then you might try starting with $GEMSTONE/bin/extent0.seaside.dbf. Alternatively, if you are dealing with a base repository (for example, someone else provided you with a system) then you could look at my script at https://gist.github.com/jgfoster/8286467d5208c66e11edefea76b3b34f <https://gist.github.com/jgfoster/8286467d5208c66e11edefea76b3b34f>.

As to GBS out-of-memory issues in VW, I’ll let others help with that.

James


> On Jan 28, 2019, at 11:00 PM, Gary Morrison <gcmfrompsu at gmail.com> wrote:
> 
> Hi James,
> This is what gslist -cvl shows: 
> 
> $ bash
> gemdba at ubuntu-s-1vcpu-2gb-nyc1-01:~$ gslist -cvl
> Status        Version    Owner       Pid   Port   Started     Type       Name
> -------      --------- --------- -------- ----- ------------ ------      ----
>   OK         3.4.3     gemdba        7261 50377 Jan 28 22:35 Netldi      gs64ldi
>   OK         3.4.3     gemdba        7195 34580 Jan 28 22:35 Stone       gs64stone
>   OK         3.4.3     gemdba        7197 45071 Jan 28 22:35 cache       gs64stone~27e920da89c7660
>  
> 
> When starting netldi I just ran, startnetldi.   I'll check the System Administration Guide, page 353 for details to identify a log file.
> 
> Thanks!
> Gary
> 
> On Tue, Jan 29, 2019 at 1:50 AM James Foster <Smalltalk at jgfoster.net <mailto:Smalltalk at jgfoster.net>> wrote:
> Hi Gary,
> 
> Do you have any GemStone processes running? What do you see when you execute ‘gslist -cvl’ from a bash prompt?
> 
> What options did you use for the startnetldi command (System Administration Guide, page 353)? Did you specify a path for a log file?
> 
> James
> 
> 
> 
> > On Jan 28, 2019, at 10:42 PM, Gary Morrison via GemStone-Smalltalk <gemstone-smalltalk at lists.gemtalksystems.com <mailto:gemstone-smalltalk at lists.gemtalksystems.com>> wrote:
> > 
> > Hi,
> > I recently installed the Community Edition of GS64 on Linux (GemStone64Bit3.4.3-x86_64.Linux)
> > 
> > I am having trouble logging into the database from VW 8.3.
> > 
> > I noticed the following errors in the stone log: 
> > 
> >     Now starting GemStone monitor.
> > 
> > [Warning]: Write to /proc/7195/oom_score_adj failed with EACCES , linux user does not have CAP_SYS_RESOURCE
> > [Warning]: No server process protection from OOM killer
> > 
> > <snip>
> > 
> >     :: (wildcard) found in listening addresses, ignoring other addresses
> >     listening on ::ffff:127.0.1.1 which is loopback for ubuntu-s-1vcpu-2gb-nyc1-01
> >     Created listening socket for :: on :: port 34580
> > Error: listen on ::ffff:127.0.1.1 (127.0.1.1) port 34580 failed, bind(21, ::ffff:127.0.1.1, port=34580) failed with errno=98,EADDRINUSE, Address is already in use
> > Error: listen on ::ffff:127.0.1.1 port 34580 failed, bind(21, ::ffff:127.0.1.1, port=34580) failed with errno=98,EADDRINUSE, Address is already in use
> > Failed to listen on ::ffff:127.0.1.1
> > 
> > 
> > So is port, 34580, the port used by netldi? 
> > 
> > I also couldn't find the log file for netldi.  I don't see it in the data directory with the other log files.
> > I was trying to see what netldi was doing when VW tried to connect.
> > 
> > Thank you for any suggestions,
> > Gary
> > 
> > _______________________________________________
> > GemStone-Smalltalk mailing list
> > GemStone-Smalltalk at lists.gemtalksystems.com <mailto:GemStone-Smalltalk at lists.gemtalksystems.com>
> > http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk <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/20190129/1300ebf5/attachment-0001.html>


More information about the GemStone-Smalltalk mailing list