Lots of "Request failed to reach server, check DNS and/or server status" errors

[Hainish]

I've been getting a lot of these:

############################################
Message:
Request failed to reach server, check DNS and/or server status
e:
#
backtrace:
/home/legind/workspace/congress-forms/app/models/congress_member.rb:282:in `rescue in fill_out_form_with_capybara'
/home/legind/workspace/congress-forms/app/models/congress_member.rb:301:in `fill_out_form_with_capybara'
/home/legind/workspace/congress-forms/app/models/congress_member.rb:175:in `fill_out_form_with_poltergeist'
/home/legind/workspace/congress-forms/app/models/congress_member.rb:45:in `fill_out_form'
tasks/congress-forms.rake:48:in `block (4 levels) in '
tasks/congress-forms.rake:43:in `each'
tasks/congress-forms.rake:43:in `block (3 levels) in '
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:240:in `call'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:240:in `block in execute'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:235:in `each'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:235:in `execute'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/home/legind/.rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/task.rb:165:in `invoke'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:150:in `invoke_task'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:106:in `each'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:106:in `block in top_level'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:115:in `run_with_threads'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:100:in `top_level'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:78:in `block in run'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/lib/rake/application.rb:75:in `run'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/gems/rake-10.3.2/bin/rake:33:in `'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/bin/rake:23:in `load'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/bin/rake:23:in `'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/bin/ruby_executable_hooks:15:in `eval'
/home/legind/.rvm/gems/ruby-2.1.0@congress-forms/bin/ruby_executable_hooks:15:in `'
############################################

This has to do with ariya/phantomjs#12234 and teampoltergeist/poltergeist#375

[NullVoxPopuli]

does this happen when you call visit? that's my problem

[Hainish]

Yes, on visit. It's pretty sporadic.

[PrakashChoudhary-20]

I am facing the same issue. Did you find any solution to it?

[PrakashChoudhary-20]

Tried connecting to the 'HTTP' requests and it worked fine for me. Tried connecting to some 'HTTPS' sites... Worked..
However, application under test is something that needs a certificate installed on browser to authenticate. Is still failing for the same reason.

[j-ro]

Only dropping by to say we generally don't see this at all, not sure why.

[Hainish]

This is occurring less now than it did before, after upgrading the instance of AWS we're running. @NullVoxPopuli, @PrakashChoudhary-20, are you encountering this error on resource-confined machines?

[NullVoxPopuli]

my issue was actually that my travis config was configured for wrong url - so the error was totally warranted.

[chamnap]

I faced the same problem. It's totally a random failure.

[Hainish]

This seems to be pretty much occurring not at all anymore. May have been resolved as of the newest phantomjs release, closing

[juanibiapina]

@Hainish what release are you talking about at this point?

[Hainish]

We're up to 2.1.1. Phantom DC has updated to support that release.
On Mar 10, 2016 5:34 AM, "Juan Ibiapina" notifications@github.com wrote:

@Hainish https://github.com/Hainish what release are you talking about
at this point?

—
Reply to this email directly or view it on GitHub
#47 (comment)
.