No service available error 502
jclaveau
PROOP

2 years ago

Since 10 minutes my api instances went down.

  • I first had a "KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full." so I restarted them to flush the pool but now they return 502 errors.
  • As my backend service also returns 502 errors (without restart), I deduced it's not related to me
  • I have no specific issue in my PG service logs
  • My apis are Directus / Node Apps
  • It worked without issue since teh last deploy resterday
  • My app is hosted in west Europe

id: 65aff0db-6586-4be0-8420-b2e67ae4378d

2 Replies

jclaveau
PROOP

2 years ago

Service is back


charlie
PRO

2 years ago

Same for me, seems to have resolved itself


Welcome!

Sign in to your Railway account to join the conversation.

Loading...