I have installed a cluster including 3 nodes on amazon Ec2. I just stopped all instances , however after restarting all insatnces while accesingth e control console using 9443 port it gives me connection refuse error
Do I neeed to restart the MapR services and how?
Thnaks
Did you check the status of Webserver as it provides access to MCS.
Related
We are using non-swarm mode for our cluster of 3 machines with a bunch of links set up between containers and noticed a very strange problem: containers between 2 specific machines cannot communicate: containers on Machine A can talk to Machine B, but cannot reach the ones of Machine C. However, containers Machine B and Machine C are perfectly capable of connecting to each other.
After reading the logs we noticed that weave container on Machine A / Machine C (the ones with issues connecting) cannot reach the opposite machine.
The log is full of the messages like:
INFO: 2017/04/11 08:33:35.169670 ->[XXX.XXX.XXX.XXX:6783] attempting connection
INFO: 2017/04/11 08:33:35.187072 ->[XXX.XXX.XXX.XXX:6783] connection shutting down due to error during handshake: Unable to decrypt TCP msg
INFO: 2017/04/11 08:42:39.024325 ->[XXX.XXX.XXX.XXX:49040] connection accepted
INFO: 2017/04/11 08:42:39.035681 ->[XXX.XXX.XXX.XXX:49040] connection shutting down due to error during handshake: Unable to decrypt TCP msg
What is even more bizarre, no firewall rules are set up, machines are perfectly reachable and I can even telnet to the other weave daemon (using port 6783) and get "weave" string in response. We tried rebooting, redeploying the cluster and even recycling the machine with no luck: some bug or problem prevents weave on these specific machines to communicate.
We would be really thankful to you, SO users, if you would help or hint in any way.
Versions of software, just in case.
OS: Ubuntu 16.04.2 x64
Docker: 1.11.2-cs5, build d364ea1
weave: 1.6.2
EDIT: weave status X outputs (redacted):
weave status connections:
Lists connections as established encrypted to hosts I can access containers on, and says failed Unable to decrypt TCP msg, retry: 2017-04-11 13:18:07.695016283 +0000 UTC for the problematic host
weave status peers:
Lists only accessible hosts
weave status report:
Just a JSON version with the same data
I currently have an EC2 instance up and running with Amazon Linux running and transferred my project (which contains both React/NodeJS/Express) onto the EC2 instance via SFTP using FileZilla.
For the EC2's Security Groups, I opened a port for 3000 (protocol: tcp, source: 0.0.0.0/0), which is how my Express is defined as well.
So I sshed into EC2 instance and ran the project's Express, and sees it listening to port 3000 within the terminal. But once I hit the Public DNS with ec2...us-west-1.compute.amazonaws.com:3000, it says The site can't be reached - ec2...us-west-1.compute.amazonaws.com took too late to respond.
What could be the issue and how can I go about from here to connect to it?
Thank you in advance and will upvote/accept answer.
Just check if your Node.js server is running on the EC2 instance.
Debugging:
Check first if It working locally properly.
Check for the node.js server in EC2.
sudo netstat -tulpn | grep :3000
try to run server with --verbose flag i.e npm run server --verbose
it will show logs of the server while starting.
Check for the security group Setting for the EC2 instance.
try to connect with the ip:port i.e 35.2..:3000
If still it not working and response taking long time.
that means some other service is running on the same port.
try this in ec2:
sudo killall -9 node
npm run server
And connect with using IP(54.4.5.*:3000) or public DNS (http://ec2...us-west-1.compute.amazonaws.com:3000).
Hope It will help :)
You may be encountering an issue with outbound traffic. You may be inside a company's network, either physically connected or VPN'd in. In some instances, your VPN isnt set up to handle split traffic, so you must abide by your company's outbound restrictions.
In a situation like this, you would want to use a proxy to access your site. when locking down your security group, make sure you use your proxy's public IP (not your company's).
Usually, when we have connectivity issues, it is something basic or a firewall. I assume you have checked whether a firewall is running on either end, eg. iptables -L -n. Also, any protocol analyzer like wireshark or tcpdump would tell you where packets to port 3000 are visible.
My objective is to access my Hbase cluster on Azure with Squirrel with a Phoenix driver running on my local computer.
My Hbase cluster on Azure is operational. I can see it in the Ambari dashboard and I can access it using SSH. I can start Phoenix with the sqlline.py command pointing to one of the zookeeper nodes. The !tables command returs four lines.
My Hbase cluster is included in an Azure VNet. From my local computer (running Windows 10) I can connect to this VNet. I can ping the IP address (10.254.x.x) of the zookeeper node successfully but pinging the FQDN of the zookeeper node results in an error message:
"Ping request could not find host zk1-.......ax.internal.cloudapp.net.
Please check the name and try again."
When I start Squirrel on my local computer with the URL pointing to the FQDN of the zookeeper node I get an error message:
"Unexpected Error occurred attempting to open an SQL connection". The
stack trace points to a java.util.concurrent.RuntimeException: "Unable
to establish connection"
When I start Squirrel on my local computer with the URL pointing to the IP address of the zookeeper node I get a different error:
"Unexpected Error occurred attempting to open an SQL connection". The
stack trace points to a java.util.concurrent.TimeoutException.
I suspect this has something to do with the Domain Name resolution problem as described here [https://superuser.com/questions/966832/windows-10-dns-resolution-via-vpn-connection-not-working]. I applied the resolution as described by LikeARock47 on Feb 23. This did not improve the situation however.
Does this indeed have to do with the Domain Name resolution issue or is the problem somewhere else?
Is there a better solution to the Domain Name resolution issue?
A JDBC connection from Squirrel on my local Windows10 computer has succesfully been established to the Hbase cluster by using the zookeeper IP address and the port and "/hbase-unsecure":
jdbc:phoenix:10.254.x.x:2181:/hbase-unsecure
I can manage my HBase cluster with a local Squirrel now!
I'd still be interested to find out how I can get the zookeeper FQDN resolved locally.....
I'm using Couchbase Version 4.1.0-5005 Enterprise Edition (build-5005) and trying to run bikeShop sample but it's not showing the index.
gives me this error
We are having troubles communicating to the indexer process. The information might be stale
i opened all ports (for test) as told in this tutorial but it's get the same error
My OS is win 7
what should i do? thanks.
The reason could be that ports are not opened on the server or on any of the cluster servers.
Try accessing
http://SERVER_ADDRESS:9102/getIndexStatus with basic auth and the server should return a error message.
Try opening ports 9100, 9101, 9102 and 9999 and then retry with the same url and you will get a success message with list of indexes at couchbase server.
Do you have a single node cluster?
Did you checked all of the services (Data,Index,Query) in your node?
Thanks,
Roi
For those are working on CB v5.1, try accessing "curl -v -u [user]:[pwd] http://hostname:8091/indexStatus"
I have couchdb running on a Linux Ubuntu 14.04 VM and a .net Web application running under Azure Web Apps. Under our ELMAH logging for the web application I keep getting intermittent errors:
System.Net.Sockets.SocketException
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [ipaddress]:5984
I've checked the CouchDB logs and there isn't a record of those requests so I don't believe it's hitting the CouchDB server, I can confirm this by looking at the web server logs on Azure and see the Error 500 response. I've also tried a tcpdump however with little success (another issue logging tcpdump to a separate disk keeps failing due to access denied)
We've previously ran CouchDB on a Windows VM with no issues so I wonder if the issue relates to the OS connection settings for tcp and timeouts
Anyone have any suggestions as to where to look or what immediately jumps to mind?