Replicator start in sandbox fails due to non-standard ports

[GoogleCodeExporter]

I downloaded tungsten-replicator-2.0.1, unpacked the tarball, and ran 
./configure. The tungsten.cfg it produced is attached. 

I then ran this command to create a service (I'm following the Installation 
Guide):

./configure-service -C --role=master --service-type=local ditto

I then get the following output when trying to start the service:

tlittle@coolaid ~/tungsten-replicator-2.0.1 $ ./tungsten-replicator/bin/trepctl 
-service ditto start
Service started successfully: name=ditto

tlittle@coolaid ~/tungsten-replicator-2.0.1 $ ./tungsten-replicator/bin/trepctl 
-service ditto status
Processing status command...
NAME                     VALUE
----                     -----
appliedLastEventId     : NONE
appliedLastSeqno       : -1
appliedLatency         : -1.0
clusterName            : 
currentEventId         : NONE
currentTimeMillis      : 1303314542966
dataServerHost         : coolaid
extensions             : 
host                   : null
latestEpochNumber      : -1
masterConnectUri       : thl://localhost:2112/
masterListenUri        : thl://coolaid:2112/
maximumStoredSeqNo     : -1
minimumStoredSeqNo     : -1
offlineRequests        : NONE
pendingError           : Replicator unable to go online due to error
pendingErrorCode       : NONE
pendingErrorEventId    : NONE
pendingErrorSeqno      : -1
pendingExceptionMessage: Unable to prepare plugin: class 
name=com.continuent.tungsten.enterprise.replicator.thl.EnterpriseTHL
resourcePrecedence     : 99
rmiPort                : -1
role                   : master
seqnoType              : java.lang.Long
serviceName            : ditto
serviceType            : unknown
simpleServiceName      : ditto
siteName               : default
sourceId               : coolaid
state                  : OFFLINE:ERROR
timeInStateSeconds     : 6.711
uptimeSeconds          : 6.883
Finished status command...

Notice this line in particular:

 pendingExceptionMessage:  Unable to prepare plugin: class name=com.continuent.tungsten.enterprise.replicator.thl.EnterpriseTHL

I'm surprised to see anything about "EnterpriseTHL" since this is the 
open-source version, but maybe that's just a naming thing.

I may be doing something wrong here, but I was just trying to setup a simple 
master-slave replication using the "Installation & Configuration Guide" found 
here: http://www.continuent.com/downloads/documentation

Thanks,
Trevor Little

Original issue reported on code.google.com by TrevorM...@gmail.com on 20 Apr 2011 at 3:56

Attachments:

• tungsten.cfg

[GoogleCodeExporter]

It seems from the tungsten.cfg that you are using the Tungsten sandbox?  If so, 
there's a problem with setting ports properly to avoid conflicts.  Can you 
provide confirmation that this is the case?

Also, the EnterpriseTHL name is a little disconcerting, but it's all open 
source.  This is just there in order to make things simpler for merges to older 
code and will go away in a future release. 

Original comment by berkeley...@gmail.com on 20 Apr 2011 at 5:32

[GoogleCodeExporter]

Issue 22 describes the main sandbox port issue.  

Original comment by berkeley...@gmail.com on 20 Apr 2011 at 5:33

[GoogleCodeExporter]

The trouble with using a non-standard server (e.g. MySQL Sandbox)  is that the 
Tungsten installer can't deal easily with ports and other distinctive 
attributes of the server.
A future release will fix this. In the meantime, an easy workaround is to use 
virtual machines with default MySQL servers. The more difficult workaround 
requires editing the configuration files. I'd rather avoid it at this stage.

Original comment by g.maxia on 20 Apr 2011 at 5:37

[GoogleCodeExporter]

I am using MySQL Sandbox, and therefore running on a non-standard port. I 
figured this was fine since the installer asked me for the host and port of the 
mysql instance. Can Tungsten replicator not talk to mysql instances on 
non-standard ports?

Original comment by TrevorM...@gmail.com on 20 Apr 2011 at 5:55

[GoogleCodeExporter]

Tungsten can talk to non-standard mysql ports just fine.
It's the installer that is not smart enough at the moment. We are working at it.
As I mentioned before, a workaround would be to edit the configuration file 
that was generated by the installer.

Original comment by g.maxia on 20 Apr 2011 at 6:56

[GoogleCodeExporter]

Ok great. Using a VM instead of the MySQL sandbox works. Thanks for the help.

Original comment by TrevorM...@gmail.com on 20 Apr 2011 at 7:20

[GoogleCodeExporter]

Original comment by berkeley...@gmail.com on 25 Apr 2011 at 3:17

• Changed title: Replicator start in sandbox fails due to non-standard ports

[GoogleCodeExporter]

This issue was fixed with the introduction of ./tools/tungsten-installer.
here's an example that installs two Tungsten instances from local MySQL 
sandboxes:
/tools/tungsten-installer \
  --master-slave \
  --home-directory=$HOME/tsb/node1 \
  --cluster-hosts=db1 \
  --master-host=db1 \
  --datasource-port=7101 \
  --datasource-user=root \
  --datasource-password=msandbox \
  --home-directory=$TUNGSTEN_BASE/db1 \
  --datasource-log-directory=$HOME/sandboxes/tr_dbs/node1/data \
  --service-name=tsandbox \
  --thl-port=12111 \
  --rmi-port=10101

./tools/tungsten-installer \
  --master-slave \
  --home-directory=$HOME/tsb/node2 \
  --cluster-hosts=db2 \
  --master-host=db1 \
  --master-thl-port=12111 \
  --datasource-port=7102 \
  --datasource-user=root \
  --datasource-password=msandbox \
  --home-directory=$TUNGSTEN_BASE/db2 \
  --datasource-log-directory=$HOME/sandboxes/tr_dbs/node2/data \
  --service-name=tsandbox \
  --thl-port=12112 \
  --rmi-port=10102

Documentation will follow shortly.

Original comment by g.maxia on 25 May 2011 at 10:42

• Changed state: Verified
• Added labels: FixedIn-2.0.3, FoundIn-2.0.3
• Removed labels: FoundIn