Environment description:
OS：CentOS 7.9
GridDB ：CE 5.0
Operation: changed the IP address of the GridDB cluster, mainly modified
"serviceAddress" in/var/lib/gridstore/conf/gs _ node.json file:
"notificationMember" in /var/lib/gridstore/conf file:
Check the service status after modification.
Check the situation of the cluster.
It seems that everything is correct, but it can't be connected through JDBC. My client is DBeaver.
No suitable driver found for jdbc:///myCluster/?notificationMember=192.168.5.120:20001
Please tell me what's wrong. thank you
Related
I was able to setup non EC mode easily, Now I am trying to setup minio server on local 3 node, as a distributed erasure code mode before I move to setup in the production. I want to replicate this setup in local network.
https://docs.min.io/docs/distributed-minio-quickstart-guide.html
Following the guide link :
I am running this command:
zc#rockpix:/minio$ export MINIO_ROOT_USER=minio
zc#rockpix:/minio$ export MINIO_ROOT_PASSWORD=minio123#
zc#rockpix:/minio$ minio server http://localhost{1...3}/mnt/ssd{1...3}
but running the above command result in
Invalid command line arguments: lookup localhost1 on 127.0.0.53:53: server misbehaving
> Please provide correct combination of local/remote paths
HINT:
For more information, please refer to https://docs.min.io/docs/minio-erasure-code-quickstart-guide
The guide does not mention if I need to setup a domain name. I was thinking if the non EC mode can working without a domain setup then why can't we setup distributed erasure code without having domain name setup ?
The error message looks like there is a DNS issue with that hostname, use a valid resolvable hostname or IP's. As a side note four nodes is the minimum recommended for a production setup.
I have installed and configured a 3 monetdb nodes cluster on 3 virtual machines on my MacBook (Using Oracle Virtual Box). I use MonetDB 5 server 11.37.7
I have followed the Cluster Management documentation of MonetDB, but the monetdb discover command only returns the dbfarm of the local instance. Each node still isn't aware of other nodes.
I can connect to any nodes from any other node using monetdb -h [host] -P [passphrase], I can also discover the remote farms of a specific host by using monetdb -h host -P passphrase discover
The answer to this question monetdb cluster management can't setup helped me in setting the listenaddr property to 0.0.0.0, but still, the discover command only returns the local monetdb farm.
EDIT
Thanks to Jennie suggestion below, I noticed that the monetdb log file contains error while sending broadcast message: Network is unreachable.
I used netcat utility to brodcast UDP message from one node to the other 2 and it worked, I can ping, ssh and the 3 nodes are part of the same network configured with virtualbox, but the error is still there.
All your VMs must be in the same LAN environment. monetdb discover basically goes over all IP addresses under the same subnet.
Can you some how verify that's the case?
I got it working, thanks to #Jennie's post. For anyone using VirtualBox:
Use the first network adapter of each configured node with Bridge access instead of NAT
Configure the following property of your dbfarm: listenaddr=0.0.0.0
For testing purpose, it may be worth reducing the property discoveryttl to less than the default 10mns
I'm trying to install Oracle Database for the first time and I'm facing many problem. I, following this guide, but I can't understand what should I set in the form shown in section 14. What is the database hostname? How I determine it?
It is described right above the section 14's screenshot:
The host name must resolve to the local host or virtual host because
the host name is used for the local Oracle WebLogic Server as well as
the Oracle Management Service. Do not provide a remote host or a load
balancer virtual host in this field. Do not enter an IP address. Do
not use underscores in the name. Short names are allowed, but you will
see a warning, so Oracle recommends that you enter a fully qualified
domain name instead.
I'm trying to install oracle on AWS redhat instance. Follow the steps given on this url: http://www.davidghedini.com/pg/entry/install_oracle_11g_xe_on And when I run config command as follows
/etc/init.d/oracle-xe configure
It gives following error.
Database Configuration failed. Look into
/u01/app/oracle/product/11.2.0/xe/config/log for details
When I check the log files it shows following errors.
ORA-01034: ORACLE not available Process ID: 0 Session ID: 0 Serial
number: 0
It seems specific issue on AWS cloud instance.
Is it because of swap memory?
Or is it because of port issue?
I'm using micro instance on it.
How can I get through?
this might be an EC2 security group issue and outbound access to the network on some port being used by the installer (license check, maybe?).
if your EC2 instance is very tightly locked down, you could test if it's a security group issue by adding a new Outbound security group rule to allow all TCP traffic out to anywhere on the internet (0.0.0.0/0)
for example, the install might be trying to hit a remote licensing server endpoint via HTTP or HTTPS but your security group doesn't allow that traffic out.
perhaps there's a 'verbose' flag that you can run the installer with that can give you more info about what it's failing on? HTH
I have an elasticsearch server with host h1 running at port 9200. And i have a separate kibana server with host h2 running on port 5601. I have configured both of them properly and then tried to see the GUI of kibana.
It says Status:Red and in the error i see "Unable to connect to Elasticsearch at h1:9200"
I ran the basic troubleshoot mentioned in the elk documentation i.e. to check whether kibana.yml's elasticsearch.url field is properly referring to h1:9200 or not and vice versa for elasticsearch.yml's fields. Everything seems to be fine. What could be any other reason for this error? How to fix the same?
Could be for a number of reasons, connectivity/network configuration usually the prime suspect - check out this troubleshooting article for possible solutions