search

zkfan / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

RMI port option is not applied #72

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. start the replicator in --direct mode
TUNGSTEN_BASE=$HOME/testtool
./tools/tungsten-installer \
    --direct \
    --master-host=127.0.0.1 \
    --master-port=7101 \
    --slave-host=127.0.0.1 \
    --slave-port=7102 \
    --master-user=root \
    --slave-user=root \
    --master-password=msandbox \
    --slave-password=msandbox \
    --master-log-directory=$HOME/sandboxes/tr_dbs/node1/data \
    --service-name=Castor \
    --thl-port=12112 \
    --rmi-port=10101 \
    --home-directory=$TUNGSTEN_BASE \
    --thl-directory=$TUNGSTEN_BASE/thl1 \
    --relay-directory=$TUNGSTEN_BASE/relay1 

2. check the port in the configuration file 
grep rmi_port tungsten/tungsten-replicator/conf/static-*.properties 
tungsten/tungsten-replicator/conf/static-Castor.properties:replicator.rmi_port=1
0101
tungsten/tungsten-replicator/conf/static-Pollux.properties:replicator.rmi_port=1
0101

3. Check the port occupancy
$ nmap localhost

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2011-05-19 09:54 CEST
Interesting ports on master.localhost (127.0.0.1):
Not shown: 1674 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
3306/tcp  open  mysql
10000/tcp open  snet-sensor-mgmt

sudo netstat -lnp | grep 10000
tcp        0      0 :::10000                    :::*                        
LISTEN      13308/java      

What is the expected output? What do you see instead?
I expect to see port 10101 used instead of port 10000

Original issue reported on code.google.com by g.maxia on 19 May 2011 at 8:00

GoogleCodeExporter commented 9 years ago 
The RMI port should've been written into services.properties.  That is now 
happening.

Original comment by jeffm...@gmail.com on 19 May 2011 at 1:21

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Not fixed. Using a RMI port different from 10000 will be ignored.

Original comment by g.maxia on 20 May 2011 at 4:21

GoogleCodeExporter commented 9 years ago 
Giuseppe,

Please post the manifest for the build so that I can see why this isn't working 
for you.

Original comment by jeffm...@gmail.com on 20 May 2011 at 4:52

GoogleCodeExporter commented 9 years ago 
DATE: Fri May 20 05:39:16 UTC 2011
RELEASE: tungsten-replicator-2.0.3-93
USER ACCOUNT: hudson
BUILD_NUMBER: 93
BUILD_ID: 93
JOB_HAME: Build Replicator Branch-2.0 Google
BUILD_TAG: hudson-Build Replicator Branch-2.0 Google-93
HUDSON_URL: http://cc.aws.continuent.com/
SVN_REVISION: 152
HOST: ip-10-251-90-63
SVN URLs:
  https://tungsten-replicator.googlecode.com/svn/trunk/commons
  https://tungsten-replicator.googlecode.com/svn/trunk/fsm
  https://tungsten-replicator.googlecode.com/svn/trunk/replicator
  https://tungsten-replicator.googlecode.com/svn/trunk/replicator-extra
  https://bristlecone.svn.sourceforge.net/svnroot/bristlecone/trunk/bristlecone
SVN Revisions:
  commons: Revision: 154
  fsm: Revision: 154
  replicator: Revision: 154
  replicator-extra: Revision: 154
  bristlecone: Revision: 103

If I install without the --rmi-port option, it installs. If I use the 
--rmi-port, with any value, it hangs.

TUNGSTEN_BASE=$HOME/testtool/
./tools/tungsten-installer \
    --direct \
    --master-host=db1 \
    --master-port=7101 \
    --slave-host=db2 \
    --slave-port=7102 \
    --master-user=root \
    --slave-user=root \
    --master-password=msandbox \
    --slave-password=msandbox \
    --master-log-directory=$HOME/sandboxes/tr_dbs/node1/data \
    --service-name=Castor \
    --thl-port=12112 \
    --rmi-port=20101 \
    --channels=1 \
    --home-directory=$TUNGSTEN_BASE \
    --thl-directory=$TUNGSTEN_BASE/thl1 \
    --relay-directory=$TUNGSTEN_BASE/relay1

Original comment by g.maxia on 20 May 2011 at 6:14

GoogleCodeExporter commented 9 years ago

Original comment by jeffm...@gmail.com on 20 May 2011 at 7:17

GoogleCodeExporter commented 9 years ago

Original comment by jeffm...@gmail.com on 20 May 2011 at 7:18

GoogleCodeExporter commented 9 years ago 
This is working.  Nmap without specifying a port will not scan all ports and so 
the user must specify the port to be checked.

Original comment by jeffm...@gmail.com on 23 May 2011 at 12:37