I have insatlled Below Softwares in windows 10
1.cassandra version 2.2.15
Docker version 19.03.2
3.minikube version: v1.4.0
4.helm client and sever v2.15.0-rc.1
kubectl client v1.14.6 and server v1.16.0
I am running cassandra DB in localhost port 9042 , i want to connect that localhost DB to my minikube helm with the IPaddress or hostname of the cassandra i am not able .
I am able to connect to the local cassandra db to Minikube cluster , need to change the
rpc_address in cassandra.yaml
rpc_address: <LOCAL_WINDOWS_IPV4_ADDR>
broadcast_rpc_address: 1.2.3.4
Related
I have following error on Windows10 after installing kubectl via
choco install kubernetes-cli:
PowerShell
PS C:\Users\userA> kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
Cmd
C:\Users\userA>kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
I have created .kube folder (C:\Users\userA\.kube) and inside of it an empty config file
I set windows environment variable:
Variable_name: KUBECONFIG
value: C:\Users\userA\.kube\config
EDIT: I tested it with running minikube:
You need to start the server first, with:
minikube start
Edit: As op tries to use hyper-v the following command tells minikube to use hyper-v
minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"
To get this workling it is also neccessary to set a virtual switch named "Primary Virtual Switch" in hyper-v.
I've figured it out myself - on Windows 10
Hyper-V should be turn on if you are using Docker desktop but for minikube it should be turn off.
When i had turned off Hyper-V and restarted my PC - then minikube start worked fine.
I'm trying SSH tunneling for the first time hence, I'm expecting some level of guidance (with explanation) to setup an SSH tunnel so that I from my Windows client machine can connect to things like ElasticSearch and MongoDB that are residing on AWS EC2 Windows Server.
Here is how you can make tunnel to server for MongoDB,
ssh -L 9999:127.0.0.1:27017 user#serverip -NnT
Now you are able to access your remote mongodb through tunnel on port 9999 so you can now connect to mongodb server from local like,
mongo --host 127.0.0.1 --port 9992
The same way you can also create your own tunnel for elasticsearch also by specifying Port of elastic search like below,
ssh -L 9200:127.0.0.1:9200 user#serverip -NnT
Not have more knowledge of accessing elastic through port but this might help.
SSS == 'Selenium Standalone Serwer'
I've got:
installed SSS by homebrew
downloaded couple versions of SSS
macOS High Sierra with IP's:
192.168.0.1
172.18.0.1 - IP for docker
localhost/127.0.0.1
I have turned off my firewall
I run this server in one of the following ways:
selenium-server -port 4444
java -jar selenium-server-standalone-3.8.1.jar -port 4444
after this, I've got logs:
2017-12-22 12:34:23.280:INFO:osjs.AbstractConnector:main: Started ServerConnector#210ab13f{HTTP/1.1,[http/1.1]}{0.0.0.0:4444}
so as I understand 0.0.0.0 it listens for all IPs
BUT
I can not connect to this server using IP 192.168.0.1 or 172.18.0.1
I can use the only localhost for connecting to this server.
netstat doesn't display port 4444 as open.
When I do this same on Ubuntu 16.04 it works great. I can create a new session using all addresses, I can create a new session also from docker container.
Can you tell me what I'm doing wrong or what I don't know?
I have two VirtualBox Vagrant machines running on my Mac:
Ubuntu 16.04.1, private network: 192.168.122.13, running as a webserver (PHP, Apache, etc.).
Ubuntu 16.04.1, private network: 192.168.122.14, running MySQL.
How do I connect to MySQL from the webserver?
I have enabled port forwarding on the MySQL box (3306 guest => 5629 host) and commented out the bind-address line in /etc/mysql/mysql.conf.d/mysqld.cnf. If I SSH onto the webserver and try to connect using mysql -host 192.168.122.14 -P 5629 -u xxx -p yyy the connection times out (ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.122.14' (110)).
MySQL runs on the vagrant box with IP 192.168.122.14, and is listening on port 3306. When you forward ports, it means that the port 3306 from the virtual machine, is forwarded to your host OS on the port 5629.
From your web server (192.168.122.13) you could connect to mysql by
mysql -h 192.168.122.14 -P 3306
or
mysql -h 192.168.122.1 -P 5629
Here 192.168.122.1, refers to the IP of your host OS. The IP 192.168.122.1 is created by vagrant and assigned to your host OS
I am new to OpenShift, and trying to run elasticsearch in a DIY cartridge. The elasticsearch app seems to be working, but I cannot connect to the 3306 port which it needs for node to node communication.
When I run the
$ rhc port-forward -a myapp
Forwarding ports ...
To connect to a service running on OpenShift, use the local address
Service Local OpenShift
------- -------------- ------------------------
java 127.0.0.1:3306 => 127.10.49.101:3306
java 127.0.0.1:9200 => 127.10.49.101:9200
But when I run my indexing groovy/grails app that uses an elasticsearch plugin to index data, it cannot connect to the OpenShift elasticsearch node. It should be using port 3306 to connect to the OpenShift elasticsearch node. The app config has
client.node = 'node'
client.hosts = [ [host:'127.0.0.1', port:3306 ] ]
Note that my indexing app worked fine when elasticsearch was run locally, but it does not connect to elasticsearch running on OpenShift.