Tungsten Replicator 4.0 Installation - mysql

I am trying to install Tungsten Replicator 4.0 version for Mysql 5.7. I have used binary installation(tar.gz file installation) for Mysql 5.7 and exported path in bash_profile.
./tools/tmp install command got executed successfully but services both master and slave are offline. We are getting below error for service status command.
[tungsten#beta-388 tungsten-replicator-4.0.0-18]$ /opt/continuent//tungsten/tungsten-replicator/bin/trepctl services
Processing services command...
NAME VALUE
---- -----
appliedLastSeqno: -1
appliedLatency : -1.0
role : master
serviceName : beta182_183
serviceType : unknown
started : true
state : OFFLINE:ERROR
NAME VALUE
---- -----
**appliedLastSeqno**:**** **Unknown**
**appliedLatency **:**** **Unknown**
**role** **:** **Unknown**
serviceName : beta183_182
serviceType : Unknown
started : false
state : Unknown
Finished services command...
[tungsten#beta-388 tungsten-replicator-4.0.0-18]$ /opt/continuent//tungsten/tungsten-replicator/bin/trepctl -service beta182_183 status
Processing status command...
NAME VALUE
---- -----
appliedLastEventId : NONE
appliedLastSeqno : -1
appliedLatency : -1.0
autoRecoveryEnabled : true
autoRecoveryTotal : 0
channels : -1
clusterName : beta182_183
currentEventId : NONE
currentTimeMillis : 1579684465335
dataServerHost : beta-388.panterranetworks.net
extensions :
host : beta-388.panterranetworks.net
latestEpochNumber : -1
masterConnectUri : thls://localhost:/
masterListenUri : thls://beta-388.panterranetworks.net:12120/
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.replicator.thl.THL message=[Error while attempting to acquire file lock: /opt/continuent/thl/beta182_183/disklog.lck]**
pipelineSource : UNKNOWN
relativeLatency : -1.0
resourcePrecedence : 99
rmiPort : 10110
role : master
seqnoType : java.lang.Long
serviceName : beta182_183
serviceType : unknown
simpleServiceName : beta182_183
siteName : default
sourceId : beta-388.panterranetworks.net
state : OFFLINE:ERROR
timeInStateSeconds : 15.744
timezone : GMT
transitioningTo :
uptimeSeconds : 15.931
useSSLConnection : true
version : Tungsten Replicator 4.0.0 build 18
Finished status command...
Can anyone please share how to resolve the error? I have tried multiple times with giving all permissions to the file and also uninstalled and reinstalled the tungsten.

Mysql version 5.7 is not support tungsten version 4.0,
https://docs.continuent.com/tungsten-replicator-4.0/introduction.html
Shared your config replicator!

Related

Mysql install Error: Could not find OpenSSL on the system

im following this guideline to install mysql: https://dev.mysql.com/doc/mysql-linuxunix-excerpt/5.7/en/binary-installation.html
here is list of command:
$> groupadd mysql
$> useradd -r -g mysql -s /bin/false mysql
$> cd /usr/local
$> tar zxvf /path/to/mysql-VERSION-OS.tar.gz
$> ln -s full-path-to-mysql-VERSION-OS mysql
$> cd mysql
$> mkdir mysql-files
$> chown mysql:mysql mysql-files
$> chmod 750 mysql-files
$> bin/mysqld --initialize --user=mysql
$> bin/mysql_ssl_rsa_setup
$> bin/mysqld_safe --user=mysql &
# Next command is optional
When i run to this command bin/mysql_ssl_rsa_setup then i got error:
[ERROR] Could not find OpenSSL on the system
I run this command to install openssl : yum install openssl-devel
it look ok:
Total 6.0 MB/s | 6.5 MB 00:00:01
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : libcom_err-1.43.5-8.3.alios7.x86_64 1/28
Updating : keyutils-libs-1.5.8-3.4.alios7.x86_64 2/28
Updating : libsepol-2.5-10.1.alios7.x86_64 3/28
Updating : libselinux-2.5-14.1.1.alios7.x86_64 4/28
Updating : 1:openssl-libs-1.0.2k-23.1.alios7.x86_64 5/28
Updating : krb5-libs-1.15.1-51.1.alios7.x86_64 6/28
Installing : libkadm5-1.15.1-51.1.alios7.x86_64 7/28
Installing : libsepol-devel-2.5-10.1.alios7.x86_64 8/28
Installing : keyutils-libs-devel-1.5.8-3.4.alios7.x86_64 9/28
Updating : libss-1.43.5-8.3.alios7.x86_64 10/28
Installing : libcom_err-devel-1.43.5-8.3.alios7.x86_64 11/28
Updating : e2fsprogs-libs-1.43.5-8.3.alios7.x86_64 12/28
Installing : pcre-devel-8.32-15.1.alios7.x86_64 13/28
Installing : libselinux-devel-2.5-14.1.1.alios7.x86_64 14/28
Installing : libverto-devel-0.2.5-4.1.alios7.x86_64 15/28
Installing : krb5-devel-1.15.1-51.1.alios7.x86_64 16/28
Installing : zlib-devel-1.2.7-16.2.alios7.x86_64 17/28
Installing : 1:openssl-devel-1.0.2k-23.1.alios7.x86_64 18/28
Updating : e2fsprogs-1.43.5-8.3.alios7.x86_64 19/28
Cleanup : 1:openssl-libs-1.0.2k-12.1.alios7.x86_64 20/28
Cleanup : krb5-libs-1.15.1-19.1.alios7.x86_64 21/28
Cleanup : e2fsprogs-1.43.5-8.alios7.x86_64 22/28
Cleanup : e2fsprogs-libs-1.43.5-8.alios7.x86_64 23/28
Cleanup : libss-1.43.5-8.alios7.x86_64 24/28
Cleanup : libselinux-2.5-12.1.alios7.x86_64 25/28
Cleanup : libsepol-2.5-8.1.1.alios7.x86_64 26/28
Cleanup : libcom_err-1.43.5-8.alios7.x86_64 27/28
Cleanup : keyutils-libs-1.5.8-3.1.alios7.x86_64 28/28
Verifying : 1:openssl-devel-1.0.2k-23.1.alios7.x86_64 1/28
Verifying : e2fsprogs-1.43.5-8.3.alios7.x86_64 2/28
Verifying : krb5-libs-1.15.1-51.1.alios7.x86_64 3/28
Verifying : 1:openssl-libs-1.0.2k-23.1.alios7.x86_64 4/28
Verifying : libss-1.43.5-8.3.alios7.x86_64 5/28
Verifying : keyutils-libs-1.5.8-3.4.alios7.x86_64 6/28
Verifying : krb5-devel-1.15.1-51.1.alios7.x86_64 7/28
Verifying : libcom_err-1.43.5-8.3.alios7.x86_64 8/28
Verifying : zlib-devel-1.2.7-16.2.alios7.x86_64 9/28
Verifying : libverto-devel-0.2.5-4.1.alios7.x86_64 10/28
Verifying : libselinux-devel-2.5-14.1.1.alios7.x86_64 11/28
Verifying : libcom_err-devel-1.43.5-8.3.alios7.x86_64 12/28
Verifying : libsepol-devel-2.5-10.1.alios7.x86_64 13/28
Verifying : libsepol-2.5-10.1.alios7.x86_64 14/28
Verifying : pcre-devel-8.32-15.1.alios7.x86_64 15/28
Verifying : libkadm5-1.15.1-51.1.alios7.x86_64 16/28
Verifying : libselinux-2.5-14.1.1.alios7.x86_64 17/28
Verifying : keyutils-libs-devel-1.5.8-3.4.alios7.x86_64 18/28
Verifying : e2fsprogs-libs-1.43.5-8.3.alios7.x86_64 19/28
Verifying : libss-1.43.5-8.alios7.x86_64 20/28
Verifying : keyutils-libs-1.5.8-3.1.alios7.x86_64 21/28
Verifying : libselinux-2.5-12.1.alios7.x86_64 22/28
Verifying : libcom_err-1.43.5-8.alios7.x86_64 23/28
Verifying : libsepol-2.5-8.1.1.alios7.x86_64 24/28
Verifying : e2fsprogs-1.43.5-8.alios7.x86_64 25/28
Verifying : e2fsprogs-libs-1.43.5-8.alios7.x86_64 26/28
Verifying : krb5-libs-1.15.1-19.1.alios7.x86_64 27/28
Verifying : 1:openssl-libs-1.0.2k-12.1.alios7.x86_64 28/28
Installed:
openssl-devel.x86_64 1:1.0.2k-23.1.alios7
Dependency Installed:
keyutils-libs-devel.x86_64 0:1.5.8-3.4.alios7 krb5-devel.x86_64 0:1.15.1-51.1.alios7 libcom_err-devel.x86_64 0:1.43.5-8.3.alios7
libkadm5.x86_64 0:1.15.1-51.1.alios7 libselinux-devel.x86_64 0:2.5-14.1.1.alios7 libsepol-devel.x86_64 0:2.5-10.1.alios7
libverto-devel.x86_64 0:0.2.5-4.1.alios7 pcre-devel.x86_64 0:8.32-15.1.alios7 zlib-devel.x86_64 0:1.2.7-16.2.alios7
Dependency Updated:
e2fsprogs.x86_64 0:1.43.5-8.3.alios7 e2fsprogs-libs.x86_64 0:1.43.5-8.3.alios7 keyutils-libs.x86_64 0:1.5.8-3.4.alios7
krb5-libs.x86_64 0:1.15.1-51.1.alios7 libcom_err.x86_64 0:1.43.5-8.3.alios7 libselinux.x86_64 0:2.5-14.1.1.alios7
libsepol.x86_64 0:2.5-10.1.alios7 libss.x86_64 0:1.43.5-8.3.alios7 openssl-libs.x86_64 1:1.0.2k-23.1.alios7
Complete!
but the issue not solved.
Please guide how to solve. thanks a lot
i've found this command:
sudo yum install openssl then it's solved my issue
Result:
s this ok [y/d/N]: y
Downloading packages:
(1/2): openssl-1.0.2k-23.1.alios7.x86_64.rpm | 493 kB 00:00:00
(2/2): make-3.82-21.1.alios7.x86_64.rpm | 419 kB 00:00:00
-------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.9 MB/s | 912 kB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : 1:make-3.82-21.1.alios7.x86_64 1/2
Installing : 1:openssl-1.0.2k-23.1.alios7.x86_64 2/2
Verifying : 1:make-3.82-21.1.alios7.x86_64 1/2
Verifying : 1:openssl-1.0.2k-23.1.alios7.x86_64 2/2
Installed:
openssl.x86_64 1:1.0.2k-23.1.alios7
Dependency Installed:
make.x86_64 1:3.82-21.1.alios7

Kafka JDBC Sink Connector Not Consuming Events from Remote Cluster

Standalone Kafka JDBC sink connector not inserting data into mysql database (Using confluent-community-2.12)
I've installed confluent-community-2.12 on centos7 and started the standalone jdbc sink connector to consume records from a remote kafka cluster. I can consume the records via a simple java consumer and see the record data however, when I start the sink connector it loads and connects to the remote cluster fine but just stops at the following log INFO
[2019-05-01 11:10:21,619] INFO Initializing writer using SQL dialect: MySqlDatabaseDialect (io.confluent.connect.jdbc.sink.JdbcSinkTask:57)
[2019-05-01 11:10:21,620] INFO WorkerSinkTask{id=sink-mysql-standalone-0} Sink task finished initialization and start (org.apache.kafka.connect.runtime.WorkerSinkTask:301)
Even after starting the connector if I produce any data to the cluster, at sink connector nothing happens.
I tried to fetch the result of the connector status using:
curl localhost:8083/connectors/sink-mysql-standalone/status
the result is as follows:
{"name":"sink-mysql-standalone","connector":{"state":"RUNNING","worker_id":"10.3.0.40:8083"},"tasks":[{"id":0,"state":"RUNNING","worker_id":"10.3.0.40:8083"}],"type":"sink"}
sink.properties:
name=sink-mysql-standalone
connector.class=io.confluent.connect.jdbc.JdbcSinkConnector
tasks.max=1
topics=my-topic
value.converter=org.apache.kafka.connect.json.JsonConverter
value.converter.schemas.enable=false
# JDBCSink connector specific configuration
connection.url=jdbc:mysql://10.3.0.37:3306/mydb?zeroDateTimeBehavior=convertToNull&useUnicode=yes&characterEncoding=UTF-8
connection.user=myuser
connection.password=mypassword
insert.mode=upsert
table.name.format = tbl_kaf_${topic}
pk.mode=kafka
pk.fields=__connect_topic,__connect_partition,__connect_offset
fields.whitelist=messageId
auto.create=true
auto.evolve=true
The producer produces following record:
Key: id_5dfbdffe-ffbc-4fbf-925c-a14734304fa8, Value: {
"type" : "text",
"messageId" : "ID:activemq-XXXXXX-XXXXXXXXXXXXX-X:XX:1:2:2",
"correlationId" : "",
"destination" : {
"type" : "queue",
"name" : "qToKafka"
},
"replyTo" : null,
"priority" : 0,
"expiration" : 0,
"timestamp" : 1556549819473,
"redelivered" : false,
"properties" : {},
"payloadText" : "<Some XML Data>",
"payloadMap" : null,
"payloadBytes" : null
}
Please let me know what am I missing here.
Thanks

MongoDB FailedToParse: Bad characters in value

I have a simple mongodb database. I'm dumping using mongodump.
dump command
mongodump --db user_profiles --out /data/dumps/user-profiles
Here is the content of the user_profiles database. It has one collection (user_data) consisting of the following:
{ "_id" : ObjectId("555a882a722f2a009fc136e4"), "username" : "thor", "passwd" : "*1D28C7B35C0CD618178988146861D37C97883D37", "email" : "thor#avengers.com", "phone" : "4023331000" }
{ "_id" : ObjectId("555a882a722f2a009fc136e5"), "username" : "ironman", "passwd" : "*626AC8265C7D53693CB7478376CE1B4825DFF286", "email" : "tony#avengers.com", "phone" : "4023331001" }
{ "_id" : ObjectId("555a882a722f2a009fc136e6"), "username" : "hulk", "passwd" : "*CB375EA58EE918755D4EC717738DCA3494A3E668", "email" : "hulk#avengers.com", "phone" : "4023331002" }
{ "_id" : ObjectId("555a882a722f2a009fc136e7"), "username" : "captain_america", "passwd" : "*B43FA5F9280F393E7A8C57D20648E8E4DFE99BA0", "email" : "steve#avengers.com", "phone" : "4023331003" }
{ "_id" : ObjectId("555a882a722f2a009fc136e8"), "username" : "daredevil", "passwd" : "*B91567A0A3D304343624C30B306A4B893F4E4996", "email" : "daredevil#avengers.com", "phone" : "4023331004" }
After copying the dump to a nfs and then trying to load the dump into a test server using mongorestore
mongorestore --host db-test --port 27017 /remote/dumps/user-profiles
I'm getting the following error:
Mon May 18 20:19:23.918 going into namespace [user_profiles.user_data]
assertion: 16619 code FailedToParse: FailedToParse: Bad characters in value: offset:30
How to resolve this FailedToParse Error
To do further testing I created a test_db with a test_collection that only had one simple value 'x':1, and even that didn't work. So I knew something else had to be going on.
Versions of your tools matters
The version of mongodump that was being used was 3.0.3. The version on another virtual machine that was using mongorestore was 2.4.x. This was the cause for the errors. Once I got the mongodb-org-tools updated on my virtual machine (see official guide) I was able to get up and running as expected.
Hopefully this helps someone in the future. Check your versions!
mongodump --version
mongorestore --version

Jmeter: Error in Test Plan: Conversion error

I'm new to jmeter (as in just started reading about it last week.) I've been given some tests written by someone that's left the company but I cannot get the tests to open in jmeter. According to the .jmx file,
it was written in jmeter 2.9 so I installed 2.9. I got the standard plugins, but it just isn't loading, please see the error message below and let me know if you have any ideas.
Thanks!
2015/03/02 13:35:23 ERROR - jmeter.save.SaveService: Conversion error com.thoughtworks.xstream.converters.ConversionException: com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
---- Debugging information ----
message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
class : org.apache.jorphan.collections.ListedHashTree
required-type : org.apache.jorphan.collections.ListedHashTree
converter-type : org.apache.jmeter.save.converters.HashTreeConverter
path : /jmeterTestPlan/hashTree/hashTree/hashTree/hashTree[2]/hashTree[3]/com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
line number : 113
------------------------------- : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
---- Debugging information ----
message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
class : org.apache.jorphan.collections.ListedHashTree
required-type : org.apache.jorphan.collections.ListedHashTree
converter-type : org.apache.jmeter.save.converters.HashTreeConverter
path : /jmeterTestPlan/hashTree/hashTree/hashTree/hashTree[2]/hashTree[3]/com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
line number : 113
-------------------------------
message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
---- Debugging information ----
message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
class : org.apache.jorphan.collections.ListedHashTree
required-type : org.apache.jorphan.collections.ListedHashTree
converter-type : org.apache.jmeter.save.converters.HashTreeConverter
path : /jmeterTestPlan/hashTree/hashTree/hashTree/hashTree[2]/hashTree[3]/com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
line number : 113
-------------------------------
cause-exception : com.thoughtworks.xstream.converters.ConversionException
cause-message : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor : com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
first-jmeter-class : org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:65)
class : org.apache.jmeter.save.ScriptWrapper
required-type : org.apache.jorphan.collections.ListedHashTree
converter-type : org.apache.jmeter.save.ScriptWrapperConverter
path : /jmeterTestPlan
/hashTree/hashTree/hashTree/hashTree[2]/hashTree[3]/com.atlantbh.jmeter.plugins.jsonutils.jsonpathextractor.JSONPathExtractor
line number : 113
version : 2.9 r1437961
Last Jmeter.plugins require Jmeter 2.11 to work.
I think you have to upgrade Jmeter OR to uninstall Jmeter.plugins.
I would try to upgrade Jmeter to 2.12, usually it makes no harms.

sql error database on main page

any idea how to repair this error? I get this error on the main website page
DATABASE ERROR
************************
SELECT SQL_CACHE cid, title_ AS title
FROM ilance_categories
WHERE cattype = 'product'
AND visible = '1'
AND level <= '1'
ORDER BY sort ASC
MySQL Error : Unknown column 'title_' in 'field list'
Error Number : 1054
Date : Aug 12, 2014, 11:33:15
Script : http://www.redsquaretags.com/main.php
Class : ilance_mysql
Location : main
Referrer : Not referred
IP Address : 196.22.238.162
ILance Version : 4.0.0
Build : 8059
SQL Version : 898
MySQL Version : 5.5.37-cll
Server Load : n/a
************************
END DATABASE ERROR
Thank you, that's the only error I have thank you