Error in Remote Calabash Server: 'Connection refused" - ruby

For the purposes of testing. I have three computers running 9 containers locally on top of a ruby Sinatra server, testing an Android app. I'm using calabash server with cucumber steps.
All was running fine until about a month ago and I started seeing Calabash server errors. The first few containers run fine. Then it gets to around the 5th container and I start seeing a connection error as follow: "
Error in Remote Calabash Server: 'Connection refused - Connection
refused - connect for "127.0.0.1" port 37265 (127.0.0.1:37265)'"
Followed by a long runtime error.
And that container craps out. The other containers will then usually run successfully after that.
I understand it's a very broad sounding issue and there's a lot of variables at play. But any suggestions at all of where to look would be most helpful. Could the servers just be struggling with too many requests? It's not getting hit by many at once, but who knows at this stage.
Any help as always much appreciated.

Related

Unable to connect to GitHub for 2 years, irregardless of network - any ideas?

Toku here.
I've been without GitHub for 2 years now, and I'm getting sick of it.
In terms of web connection, I get a basic "This site can't be reached" - ERR_CONNECTION_REFUSED.
Attempting to use the desktop app results in more information
Image of 443 port error - more connection refusals.
Image of curl command result
I'm running Win10 Home build 19044, connected to a private home network with no restrictions. What would be causing this?
Tried reconfiguring DNS, and it simply didn't change anything.
At the suggestion of FiddlingAway, I resynced my system time, to no effect.
For reference, I am living in the US, so there should be no issues connecting due to a countrywide ban. The web interface does not load, even on a VPN.

Non HTTP response code: java.net.ConnectException in JMeter

I am new to JMeter. I have created one script for our application. Now our complete system architecture is deployed on AWS. So, we have created one EC2 instance as "Load Generator" to run my script with 100 user load. Script is working fine on my local system but it is not working on that instance.
Every time I am getting below error. I have also tried to run from non-GUI mode as well but result is same.
Error: Response code: Non HTTP response code: java.net.ConnectException Response message: Non HTTP response message:
Connection timed out (Connection timed out)
Please help me out here. How to resolve this issue on EC2 instance.
I had a similar problem (my tests were executed on Microsoft's Azure).
The issue was that the system being tested had a IP white list.
When I ran it on my local machine, it was already within our VPN
(whitelisted).
When it was executed on Azure, the VM had a
dynamic IP which was not whitelisted.

Docker login from cmd line yields i/o timeouts

I'm trying to login to docker from the Docker Quickstart Terminal but it doesn't work.
I always get an error saying: "Error response from daemon: Server Error: Post https://index.docker.io/v1/users/: dial tcp: i/o timeout"
I have been working with docker the last few days and was always able to login and push/pull stuff. The only thing different I can think of is that I'm currently on a different Wifi.
Any help is greatly appreciated, thanks.
Karsten
This is a known issue, and is probably related to VirtualBox; after switching networks, boot2docker/VirtualBox sometimes looses connectivity or uses incorrect DNS settings.
DNS confused when switching WiFi networks
Container connectivity lost after switching wireless networks
Manual restart required everytime network connectivity changes (contains some workarounds)
Docker Machine 0.5.3 adds two new options that may circumvent this;
--virtualbox-dns-proxy
--virtualbox-host-dns-resolver
After restarting the machine it worked again, don't know what caused the problem though...

Cannot connect to localhost:8082

After successful running the maven project in eclipse, I cannot connect to http://localhost:8082. It shows the below error:
connection refused
What should I do to resolve the problem?
This exception usually occurs when there is no service listening on the port you are trying to connect to. A couple of things could be happening:
You have not started your server.
Your server is not waiting to
accept connections.
You are trying to connect to the wrong port
number.
You should check your services. I think they are either stopped or not working. You can check the services:-
a) if using windows by clicking services in control panel
b) if using linux type in the command Line sudo mqsql service.
you can refer this link- https://www.cyberciti.biz/faq/how-to-find-out-if-mysql-is-running-on-linux/
2)Also check the database connection string might you have not used correct string.

heroku: Running console attached to terminal...

I am trying to deploy a simple rails application to an heroku account, I was able to login and push, only it seems to hang when I try to
heroku run rake db:migrate
or to
heroku run console
I get the message
Running console attached to terminal...
and then nothing happens... it just hangs. I read that it could be I have some blocked ports (like, port 5000) but it seems quite strange to me, I never had such problems before...
I am on Ubuntu, how can I check if that's the case? or how could I fix the issue? Anybody got any hint? I already tried to heroku update, same issue...
Its the port problem i also face the same issue a while ago and their support guys told me top make open the port.
Here is their reply
This problem is typically caused by a connectivity or firewall issue. You can test your connection to our heroku run and heroku console servers by running the following commands:
telnet rendezvous.heroku.com 5000
telnet s1.runtime.heroku.com 5000
Some users have success after whitelisting these hostname+port combinations in their firewall. We recommend contacting your IT department to move forward with this issue.
If you are successfully able to connect, press Ctrl+] (right bracket) and then type quit to exit the telnet session.
An application which takes a long time to boot can also exasperate connectivity issues. If the server does not respond quickly enough, your local connection will timeout before the app can boot.
To test the net enabled access to that port try the following. They mention that filtered-port issue on their guide.
$ telnet rendezvous.heroku.com 5000

Resources