Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • gracedb
  • Issues
  • #147

Closed
Open
Opened Apr 27, 2019 by Tanner Prestegard@tanner.prestegardMaintainer

Intermittent 502 'Bad Gateway' error

From @patrick-brady:

Hi Tanner:

I've started going through the sentry logs for gwcelery. I did find a a number of cases of the 502 bad gateway error. This does not appear to be coming from any single api request. Here are links to 4 different sentry messages:

https://sentry.io/organizations/ligo-caltech/issues/994229585/events/ac120124b2aa41e6aa5280fceafb403b/

https://sentry.io/organizations/ligo-caltech/issues/993796824/events/c337068a03f246f1bbbd8bc4149a6256/

https://sentry.io/organizations/ligo-caltech/issues/998916934/events/567af335c4f248d7bb1cfd78a33017e8/

https://sentry.io/organizations/ligo-caltech/issues/992306270/events/bb4f0fd48cde40719383c24174fd1189/

I spent about half an hour looking around for information related to 502 errors on AWS and found the following: https://blog.transposit.com/the-mysterious-case-of-the-bad-gateway-502-b9f370207d87 This person tracked their errors to use of dropwizard (https://www.dropwizard.io/1.3.5/docs/). I have no idea if that is part of the stack use on ALB for gracedb, but it's what it did that may give hints on addressing the 502 errors. I know this is not your expertise and that Tom has extremely limited time left, but I thought I'd put this to you and see if you can make anything of it.

Cheers, Patrick

Edited Apr 27, 2019 by Tanner Prestegard
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: lscsoft/gracedb#147