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
Related
I've been coding a port scanner in Rust, and for detecting open ports what I do is create a TcpStream and try to connect to different ports on a given host to see if it allows the connection.
The problem I'm having is that when the connection fails, the OS (Linux) returns one of three codes:
101 - It is displayed if network is unreachable.
111 - It is displayed if connection is refused.
113 - It is displayed if there is no route to host.
And I've been looking for in-depth explanations of each error and what causes them, but I just find the same text over and over again.
Network unreachable → most likely explanation is that your computer is not connected to any network (Wi-Fi down, ethernet unplugged, …)
Connection refused means that you were able to reach the target computer, but that it refused the connection → no application is listening on the requested port on the other computer, or the firewall blocked the connection.
No route to host means that you were unable to reach the target computer. Either it is off, or there is a problem somewhere in the network between your computer and the target.
I have 116.89.189.0 public ip and in openstack vm, it allocated 116.89.189.39.
And I installed nodejs on vm(ubuntu 18.04) and started basic server.
but it doesn't works. what strange is that i can ping to 116.89.189.39 but
with my pc browser, 116.89.189.39:3000 doesn't works.
I checked with wireshark, there are many TCP Retransmission packets and
some strange packets from 116.89.189.3 (NOT 116.89.189.39)
below things are my nodejs server example and sercurity groups settings.
security group setting
network topology at OpenStack
nodejs on ubuntu
basic server source code
I am trying to connect to oracle database hosted on Linux server remotely from my windows machine and getting error ORA-12170: TNS: Connect Timeout. I've already checked the following:
listener.ora configuration and it's status.
tnsnames.ora naming parameters.
firewall is listening on the IP and the default port 1521
If there is no firewall between the client and the target database then you should not normally need to adjust the timeout. You can try adjusting the sqlnet parameters mentioned in the error message: *Action: If the error occurred because of a slow network or system,
// reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
// SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.
- -
However, I think you should ask your network team to trace your connection attempt especially if after increasing the timeout you still get the error. The full Oracle version in use and the platforms (client and target) may be important.
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.
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?