I have setup 5 VMs on my server, to deploy and try rethink DB. These machines are named as: debianone, debiantwo, debianthree, debianfour, debianfive. On debianove I'm running this command:
> ./rethinkdb --bind all
and here what I see as the log:
> Running rethinkdb 2.3.2 (GCC 4.9.2)... Running on Linux 3.16.0-4-amd64
> x86_64 Loading data from directory
> /home/saman/rethinkdb-2.3.2/build/release/rethinkdb_data Listening for
> intracluster connections on port 29015 Listening for client driver
> connections on port 28015 Listening for administrative HTTP
> connections on port 8080 Listening on cluster addresses: 127.0.0.1,
> 192.168.122.154, ::1, fe80::5054:ff:fe32:214c%2 Listening on driver addresses: 127.0.0.1, 192.168.122.154, ::1, fe80::5054:ff:fe32:214c%2
> Listening on http addresses: 127.0.0.1, 192.168.122.154, ::1,
> fe80::5054:ff:fe32:214c%2 Server ready, "debianone_fqw"
> 1bed427d-e98b-4cde-b58f-269c7d07dd83
After that I do execute below command on debiantwo:
./rethinkdb --join debianone:29015 --bind all
and it successfully getting connected to the first server with below logs:
Running rethinkdb 2.3.2 (GCC 4.9.2)...
Running on Linux 3.16.0-4-amd64 x86_64
Loading data from directory /home/saman/rethinkdb-2.3.2/build/release/rethinkdb_data
Listening for intracluster connections on port 29015
Connected to server "debianone_fqw" 1bed427d-e98b-4cde-b58f-269c7d07dd83
Listening for client driver connections on port 28015
Listening for administrative HTTP connections on port 8080
Listening on cluster addresses: 127.0.0.1, 192.168.122.125, ::1, fe80::5054:ff:fe0b:df56%2
Listening on driver addresses: 127.0.0.1, 192.168.122.125, ::1, fe80::5054:ff:fe0b:df56%2
Listening on http addresses: 127.0.0.1, 192.168.122.125, ::1, fe80::5054:ff:fe0b:df56%2
Server ready, "debianone_fqw" 1bed427d-e98b-4cde-b58f-269c7d07dd83
Then I'm moving into debianthree and run the same above command, in order to connect to debianone. but unfortunately it stucks with below output:
Running rethinkdb 2.3.2 (GCC 4.9.2)...
Running on Linux 3.16.0-4-amd64 x86_64
Loading data from directory /home/saman/rethinkdb-2.3.2/build/release/rethinkdb_data
Listening for intracluster connections on port 29015
and at the same time I can see below errors in the debianone logs:
2016-05-18T16:29:42.984026809 210.309930s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:43.184322734 210.510226s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:43.484533404 210.810437s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:43.934770639 211.260674s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:44.610004320 211.935908s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:45.622282451 212.948186s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:47.140603565 214.466507s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:49.417698306 216.743602s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:52.832918941 220.158822s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:58.364148418 225.690052s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:58.564178142 225.890082s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:58.864526591 226.190430s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:59.314689583 226.640593s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:29:59.989894570 227.315798s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:01.002126962 228.328030s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:02.520249008 229.846152s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:04.797608179 232.123512s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:08.212754870 235.538658s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:13.334942743 240.660846s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:21.018191367 248.344095s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
2016-05-18T16:30:32.542455984 259.868360s info: Rejected a connection from server 1bed427d-e98b-4cde-b58f-269c7d07dd83 since one is open already.
I still don't understand why rethinkdb is generating "debianone_fqw" id for all servers.
Has anyone ever had the same issue while deploying rethinkdb?
This seems like a bug. I found this issue on Github https://github.com/rethinkdb/rethinkdb/issues/5456. You maywant to create an issue and let them know.
You probably copied the RethinkDB data directory rethinkdb_data to all VMs when cloning (?) them. Every RethinkDB server has a server ID which must be unique. If the data directory is copied, all servers will have the same ID and you get the issue you're seeing.
Can you try deleting rethinkdb_data on all but one of the VMs and then start the servers again?
Related
Configuring a ELK stack version 8.1, based on two virtual machine which both run Oracle linux 8. I need to send logs from a VM to the other using rsyslog. On the recieving machine logs will be acquired using FileBeat. The file rsyslog.conf has been configured on the sending machine, adding target machine parameters. The file filebeat.yml has been configured to recieve logs from rsyslog like this:
- type: syslog
enabled: true
format: auto
protocol.tcp:
host: "X.X.X.X:10514"
The firewalld on the receiving machine has been configured opening the port 10514.
Since the reboot after configuration, the only thing I can get is the error:
cannot connect to X.X.X.X:10514: Connection refused
How can I solve this problem?
I'm using mysql in wamp and i'm trying to use database connector in anypoint studio. for the configuration i put Host: localhost, port 3306, User: root, password: ,(empty) and i add mysql driver mysql-connector-java-5.1.32.jar. and then i get this error:
Test connection failed: Cannot get connection for URL
jdbc:mysql://localhost:3306/mulesoft: Communication link failure
The last packet sent successfully to the server was 0 milliseconds ago. the driver has not received any packets from the server.
The problem is solved I had to restart the Wamp.
I want to use jvisualvm's remote functionality to see live stats of a remote JVM.
I've started the jvisualvm from my windows machine but I don't know how to configure the remote connection.
On the remote machine (OS: Redhat Linux), tomcat is started with below jmx parameters:
-Dcom.sun.management.jmxremote"
-Dcom.sun.management.jmxremote.port=3030"
-Dcom.sun.management.jmxremote.authenticate=false"
-Dcom.sun.management.jmxremote.ssl=false"
netstat -lnp| grep 3030
tcp 0 0 0.0.0.0:3030 0.0.0.0:* LISTEN 30728/java
ssh connection is open to remote server and I tunneled the remote port 3030 on a certain local port but when I create new jmx connection (localhost:localport) in jvisualvm I get the below error
Cannot connect to localhost:10000 using service:jmx:rmi:///jndi/rmi://localhost:10000/jmxrmi
Can someone help me to create the connection?
First of all if you are making a remote connection, localhost connection doesn't make sense.
You need to start jstatd on the remote machine. For this purpose create a jstatd.all.policy file in the home directory of your remote machine and add the following lines:
grant codebase "file:${java.home}/../lib/tools.jar" {
permission java.security.AllPermission;
};
Then on the command line of your remote machine you will type ' jstatd -J-Djava.security.policy=jstatd.all.policy -J-Djava.rmi.server.hostname={Your Ip address} '
Once jstatd service start on the remote machine you basically add the remote connection Ip address connection on the jvisualVM UI using add remote host.
The Oracle documents for JvisualVM can be referred at https://docs.oracle.com/javase/8/docs/technotes/guides/visualvm/applications_remote.html but it is really confusing to understand jstatd steps.
I want to create localhost connection in Oracle SQL Developer tool
my credentials are
username : SYSTEM
password : SYSTEM
Hostname :localhost or 127.0.0.1
port : 1521
sid : xe
When i connect i gives error The Network Adapter could not establish connection
The Network Adapter could not establish connection is caused because:
The database host name or port number is wrong.
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
you have either the wrong SQL Developer URL or you have a basic SQL*Net connectivity issue! This error is most likely caused by one of these factors:
You are using the wrong URL
The wrong port number or IP address (or DNS host name) was used
The listener is not configured properly
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
For a step by step checklist, see the notes on troubleshooting an Oracle connection problem.
I am trying to push my Activemq logs to a remote system Splunk Indexer using Universal forwarder however its not working. On my local system I see the logs as below:
06-13-2012 20:29:38.841 +0530 WARN DeploymentClient - Unable to send
handshake message to deployment server. Error status is: not_connected
06-13-2012 20:29:40.741 +0530 WARN TcpOutputProc - Raw connection to
ip=ip.address:9997 timed out
Local System OS - Windows-7
Remote system OS - Windows NT 2003
Can anyone help me out to solve this.
Thanks
the deployment server usually runs on port 8089 not 9997, which is typical used for forwarding data.
By default, Windows firewall disable port connection.
You can try adding exception for tcp port 9997 ( if you use this port for receiving data in Splunk server) in advanced firewall setting.