Skip to content

Instantly share code, notes, and snippets.

@brson
Created June 1, 2016 17:18
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save brson/f36e363febafe0cac6b2ca5b291760b9 to your computer and use it in GitHub Desktop.
Save brson/f36e363febafe0cac6b2ca5b291760b9 to your computer and use it in GitHub Desktop.
2016-06-01T17:17:53.047847+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/api/v1/crates/app_units/0.2.4/download" host=crates.io request_id=8c2af21b-3819-47c2-8ed8-a1c9d997c667 fwd="86.161.10.130" dyno=web.2 connect=1ms service=30000ms status=503 bytes=0
2016-06-01T17:17:53.220539+00:00 app[web.1]: 2016/06/01 17:17:53 [error] 78#0: *549 upstream prematurely closed connection while reading response header from upstream, client: 10.136.156.148, server: _, request: "GET /api/v1/crates/getopts/0.2.14/download HTTP/1.1", upstream: "http://127.0.0.1:8888/api/v1/crates/getopts/0.2.14/download", host: "crates.io"
2016-06-01T17:17:53.221323+00:00 app[web.1]: measure#nginx.service=30.002 request_id=58d593c5-3f60-473a-8c92-d1c4d9155163
2016-06-01T17:17:53.220390+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:59370 [2016-06-01T17:17:53Z] Get /api/v1/crates/getopts/0.2.14/download - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:17:53.225047+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/api/v1/crates/getopts/0.2.14/download" host=crates.io request_id=58d593c5-3f60-473a-8c92-d1c4d9155163 fwd="208.78.110.199" dyno=web.1 connect=4ms service=30000ms status=503 bytes=0
2016-06-01T17:17:55.421512+00:00 app[web.1]: measure#nginx.service=30.001 request_id=04a6bf97-59c3-446c-871c-66f581c42b96
2016-06-01T17:17:55.421303+00:00 app[web.1]: 2016/06/01 17:17:55 [error] 78#0: *553 upstream prematurely closed connection while reading response header from upstream, client: 10.65.95.34, server: _, request: "GET /api/v1/crates/nickel?_=1464801444546 HTTP/1.1", upstream: "http://127.0.0.1:8888/api/v1/crates/nickel?_=1464801444546", host: "crates.io", referrer: "https://crates.io/crates/nickel"
2016-06-01T17:17:55.421121+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:59502 [2016-06-01T17:17:55Z] Get /api/v1/crates/nickel - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:17:55.419217+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/api/v1/crates/nickel?_=1464801444546" host=crates.io request_id=04a6bf97-59c3-446c-871c-66f581c42b96 fwd="171.4.248.164" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0
2016-06-01T17:17:58.830874+00:00 app[web.1]: measure#nginx.service=29.998 request_id=9a136bc7-ef20-4136-af7d-fe540e247bb5
2016-06-01T17:17:58.833040+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:59758 [2016-06-01T17:17:58Z] Get /summary - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:17:58.831280+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/summary?_=1464801448547" host=crates.io request_id=9a136bc7-ef20-4136-af7d-fe540e247bb5 fwd="176.63.28.208" dyno=web.1 connect=5ms service=30001ms status=503 bytes=0
2016-06-01T17:17:59.226943+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=crates.io request_id=2f5d3aea-db59-4224-b999-37a851d9a26a fwd="65.88.88.203" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0
2016-06-01T17:17:59.229385+00:00 app[web.1]: 2016/06/01 17:17:59 [error] 78#0: *557 upstream prematurely closed connection while reading response header from upstream, client: 10.138.157.101, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8888/", host: "crates.io"
2016-06-01T17:17:59.230075+00:00 app[web.1]: measure#nginx.service=30.002 request_id=2f5d3aea-db59-4224-b999-37a851d9a26a
2016-06-01T17:17:59.229116+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:59788 [2016-06-01T17:17:59Z] Get / - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:18:03.851677+00:00 app[web.2]: measure#nginx.service=0.002 request_id=72025e34-27ce-4367-95a0-902027f652d0
2016-06-01T17:18:03.849877+00:00 app[web.2]: INFO:conduit_log_requests: 127.0.0.1:42449 [2016-06-01T17:18:03Z] Get /keywords/random - 0ms 200
2016-06-01T17:18:03.851939+00:00 heroku[router]: at=info method=GET path="/keywords/random" host=crates.io request_id=72025e34-27ce-4367-95a0-902027f652d0 fwd="66.249.66.144" dyno=web.2 connect=0ms service=2ms status=200 bytes=1371
2016-06-01T17:18:05.830653+00:00 app[web.1]: 2016/06/01 17:18:05 [error] 78#0: *559 upstream prematurely closed connection while reading response header from upstream, client: 10.140.192.224, server: _, request: "GET /api/v1/crates?page=1&per_page=10&q=boltzmann&_=1464801453865 HTTP/1.1", upstream: "http://127.0.0.1:8888/api/v1/crates?page=1&per_page=10&q=boltzmann&_=1464801453865", host: "crates.io", referrer: "https://crates.io/search?q=boltzmann"
2016-06-01T17:18:05.832665+00:00 app[web.1]: measure#nginx.service=30.003 request_id=2eb5fa67-4719-40be-8e96-c71c9471977e
2016-06-01T17:18:05.830500+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:60253 [2016-06-01T17:18:05Z] Get /api/v1/crates - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:18:05.827774+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/api/v1/crates?page=1&per_page=10&q=boltzmann&_=1464801453865" host=crates.io request_id=2eb5fa67-4719-40be-8e96-c71c9471977e fwd="88.195.204.108" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0
2016-06-01T17:18:07.430342+00:00 app[web.1]: 2016/06/01 17:18:07 [error] 78#0: *561 upstream prematurely closed connection while reading response header from upstream, client: 10.142.8.132, server: _, request: "GET /api/v1/crates/rustc-demangle/0.1.0/download HTTP/1.1", upstream: "http://127.0.0.1:8888/api/v1/crates/rustc-demangle/0.1.0/download", host: "crates.io"
2016-06-01T17:18:07.430227+00:00 app[web.1]: ERROR:conduit_log_requests: 127.0.0.1:60349 [2016-06-01T17:18:07Z] Get /api/v1/crates/rustc-demangle/0.1.0/download - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
2016-06-01T17:18:07.434713+00:00 app[web.1]: measure#nginx.service=30.005 request_id=d23ae391-614d-4086-9a0b-1f0e5ad253ff
2016-06-01T17:18:07.430398+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/api/v1/crates/rustc-demangle/0.1.0/download" host=crates.io request_id=d23ae391-614d-4086-9a0b-1f0e5ad253ff fwd="208.78.110.199" dyno=web.1 connect=3ms service=30002ms status=503 bytes=0
2016-06-01T17:18:08.640752+00:00 app[web.2]: 2016/06/01 17:18:08 [error] 78#0: *539 upstream prematurely closed connection while reading response header from upstream, client: 10.146.25.156, server: _, request: "GET /api/v1/crates/gtk/0.0.6/download HTTP/1.1", upstream: "http://127.0.0.1:8888/api/v1/crates/gtk/0.0.6/download", host: "crates.io"
2016-06-01T17:18:08.645186+00:00 app[web.2]: measure#nginx.service=30.006 request_id=f66f9018-03bc-4461-bcfb-cc73903e3295
2016-06-01T17:18:08.640616+00:00 app[web.2]: ERROR:conduit_log_requests: 127.0.0.1:38790 [2016-06-01T17:18:08Z] Get /api/v1/crates/gtk/0.0.6/download - 30000ms 500: failed to get a database connection: Timed out while waiting for a connection failed to get a database connection: Timed out while waiting for a connection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment