Create TeamAdd Your APIDocs
Log In
Sign Up

Domainr

FREEMIUM
Verified
✓
By Domainr | Updated 9 days ago | Business
Popularity

9.9 / 10

Latency

382ms

Service Level

100%

Health Check

N/A

Back to All Discussions

503 backend read error

Rapid account: Wjozwowski
wjozwowski
8 years ago

Hi. Every second or third status request returns “503 backend read error”.

It doesn’t depend on data we send because we just have to resend the same request and next time it works as expected.

What’s the reason of such a big percentage of errors and are you going to fix this soon?

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

Okay, looks like the problem has been fixed. Thank you.

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

Sorry, I didn’t notice your last message. Testing now and will let you know the result soon.

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

I can’t tell exactly because all the testing and gathering statistics requires effort and time. What I can tell confidently is that the problem is still there because we’re still experiencing problems with checking domain availability.

Currently there’re more than 20000 domains in our database which have failed our software processing. Not all of them failed because of the “503 backend read error” but according to our previous analysis it was the main reason (about 80%).

Have you tried to check the domains I provided? You have to check them in batch (not one by one).

Rapid account: Domainr
domainr Commented 8 years ago

Hi there,

We found and fixed a timeout issue that may have been causing this — let us know if you’re still seeing it now?

Rapid account: Domainr
domainr Commented 8 years ago

Are you still seeing the exact same behavior, “Every second or third status request returns ‘503 backend read error’”?

Rapid account: Domainr
domainr Commented 8 years ago

Apologies for the delay, for some reason we didn’t receive a Mashape email notification for your previous post here. We’re looking into this now.

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

Any updates? Should I provide additional information?

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

Hello.

Here’s a list of domains:

centurion-project.org
gamcare.com
sophiabusinessangels.com
biotechman.com
finalprestige.net
webbeat.tv
sandboxcouture.com
davejohnsonart.com
bounceconnct.com
theycallmeque.com
rawb.net
maryannsansonetti.me
iemc07.org

And the error itself:

Wrong HTTP Status: 503
  Additional information:
  Unirest\Response Object
  (
      [code] => 503
      [raw_body] =>
  <?xml version="1.0" encoding="utf-8"?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  <html>
    <head>
      <title>503 backend read error</title>
    </head>
    <body>
      <h1>Error 503 backend read error</h1>
      <p>backend read error</p>
      <h3>Guru Mediation:</h3>
      <p>Details: cache-iad2145-IAD 1449572661 922601321</p>
      <hr>
      <p>Varnish cache server</p>
    </body>
  </html>
      [body] =>
  <?xml version="1.0" encoding="utf-8"?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  <html>
    <head>
      <title>503 backend read error</title>
    </head>
    <body>
      <h1>Error 503 backend read error</h1>
      <p>backend read error</p>
      <h3>Guru Mediation:</h3>
      <p>Details: cache-iad2145-IAD 1449572661 922601321</p>
      <hr>
      <p>Varnish cache server</p>
    </body>
  </html>
      [headers] => Array
          (
              [0] => HTTP/1.1 503 backend read error
              [Accept-Ranges] => bytes
              [Content-Type] => text/html; charset=utf-8
              [Date] => Tue, 08 Dec 2015 11:04:21 GMT
              [Retry-After] => 0
              [Server] => Mashape/5.0.6
              [Via] => 1.1 varnish
              [X-Cache] => MISS
              [X-Cache-Hits] => 0
              [X-RateLimit-free-Limit] => 100000
              [X-RateLimit-free-Remaining] => 95241
              [X-Served-By] => cache-iad2130-IAD
              [X-Timer] => S1449572646.039680,VS0,VE14999
              [Content-Length] => 447
              [Connection] => keep-alive
          )
  )
Rapid account: Domainr
domainr Commented 8 years ago

You can submit private Mashape tickets, here’s a screenshot of it: http://cl.ly/image/0d2Y2n1R2Q3c

We definitely want to track down why this is happening, as it sounds like a bug.

Rapid account: Wjozwowski
wjozwowski Commented 8 years ago

It happens randomly with random TLDs and domains. If there’s a way to send you a private message, I can provide a list of domains but you probably won’t be able to reproduce the error because it happens randomly (we just have to resend the same request again and it works as expected).

Join in the discussion - add comment below:

Login / Signup to post new comments