[GemStone-Smalltalk] How to configure GS/S 6.1.2 through a firewall (blast from the past)
Normand Mongeau
nmongeau at theobjects.com
Tue Feb 25 10:19:12 PST 2014
No I still have the same problem. Even though netldi is configured to use
ports 7001 to 7006, I still get errors for ports outside that range (for
example below, port 10657).
From: James Foster [mailto:james.foster at gemtalksystems.com]
Sent: mardi, 25 février 2014 13:15
To: Normand Mongeau
Cc: gemstone-smalltalk at lists.gemtalksystems.com
Subject: Re: [GemStone-Smalltalk] How to configure GS/S 6.1.2 through a
firewall (blast from the past)
This confirms that the Gem started (so we got through all the NetLDI
complications), and that the problem was with the Gem-to-Stone connection. I
assume that this problem was solved when you set an environment variable
GS_MAKE_EVENTS_GLOBAL=1.
James
On Feb 25, 2014, at 10:08 AM, Normand Mongeau <nmongeau at theobjects.com>
wrote:
Heres the matching gem log :
Heres the matching gem log :
____________________________________________________________________________
_
| GemStone Object-Oriented Data Management System
|
| Copyright (C) GemStone Systems, Inc. 1986-2004.
|
| All rights reserved.
|
+---------------------------------------------------------------------------
--+
| PROGRAM: GEM, GemStone Session Process
|
| VERSION: 6.1.2, Wed Feb 25 15:46:30 US/Pacific 2004
|
| BUILT FOR: Pentium/Windows_NT
|
| RUNNING ON: 2-CPU phatboy: Intel CPU, Windows NT 5.1 build 2600 Service
Pack|
| 3
|
| PROCESS ID: 3308 DATE: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
|
|___________________________________________________________________________
__|
____________________________________________________________________________
_
| Configuration Files
|
|
|
| System File: C:/GemStone61/data/system.conf
|
|
|
| Executable File: C:/users/default/gem.conf
|
| Warning: File not found (The system cannot find the file specified.)
|
| using defaults.
|
|___________________________________________________________________________
__|
____________________________________________________________________________
_
| Gem Configuration Options for process id 3308
|
|___________________________________________________________________________
__|
GEM_DETACH_PAGES_ON_COMMIT = TRUE;
GEM_DETACH_PAGES_ON_ABORT = TRUE;
DUMP_OPTIONS = TRUE;
GEM_DBF_FILE_LOCK = TRUE;
GEM_GCI_LOG_ENABLED = FALSE;
GEM_FREE_FRAME_LIMIT = -1;
GEM_HALT_ON_ERROR = 0;
GEM_IO_LIMIT = 5000;
GEM_MAX_SMALLTALK_STACK_DEPTH = 1000;
GEM_NATIVE_CODE_MAX = 8192;
GEM_NATIVE_CODE_THRESHOLD = 6;
GEM_NOT_CONNECTED_DELTA = 300;
GEM_NOT_CONNECTED_THRESHOLD = 2000;
GEM_PGSVR_FREE_FRAME_LIMIT = -1;
GEM_PRIVATE_PAGE_CACHE_KB = 200;
GEM_RPCGCI_TIMEOUT = 0;
GEM_TEMPOBJ_CACHE_SIZE = 600;
LOG_WARNINGS = TRUE;
SHR_NUM_FREE_FRAME_SERVERS = 1;
SHR_PAGE_CACHE_SIZE_KB = 10000;
SHR_PAGE_CACHE_NUM_PROCS = 256;
SHR_TARGET_FREE_FRAME_COUNT = -1;
[Info]: RPC client/gem/minimum GCI levels = 33/33/30
Error connecting to stone:
Nonblocking connect(MyIP,port=10657) failed to
complete.-----------------------------------------------------
GemStone: Error Fatal
["The connection to the Stone Repository monitor was refused:\n"
errmsg.netErrCo
nnectionRefused Nonblocking connect(MyIP,port=10657) failed
to complete.]
Error Category: 3613 [GemStone] Number: 4136 Arg Count: 0 Context : 10
*****************************************************
****** GemStone Abnormal Shutdown
*****************************************************
-----------------------------------------------------
GemStone: Error Fatal
["The connection to the Stone Repository monitor was refused:\n"
errmsg.netErrCo
nnectionRefused Nonblocking connect(MyIP,port=10657) failed
to complete.]
Error Category: 3613 [GemStone] Number: 4136 Arg Count: 0 Context : 10
From: James Foster [mailto:james.foster at gemtalksystems.com]
Sent: mardi, 25 février 2014 00:17
To: Normand Mongeau
Cc: gemstone-smalltalk at lists.gemtalksystems.com
Subject: Re: [GemStone-Smalltalk] How to configure GS/S 6.1.2 through a
firewall (blast from the past)
This suggests that the Gem has started so it should have created a log file
as well. That would be the next place to look.
On Feb 24, 2014, at 8:00 PM, Normand Mongeau <
<mailto:nmongeau at theobjects.com> nmongeau at theobjects.com> wrote:
Yes to all of those questions
Im doing an RPC login.
For starters, heres a sample of netldi in debug mode:
Summary of netldi parameters:
The host name is "phatboy".
GEMSTONE is: "C:\GemStone61".
System password authorization is permitted.
Clients are not authenticated.
Process creation is permitted through user's HOME directory.
Pool of ports is "7001:7006".
Created processes belong to the account named "SYSTEM".
The default directory for log files is 'C:\users\default\'.
Entering Service Loop
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Attempting accept...
...succeeded accepting client from 192.168.0.1, connection = 2
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Finished reading client request:
Client is a rpc application.
'!@MyIP#encrypted:Claude!gemnetobject'
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Successful fork; Child's Pid: 3308 command is:
'C:/GemStone61/bin/gem.exe TCP 10806 30'
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Now reading reply from child
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Reply to client started:
'SUCCESS 7001'
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Done writing reply to client.
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Disposed. elapsed time = 0
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Attempting accept...
...succeeded accepting client from 192.168.0.1, connection = 2
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Finished reading client request:
Client is a rpc gem or a linked application.
'!@MyIP#encrypted:SYSTEM#server!icp1'
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Reply to client started:
'SUCCESS 10657'
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Done writing reply to client.
0: Mon 24 Feb 2014 15:42:02 Eastern Standard Time
Disposed. elapsed time = 0
At this point the client gets the error:
GS Server Error - GbsNetErrConnectionRefused - ["The connection to the Stone
Repository monitor was refused:\n" errmsg.netErrConnectionRefused
Nonblocking connect(my IP Address,port=10657) failed to complete.]
From: James Foster [ <mailto:james.foster at gemtalksystems.com>
mailto:james.foster at gemtalksystems.com]
Sent: 24 février 2014 22:50
To: Normand Mongeau
Cc: <mailto:gemstone-smalltalk at lists.gemtalksystems.com>
gemstone-smalltalk at lists.gemtalksystems.com
Subject: Re: [GemStone-Smalltalk] How to configure GS/S 6.1.2 through a
firewall (blast from the past)
Good work verifying that the initial connection from the GCI client to the
NetLDI is working. Reading the error message more closely I see that the
problem claims to be connecting to the stone. Are you doing a linked login
or an RPC login? I think it will be much more difficult to do a linked login
from outside a firewall. Can you start the NetLDI in debug mode (/d)? Can
you track down the various log files? Is there a gemnetobject log file?
James
On Feb 24, 2014, at 7:42 PM, Normand Mongeau <
<mailto:nmongeau at theobjects.com> nmongeau at theobjects.com> wrote:
Proof that 10088 is configured correctly, I just closed that port in the
firewall and the error message is different:
GS Server Error - GbsHostErrCantSpawn - Unable to create a GemStone session.
NetLDI service 'netldi61' not found on node 'MyIP:
Nonblocking connect(MyIP,port=10088) failed to complete.
From: Normand Mongeau [ <mailto:nmongeau at theobjects.com>
mailto:nmongeau at theobjects.com]
Sent: 24 février 2014 22:34
To: 'James Foster'
Subject: RE: [GemStone-Smalltalk] How to configure GS/S 6.1.2 through a
firewall (blast from the past)
Hi James,
I should have mentioned that port 10088 is already configured and
functional, and the firewall already lets it through.
There is something missing and I dont know what, but this is extremely
frustrating.
Heres where I am:
-netldi61 10088/tcp is configured in the services file
-port 10088 is open in the firewall
-the netldi service was created with a port range (I now changed it to
7001:7006)
-ports 7001 to 7006 are also open in the firewall
When I connect using the LAN ip address, it works, but when I try using the
public WAN address, I always get an error message, and the port is always
outside the 7001 to 7006 range.
Normand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/gemstone-smalltalk/attachments/20140225/d3ac4f9c/attachment-0001.html>
More information about the GemStone-Smalltalk
mailing list